path: root/2025/captions/emacsconf-2025-latex--latex-export-in-orgmode-the-overhaul--pedro-a-aranda-gutirrez--main.vtt

WEBVTT

00:00:00.000 --> 00:00:04.456
Okay. Good afternoon, morning or evening,

00:00:04.457 --> 00:00:06.519
whatever it is in your airtime zone.

00:00:06.520 --> 00:00:10.959
I'm Pedro Aranda and I'm going to be talking about

00:00:10.960 --> 00:00:12.959
what I've been doing

00:00:12.960 --> 00:00:16.999
with the latest backend in Org Mode

00:00:17.000 --> 00:00:24.719
and the different Sorry, and the way it treats fonts.

00:00:24.720 --> 00:00:28.279
Just a couple of words before

00:00:28.280 --> 00:00:30.359
I am going to go through motivation,

00:00:30.360 --> 00:00:35.279
the evolution and get you an idea of what you can get

00:00:35.280 --> 00:00:38.079
from the feature branch that I have started

00:00:38.080 --> 00:00:41.399
and give a couple of demos.

00:00:41.400 --> 00:00:47.779
actually my motivation is I was using ox-latex currently

00:00:47.780 --> 00:00:51.439
and b and ox-beamer for as a foundation for my activities

00:00:51.440 --> 00:00:54.399
mainly for lecture notes and lecture slides

00:00:54.400 --> 00:01:01.359
so i came from pure latex and beamers

00:01:01.360 --> 00:01:04.519
and for me the real cool use case

00:01:04.520 --> 00:01:05.959
or I would say this was

00:01:05.960 --> 00:01:07.959
the killer use case for me was

00:01:07.960 --> 00:01:09.239
I have a programming lecture

00:01:09.240 --> 00:01:12.199
which is sort of a Python 101

00:01:12.200 --> 00:01:14.199
and when I'm live in the lecture

00:01:14.200 --> 00:01:18.279
I can go and if the pupils ask me I can modify code,

00:01:18.280 --> 00:01:21.079
show modified code and results on the fly

00:01:21.080 --> 00:01:25.119
and that's something that really impresses the kids

00:01:25.120 --> 00:01:30.159
and makes them understand what we are talking about.

00:01:30.160 --> 00:01:34.399
From my pro-subjective point of view, in some,

00:01:34.400 --> 00:01:38.159
mainly in ox-beamer, some of the things that I was missing

00:01:38.160 --> 00:01:41.879
is that emojis would really break the monotony

00:01:41.880 --> 00:01:47.679
and I missed the support for emojis and stock Beamer themes.

00:01:47.680 --> 00:01:52.159
And some fonts I also found were suboptimal

00:01:52.160 --> 00:01:56.639
or difficult to adapt in case they need an adaptation.

00:01:56.640 --> 00:02:01.799
So, for example, people who need special fonts

00:02:01.800 --> 00:02:05.799
because of their special capabilities,

00:02:05.800 --> 00:02:11.159
it's difficult to get those fonts from the stock themes

00:02:11.160 --> 00:02:17.359
and from the stock font implementations you have there.

00:02:17.360 --> 00:02:19.399
So, requirements on mice

00:02:19.400 --> 00:02:21.479
from the Emacs site to do this is none,

00:02:21.480 --> 00:02:24.999
because basically, okay, the only thing I want

00:02:25.000 --> 00:02:27.159
is to work on a vanilla Emacs,

00:02:27.160 --> 00:02:28.399
which is more or less recent,

00:02:28.400 --> 00:02:30.119
because yes, I'm a bit of a freak

00:02:30.120 --> 00:02:32.479
and I compile it every two, three,

00:02:32.480 --> 00:02:36.839
I get it from master and compile it every two, three days.

00:02:36.840 --> 00:02:40.599
And Yahoo, I had to change to Neumark,

00:02:40.600 --> 00:02:47.359
and I'm able now to get my vanilla Neumarks within four.

00:02:47.360 --> 00:02:53.359
So that was a big accomplishment in these last days.

00:02:53.360 --> 00:02:55.119
What is the evolution?

00:02:55.120 --> 00:03:00.719
I mean my personal evolution and my take of xLatex

00:03:00.720 --> 00:03:05.919
was I put everything in a in a latex file

00:03:05.920 --> 00:03:09.959
and I input it through the latex shader and that's it.

00:03:09.960 --> 00:03:12.319
But that was not very beginner friendly

00:03:12.320 --> 00:03:15.719
and once I had some people interested in this,

00:03:15.720 --> 00:03:19.159
oh wow I can modify the code on the fly

00:03:19.160 --> 00:03:21.119
and see the results on the fly,

00:03:21.120 --> 00:03:26.719
it was more difficult for them to give it a go.

00:03:26.720 --> 00:03:32.359
So I just, because they,

00:03:32.360 --> 00:03:36.919
there are people who have not that big,

00:03:36.920 --> 00:03:41.159
that much experience with LaTeX

00:03:41.160 --> 00:03:44.919
and It can even be a bridge to introduce people into latex.

00:03:44.920 --> 00:03:48.959
So, in any case, it was not very beginner-friendly

00:03:48.960 --> 00:03:52.799
and I had complaints on that.

00:03:52.800 --> 00:03:57.159
So, what I think was, we can do better.

00:03:57.160 --> 00:04:00.399
My first attempt was something that was completely neutral

00:04:00.400 --> 00:04:02.879
to Babel or Polyglosia.

00:04:02.880 --> 00:04:06.199
and it was made basically for font Lattesch

00:04:06.200 --> 00:04:08.839
although some of the things can for rural Lattesch

00:04:08.840 --> 00:04:14.279
and some of the things can also be used with the latest.

00:04:14.280 --> 00:04:16.519
So overriding template fonts

00:04:16.520 --> 00:04:21.279
and taking into account pullback fonts

00:04:21.280 --> 00:04:23.839
was something that I learned uh uh

00:04:23.840 --> 00:04:27.959
when we started this conversation

00:04:27.960 --> 00:04:29.839
and the only problem with this

00:04:29.840 --> 00:04:34.799
is that fallback fonts only work for latex

00:04:34.800 --> 00:04:40.679
and because uh because it doesn't support them

00:04:40.680 --> 00:04:42.439
actually for fallback points is a lua feature

00:04:42.440 --> 00:04:45.319
There was already something in the list

00:04:45.320 --> 00:04:48.399
regarding script detection which helped me a lot.

00:04:48.400 --> 00:04:52.399
So big recognition to Romano Lafias for that

00:04:52.400 --> 00:04:57.679
and for his publishing the algorithm or the script

00:04:57.680 --> 00:05:04.399
and the in the org mode mailing list.

00:05:04.400 --> 00:05:11.319
And then came my sort of little nightmare,

00:05:11.320 --> 00:05:13.879
which was when we started talking

00:05:13.880 --> 00:05:17.359
about internationalization or localization.

00:05:17.360 --> 00:05:21.599
Looking back, I have a very strange feeling

00:05:21.600 --> 00:05:22.919
about a blurring target there.

00:05:22.920 --> 00:05:29.679
Because the reality being very, very frank, did I need it?

00:05:29.680 --> 00:05:34.919
Really no, because I just needed

00:05:34.920 --> 00:05:39.999
to add Spanish with Babel and that was it.

00:05:40.000 --> 00:05:43.199
Well actually for me it still is

00:05:43.200 --> 00:05:46.519
and you can put the British, German or Italian

00:05:46.520 --> 00:05:48.359
it continues to be true for me

00:05:48.360 --> 00:05:51.839
so I had personally I had little interest in doing that

00:05:51.840 --> 00:05:55.319
but I took it as a challenge

00:05:55.320 --> 00:06:02.479
which has shown to be really tough.

00:06:02.480 --> 00:06:05.799
What do you get from the feature branch? The feature branch

00:06:05.800 --> 00:06:08.999
adds font management for font spec,

00:06:09.000 --> 00:06:10.839
which is not strictly needed

00:06:10.840 --> 00:06:16.079
when you are on Latin, Cyrillic, and Greek scripts

00:06:16.080 --> 00:06:20.599
as long as the fonts in your template support them.

00:06:20.600 --> 00:06:28.799
But again, it's a nice way to get better support here.

00:06:28.800 --> 00:06:33.039
You don't need it if you're happy with the fonts you get

00:06:33.040 --> 00:06:38.439
from the templates that you use both for Beamer

00:06:38.440 --> 00:06:40.359
and the document classes in LaTeX.

00:06:40.360 --> 00:06:43.639
If you don't want to use alternative fonts,

00:06:43.640 --> 00:06:47.999
you don't need it, but you would need it.

00:06:48.000 --> 00:06:50.639
Of course, if you don't want things like,

00:06:50.640 --> 00:06:55.719
for example, emojis or need emojis,

00:06:55.720 --> 00:06:59.359
you really don't need forward fonts.

00:06:59.360 --> 00:07:03.959
So my idea is that the next thing that you can add

00:07:03.960 --> 00:07:07.319
is Babel and Polyglos here

00:07:07.320 --> 00:07:13.079
for enhanced localization and multilingual documents there.

00:07:13.080 --> 00:07:17.799
And at the end, my vision was that the keywords involved

00:07:17.800 --> 00:07:19.799
would be language, the main language.

00:07:19.800 --> 00:07:23.039
And then a nice idea from Ihor

00:07:23.040 --> 00:07:27.199
was to put all the secondary languages there too.

00:07:27.200 --> 00:07:30.559
Then specify the LaTeX compiler

00:07:30.560 --> 00:07:32.639
and then what I've added is a keyword

00:07:32.640 --> 00:07:34.279
which is LaTeX Montylang

00:07:34.280 --> 00:07:37.879
which can be fontspec or babel or polyglossia

00:07:37.880 --> 00:07:40.319
for localized documents.

00:07:40.320 --> 00:07:45.359
By default, this thing is nil and when it is nil,

00:07:45.360 --> 00:07:51.719
you get the behavior from OrgBug

00:07:51.720 --> 00:07:56.559
that you already are used to if you don't want to switch.

00:07:56.560 --> 00:08:00.559
and I was there and I was really

00:08:00.560 --> 00:08:03.479
was chirped into the conversation

00:08:03.480 --> 00:08:06.799
and I'm really helpful and a big thanks to him

00:08:06.800 --> 00:08:09.199
because he also had a an easy idea

00:08:09.200 --> 00:08:13.079
to support Chinese and Japanese documents

00:08:13.080 --> 00:08:17.239
so that the only thing that you need is to add the language

00:08:17.240 --> 00:08:19.879
that you're going to write your document in

00:08:19.880 --> 00:08:23.639
very very big thank you for that

00:08:23.640 --> 00:08:25.399
because that was really a challenge

00:08:25.400 --> 00:08:29.279
not being able to decipher

00:08:29.280 --> 00:08:32.639
what I was what I was coding there

00:08:32.640 --> 00:08:34.439
in terms of I have a document

00:08:34.440 --> 00:08:37.519
I copy and paste it from some place

00:08:37.520 --> 00:08:40.039
and from there I get my answer I get my my pdf

00:08:40.040 --> 00:08:47.279
and I compare whether it is correct or not

00:08:47.280 --> 00:08:50.239
So what is behind the scenes?

00:08:50.240 --> 00:08:52.959
I've always suggested that in order

00:08:52.960 --> 00:08:55.239
to use the feature branch efficiently

00:08:55.240 --> 00:08:59.919
you create a file with the default values

00:08:59.920 --> 00:09:02.439
you need for your variables

00:09:02.440 --> 00:09:06.199
and that's the this famous.locals.el files.

00:09:06.200 --> 00:09:10.239
What I do is I have a generic one

00:09:10.240 --> 00:09:12.079
in my home documents directory

00:09:12.080 --> 00:09:16.599
and this is used for all the org documents

00:09:16.600 --> 00:09:20.559
that are in subdirectories from there.

00:09:20.560 --> 00:09:24.039
Why? Because normally you will not be

00:09:24.040 --> 00:09:26.599
changing your fonts that often.

00:09:26.600 --> 00:09:29.599
and if you need you can always go

00:09:29.600 --> 00:09:33.479
and have your configuration locally.

00:09:33.480 --> 00:09:38.639
So it's this point where I'm collecting

00:09:38.640 --> 00:09:40.759
my phone configuration and

00:09:40.760 --> 00:09:47.519
For me, this gives me a very, very nice quick start

00:09:47.520 --> 00:09:49.639
for new documents and presentations.

00:09:49.640 --> 00:09:54.639
And there you can even configure a lot of compiler

00:09:54.640 --> 00:09:57.919
and font language management too,

00:09:57.920 --> 00:10:00.919
so you have everything in a file.

00:10:00.920 --> 00:10:04.759
And the other nice thing for that

00:10:04.760 --> 00:10:08.479
is that you can also include that in a subdirectory.

00:10:08.480 --> 00:10:13.199
And if this subdirectory is something that you're sharing

00:10:13.200 --> 00:10:14.479
in a project with other people,

00:10:14.480 --> 00:10:17.759
you are already configuring the, say,

00:10:17.760 --> 00:10:23.559
quote, unquote, corporate look and feel for your documents

00:10:23.560 --> 00:10:26.079
in that project for everyone

00:10:26.080 --> 00:10:28.919
and no one else has to care about

00:10:28.920 --> 00:10:35.119
how this document has to be configured.

00:10:35.120 --> 00:10:38.679
One of the things that I really like in this approach

00:10:38.680 --> 00:10:40.439
is that it is a grow-as-you-go.

00:10:40.440 --> 00:10:44.079
So, for example, you can start with something like that,

00:10:44.080 --> 00:10:48.439
which is I have my fonts, my basic fonts for main,

00:10:48.440 --> 00:10:51.479
which is the Serif font, for sans,

00:10:51.480 --> 00:10:54.079
which is the Sans Serif font, for maths,

00:10:54.080 --> 00:10:58.639
and for the mono, with some features like to make them scale.

00:10:58.640 --> 00:11:02.679
This is something that is uh provided by you

00:11:02.680 --> 00:11:05.359
through the font spec package

00:11:05.360 --> 00:11:08.959
and you're happy with it and you work with it

00:11:08.960 --> 00:11:11.919
and given a in a given moment

00:11:11.920 --> 00:11:14.439
you go and you have your own problems

00:11:14.440 --> 00:11:16.599
and or your own challenge

00:11:16.600 --> 00:11:20.279
and you need to have for example emojis for one of the fonts

00:11:20.280 --> 00:11:24.959
and what you do is in this case you just add the emojis

00:11:24.960 --> 00:11:31.239
as a fallback font in in the font that where you want to replace this

00:11:31.240 --> 00:11:36.119
is this is what i'm doing right now for this presentation and you will see

00:11:36.120 --> 00:11:39.119
You can always, as I've said,

00:11:39.120 --> 00:11:42.359
you can always have your dear locals

00:11:42.360 --> 00:11:46.319
and you can copy that into a working directory

00:11:46.320 --> 00:11:49.439
which needs special adaptations or has special needs

00:11:49.440 --> 00:11:54.119
and from there you have that directory

00:11:54.120 --> 00:11:59.079
with your modified or customized their local study l file

00:11:59.080 --> 00:12:05.439
so font spec is normally enough

00:12:05.440 --> 00:12:09.999
but sometimes you can't control all the fonts

00:12:10.000 --> 00:12:15.479
with font spec only so and there you have a polyglot here

00:12:15.480 --> 00:12:19.319
and babel coming to your help

00:12:19.320 --> 00:12:21.359
this may also be the case

00:12:21.360 --> 00:12:25.879
that you are working in an intended language

00:12:25.880 --> 00:12:28.959
i don't know which but an intended language and you found

00:12:28.960 --> 00:12:31.279
and you wanted to see how that was configured

00:12:31.280 --> 00:12:34.999
and you found the latest example

00:12:35.000 --> 00:12:38.639
that used Babel or Polyglossia.

00:12:38.640 --> 00:12:42.559
The exporter provides you three variables

00:12:42.560 --> 00:12:48.679
to configure both font spec, Polyglossia and Babel.

00:12:48.680 --> 00:12:56.799
So just as an example of how I picture this is,

00:12:56.800 --> 00:12:59.359
uh, you find it in the internet,

00:12:59.360 --> 00:13:01.679
something like that, uh, something like this,

00:13:01.680 --> 00:13:05.599
because you have your document and you need tie.

00:13:05.600 --> 00:13:09.999
So, and I found an example in the internet

00:13:10.000 --> 00:13:12.679
that tells me that I'm going to be using

00:13:12.680 --> 00:13:15.079
Babel main is going to be English.

00:13:15.080 --> 00:13:17.919
And I'm also going to have a tie.

00:13:17.920 --> 00:13:22.879
and then they tell me that for english

00:13:22.880 --> 00:13:26.639
i'm going to be using noto serif for the main

00:13:26.640 --> 00:13:31.759
for the main of the serif font noto sans for the sans font

00:13:31.760 --> 00:13:35.799
and then when i'm writing things in thai

00:13:35.800 --> 00:13:40.119
i'm going to be using noto serif thai and noto sans thai

00:13:40.120 --> 00:13:42.399
That's what I see in the internet.

00:13:42.400 --> 00:13:47.159
So what you can always do, what you would do in this case,

00:13:47.160 --> 00:13:54.279
is I'm going to get and map the font configurations

00:13:54.280 --> 00:13:59.239
from the latest into this variable.

00:13:59.240 --> 00:14:03.479
Things that you have to take into account here

00:14:03.480 --> 00:14:05.919
is, for example, the language.

00:14:05.920 --> 00:14:11.919
The language here is Thai. You have the language

00:14:11.920 --> 00:14:16.759
that you're intending this font for is Thai.

00:14:16.760 --> 00:14:21.279
So this appears here. In case you don't have any language,

00:14:21.280 --> 00:14:24.799
like in the first two lines,

00:14:24.800 --> 00:14:27.239
you just say that the language is nil,

00:14:27.240 --> 00:14:31.439
which is the language for the default language.

00:14:31.440 --> 00:14:34.799
The other thing is in my example,

00:14:34.800 --> 00:14:40.039
in this example that I found in the internet,

00:14:40.040 --> 00:14:46.319
I have my properties for the fonts in this part in Latex

00:14:46.320 --> 00:14:52.239
and I put them as properties here.

00:14:52.240 --> 00:14:55.079
That's the whole idea behind the feature branch.

00:14:55.080 --> 00:15:03.119
The Babel provide part is also integrated

00:15:03.120 --> 00:15:10.119
from the Org header, mainly from the language line.

00:15:10.120 --> 00:15:14.639
We have a variable in case you need to tweak it,

00:15:14.640 --> 00:15:21.079
but normally the defaults provided by Org are good enough.

00:15:21.080 --> 00:15:27.679
So what is the rationale behind my take at Latex Fonts Management?

00:15:27.680 --> 00:15:31.359
And that's something that might be something very personal.

00:15:31.360 --> 00:15:33.759
When am I using FontSpec?

00:15:33.760 --> 00:15:37.239
I'm using FontSpec when I'm with Lua or Zlatex

00:15:37.240 --> 00:15:40.279
and I want fonts that are different

00:15:40.280 --> 00:15:42.439
from those specified in the Latex class.

00:15:42.440 --> 00:15:49.279
That's point number one. I will also go for font spec

00:15:49.280 --> 00:15:52.599
when I need to support scripts,

00:15:52.600 --> 00:15:54.559
but I'm missing in the fonts I use,

00:15:54.560 --> 00:15:59.479
and I can use fallback fonts for that. I have two.

00:15:59.480 --> 00:16:05.239
The only limitation I have here is the following.

00:16:05.240 --> 00:16:09.039
All languages must be left to right.

00:16:09.040 --> 00:16:12.799
And if you don't say anything at all,

00:16:12.800 --> 00:16:16.519
the LATIC backend assumes that you want the dates,

00:16:16.520 --> 00:16:19.159
standard names for the abstract and so on

00:16:19.160 --> 00:16:21.039
in American English. if you're using them.

00:16:21.040 --> 00:16:25.439
In many cases, you're not using any sort of

00:16:25.440 --> 00:16:32.319
abstract table of contents and so on

00:16:32.320 --> 00:16:37.239
and you don't need that.

00:16:37.240 --> 00:16:44.599
The important thing is maybe date management.

00:16:44.600 --> 00:16:50.399
If you need dates, headings

00:16:50.400 --> 00:16:56.919
or anything in any other language or locale,

00:16:56.920 --> 00:17:06.599
then yes, then you need to use Babel or Polyglosia.

00:17:06.600 --> 00:17:12.079
Choice, Depends. Can use poly loss here,

00:17:12.080 --> 00:17:15.639
or you can use Babel, whatever you want.

00:17:15.640 --> 00:17:20.079
Also, in some cases, it will depend

00:17:20.080 --> 00:17:21.839
if you've been researching a bit

00:17:21.840 --> 00:17:24.119
of how this is done with pure latest,

00:17:24.120 --> 00:17:25.999
it will be also depending on, uh,

00:17:26.000 --> 00:17:28.919
on the examples that you get.

00:17:28.920 --> 00:17:35.719
So, what can you, when you are using

00:17:35.720 --> 00:17:41.639
Babel or Polygross here, what do you have?

00:17:41.640 --> 00:17:46.239
You have your dates, your headings, and so on.

00:17:46.240 --> 00:17:48.279
You might need to control the text

00:17:48.280 --> 00:17:51.239
in the sense that what passage

00:17:51.240 --> 00:17:53.479
is written in what language.

00:17:53.480 --> 00:17:58.119
For example, for things like hyphenation

00:17:58.120 --> 00:18:01.919
and some ways of writing the hyphens in a

00:18:01.920 --> 00:18:12.039
and direct speech and things like that.

00:18:12.040 --> 00:18:17.359
And the other place where you need

00:18:17.360 --> 00:18:19.199
other Babel or polyglots here,

00:18:19.200 --> 00:18:24.559
and you will see that because all examples

00:18:24.560 --> 00:18:26.839
that you can get for later in this case

00:18:26.840 --> 00:18:30.679
is when you have a language

00:18:30.680 --> 00:18:38.199
that uses right to left alignment

00:18:38.200 --> 00:18:40.439
like Arabic, Hebrew and others.

00:18:40.440 --> 00:18:45.359
So One note of, I would say, care is you always use the,

00:18:45.360 --> 00:18:46.479
if you use Unicode fonts

00:18:46.480 --> 00:18:49.359
that includes the scripts as you need,

00:18:49.360 --> 00:18:51.759
you will have done, that will be a great leap for you

00:18:51.760 --> 00:18:53.759
because that simplifies the configuration a lot.

00:18:53.760 --> 00:18:55.359
Now a couple of demos.

00:18:55.360 --> 00:19:01.079
I don't know if you've noticed

00:19:01.080 --> 00:19:03.359
first demo is that I'm using.

00:19:03.360 --> 00:19:05.119
fonts but are not the official fonts

00:19:05.120 --> 00:19:06.399
in this Beamer template

00:19:06.400 --> 00:19:07.959
which is by the way Boadilla.

00:19:07.960 --> 00:19:10.519
This would be the first thing

00:19:10.520 --> 00:19:14.079
so I've been using other fonts

00:19:14.080 --> 00:19:17.639
and they are at least from what I get in class

00:19:17.640 --> 00:19:20.439
they are more readable than the official

00:19:20.440 --> 00:19:22.439
than the default fonts in Poliglossi

00:19:22.440 --> 00:19:24.439
that you get in Babel for the Boadilla theme.

00:19:24.440 --> 00:19:25.959
Another thing is what I've told you,

00:19:25.960 --> 00:19:27.559
I have my own things like emojis.

00:19:27.560 --> 00:19:29.799
Now, if you allow me for a second,

00:19:29.800 --> 00:19:38.399
I'm going to switch to the Emacs

00:19:38.400 --> 00:19:40.279
which is running behind the scenes to show you what.

00:19:40.280 --> 00:19:45.719
Okay, fine. So, this is the presentation.

00:19:45.720 --> 00:19:47.879
that I have here, and as you see,

00:19:47.880 --> 00:19:50.959
I'm using Lua Latex and just one spec.

00:19:50.960 --> 00:19:59.479
given I don't know why I would I would need this

00:19:59.480 --> 00:20:01.079
this is an English presentation

00:20:01.080 --> 00:20:03.039
but just to show you what you can do

00:20:03.040 --> 00:20:09.359
if I go back here and I go to the beginning of the presentation

00:20:09.360 --> 00:20:13.159
and now what I don't think you're showing anything oh thank you

00:20:13.160 --> 00:20:21.399
Okay, this is the presentation, right?

00:20:21.400 --> 00:20:33.559
So what I'm going to do is I'm going to go back

00:20:33.560 --> 00:20:35.839
and I'm going to show the full screen.

00:20:35.840 --> 00:20:37.199
And in this full screen,

00:20:37.200 --> 00:20:41.919
you see the presentation on one side

00:20:41.920 --> 00:20:46.079
and you see Emacs on the other side. Oh, still nothing.

00:20:46.080 --> 00:20:50.279
Yeah, we're not seeing your screen at the moment, sorry.

00:20:50.280 --> 00:20:54.079
Oh, thank you. Thank you for that.

00:20:54.080 --> 00:20:59.959
Now it's starting to come. Okay. Yay! Fine.

00:20:59.960 --> 00:21:03.479
So this presentation, I've done it with Lua Latex,

00:21:03.480 --> 00:21:05.839
and what I add here is font spec and English language.

00:21:05.840 --> 00:21:10.279
Just to show you, but with the same configuration,

00:21:10.280 --> 00:21:14.279
with the same font spec configuration,

00:21:14.280 --> 00:21:15.439
but adding Polyglossia.

00:21:15.440 --> 00:21:23.159
I just have enough with adding polygons here

00:21:23.160 --> 00:21:28.799
with the Spanish language to get my dates correctly

00:21:28.800 --> 00:21:32.559
and this is something I'm going to see the date in English

00:21:32.560 --> 00:21:46.719
and if I now go and recompile it in a couple of seconds

00:21:46.720 --> 00:21:48.999
you will see that the data is in Spanish.

00:21:49.000 --> 00:21:53.879
We are using the same Which I can show by the way.

00:21:53.880 --> 00:21:58.079
I see just by adding polyglyphs here.

00:21:58.080 --> 00:21:59.439
I can get my dates in Spanish.

00:21:59.440 --> 00:22:09.559
What I have included the the locals in the.

00:22:09.560 --> 00:22:14.999
In this in this lines, but just to discuss it a bit more.

00:22:15.000 --> 00:22:19.439
I have it for all the presentations.

00:22:19.440 --> 00:22:24.319
I think it was here. No. For the demo.

00:22:24.320 --> 00:22:27.719
For the presentations I use for MX conferences.

00:22:27.720 --> 00:22:31.119
I have it and it's something like this.

00:22:31.120 --> 00:22:37.359
actually you don't need a fallback

00:22:37.360 --> 00:22:39.439
for for the main font here

00:22:39.440 --> 00:22:44.239
because the presentations are done with the sans font

00:22:44.240 --> 00:22:46.559
so the only thing that I would really need

00:22:46.560 --> 00:22:48.199
would be something like this

00:22:48.200 --> 00:22:53.359
this can be commented and the same happens here

00:22:53.360 --> 00:22:56.159
with the model this can be also commented

00:22:56.160 --> 00:23:00.399
and the only thing where I would really need

00:23:00.400 --> 00:23:02.119
a full back font is here

00:23:02.120 --> 00:23:04.319
and what this is telling me is that

00:23:04.320 --> 00:23:07.079
you have a full back for the emoji

00:23:07.080 --> 00:23:09.799
for the emoji script

00:23:09.800 --> 00:23:15.399
and you need to use the apple color emoji font with A modifier

00:23:15.400 --> 00:23:18.759
which in this case is that you need

00:23:18.760 --> 00:23:21.359
to have the half-word renderer.

00:23:21.360 --> 00:23:24.599
That's the only thing that you really need.

00:23:24.600 --> 00:23:26.679
Where do I get all these things from?

00:23:26.680 --> 00:23:29.039
All these things I get from the different parts

00:23:29.040 --> 00:23:32.079
and from different scripts in the Internet.

00:23:32.080 --> 00:23:38.039
I also have a couple of other things to show.

00:23:38.040 --> 00:23:42.919
For example, first of all, I do not need this.

00:23:42.920 --> 00:23:44.749
This is a letter that I've been writing this morning

00:23:44.750 --> 00:23:55.640
and I'm not using the full feature branches at all

00:23:55.641 --> 00:23:58.119
because I just needed a sans font

00:23:58.120 --> 00:24:02.119
and it's going to be a letter that I'm writing in.

00:24:02.120 --> 00:24:06.119
with the sans font and the only thing I need

00:24:06.120 --> 00:24:09.119
was Spanish for the date anyhow

00:24:09.120 --> 00:24:14.719
how did what was my first thing that I did

00:24:14.720 --> 00:24:19.639
with the back end back in I think it was April

00:24:19.640 --> 00:24:23.079
we had a this comes from the mailing list

00:24:23.080 --> 00:24:26.759
we had someone who had this who had this problem right

00:24:26.760 --> 00:24:29.559
and he wanted to add emojis

00:24:29.560 --> 00:24:33.039
and he had problems with the verbatim font

00:24:33.040 --> 00:24:35.279
And that's how everything got started.

00:24:35.280 --> 00:24:42.599
If you now go and I get my period

00:24:42.600 --> 00:24:44.599
of latex for that running.

00:24:44.600 --> 00:24:50.559
Well, I actually, all my latex is supported for that.

00:24:50.560 --> 00:24:58.119
And this was what I showed in one of the Emacs, Org Mode meetups.

00:24:58.120 --> 00:25:00.079
And there you see that We have the emojis.

00:25:00.080 --> 00:25:06.879
We had the fonts for the different things. We had maps.

00:25:06.880 --> 00:25:13.799
And you could even go and add scripts

00:25:13.800 --> 00:25:16.319
and little passages and different scripts.

00:25:16.320 --> 00:25:22.359
And this was done with the same principles that I want.

00:25:22.360 --> 00:25:25.439
I have my main font. I have the emojis.

00:25:25.440 --> 00:25:30.559
and I want, I have my son's phone and I have the emojis,

00:25:30.560 --> 00:25:32.959
the Han for Japanese and the Kana for Japanese,

00:25:32.960 --> 00:25:36.799
so that these characters here,

00:25:36.800 --> 00:25:40.679
both in the sons and in the serif passages

00:25:40.680 --> 00:25:44.399
are included correctly in the PDF.

00:25:44.400 --> 00:25:49.999
And a third thing of what you can do

00:25:50.000 --> 00:25:53.439
I've also shown this so this is more

00:25:53.440 --> 00:25:55.799
for people who have not seen it

00:25:55.800 --> 00:26:01.399
this is a side-by-side package a passage of

00:26:01.400 --> 00:26:04.919
well actually the beginning of the analysis by Xenophon

00:26:04.920 --> 00:26:12.919
both in in Greek and in German with some comments

00:26:12.920 --> 00:26:18.679
and if I go this is this is done with Polyglossia

00:26:18.680 --> 00:26:25.279
so if I go once again and produce

00:26:25.280 --> 00:26:32.039
the PDF for this just a second

00:26:32.040 --> 00:26:41.119
Come on. There you are. You get this.

00:26:41.120 --> 00:26:46.399
And there you see different fonts.

00:26:46.400 --> 00:26:48.239
Which fonts am I using for this?

00:26:48.240 --> 00:26:51.279
I'm using for the main font for me is Swissere.

00:26:51.280 --> 00:27:01.479
This listing is produced with Deja Vu Sansponor.

00:27:01.480 --> 00:27:13.359
And using Polyglos here, I'm able to go and define

00:27:13.360 --> 00:27:15.799
the Greek polytone for the variant,

00:27:15.800 --> 00:27:18.799
for the Serif variant with the Noto Serif font,

00:27:18.800 --> 00:27:26.199
just to differentiate it from the German text.

00:27:26.200 --> 00:27:30.279
And nice thing is that both in the German text

00:27:30.280 --> 00:27:37.359
You see for example here and with the Greek text

00:27:37.360 --> 00:27:40.879
everything is scaled to match

00:27:40.880 --> 00:27:44.119
the lower case of the main font which is free serif.

00:27:44.120 --> 00:27:45.879
So that everything looks

00:27:45.880 --> 00:27:49.359
extremely uniform and nice to read.

00:27:49.360 --> 00:27:53.759
So that's what you want to do.

00:27:53.760 --> 00:27:56.519
That's what you can do with this.

00:27:56.520 --> 00:28:00.759
Just a couple of final words on this.

00:28:00.760 --> 00:28:17.519
I want to thank once again Juan Manuel Garcia and Jim Crump

00:28:17.520 --> 00:28:19.919
for what they have shared.

00:28:19.920 --> 00:28:24.079
And I also want to thank everybody

00:28:24.080 --> 00:28:26.479
for productive contributions to the discussion.

00:28:26.480 --> 00:28:32.159
I'm saying this because I think I need a longer rest

00:28:32.160 --> 00:28:34.839
and I'm going to be leaving

00:28:34.840 --> 00:28:38.559
the feature fund untouched for a couple of months

00:28:38.560 --> 00:28:41.719
so that people can take the feature branch

00:28:41.720 --> 00:28:43.519
untouched for a couple of months.

00:28:43.520 --> 00:28:47.599
to see if people want to use it and how they want to use it

00:28:47.600 --> 00:28:49.919
and then maybe in the future we can discuss

00:28:49.920 --> 00:28:52.559
if we want to integrate it or not

00:28:52.560 --> 00:28:58.839
or if people need it and all that. Now questions, comments?

00:28:58.840 --> 00:29:41.279
I think there was one question on. Beautiful for.

00:29:41.280 --> 00:29:47.119
I think that goes beyond fonts right.

00:29:47.120 --> 00:29:52.839
Someone is asking what about how is about video

00:29:52.840 --> 00:29:56.319
mainly MP4 support on ox-latex.

00:29:56.320 --> 00:29:58.799
I started the presentations with many videos.

00:29:58.800 --> 00:30:07.839
This is something that really pushed me back using ox-latex.

00:30:07.840 --> 00:30:18.799
What I would say to this is I mean this goes beyond

00:30:18.800 --> 00:30:24.319
what we're discussing here with fonts.

00:30:24.320 --> 00:30:29.319
I would advise you to go and get the same

00:30:29.320 --> 00:30:35.239
or have the same thing that I did

00:30:35.240 --> 00:30:39.119
which was first of all try to write it in latex

00:30:39.120 --> 00:30:49.599
and then Once you have the minimal working examples,

00:30:49.600 --> 00:30:53.159
you can get the latest parts

00:30:53.160 --> 00:30:58.159
integrated into your own presentation.

00:30:58.160 --> 00:31:01.319
That's what I've been doing.

00:31:01.320 --> 00:31:04.519
By the way, I still do it, for example, not in this,

00:31:04.520 --> 00:31:06.079
but for my lectures,

00:31:06.080 --> 00:31:09.119
I have a lot of I'm using a lot of ticks

00:31:09.120 --> 00:31:12.479
to do graphs and animated graphs.

00:31:12.480 --> 00:31:18.319
And that's begin export later and export later.

00:31:18.320 --> 00:31:20.159
That's what I'm doing.

00:31:20.160 --> 00:31:28.999
Videos are generally a bit tricky because you cannot

00:31:29.000 --> 00:31:35.119
So I think there is something called PDF-PC that can,

00:31:35.120 --> 00:31:37.399
this provides a lot of cloud package

00:31:37.400 --> 00:31:39.079
where you can include videos

00:31:39.080 --> 00:31:44.399
and then they can be played through that specific program.

00:31:44.400 --> 00:31:46.239
And JavaScript embedding,

00:31:46.240 --> 00:31:49.999
that can only be done through Acrobat Reader,

00:31:50.000 --> 00:31:54.519
which is like also finicky. Sure, yes.

00:31:54.520 --> 00:32:03.999
As you said there are many things that need to be changed.

00:32:04.000 --> 00:32:07.199
But I mean it's always a thing of taking it

00:32:07.200 --> 00:32:11.359
and trying to see what you can do

00:32:11.360 --> 00:32:13.319
and what the specifics are.

00:32:13.320 --> 00:32:17.079
Maybe this can be done with Acrobat

00:32:17.080 --> 00:32:23.959
and with a couple of extra packages and who knows.

00:32:23.960 --> 00:32:26.359
And you can always keep it as as late

00:32:26.360 --> 00:32:34.599
as fragments inside Org, I think. Any other questions?