I had forgotten the list... sorry. To add to the message, I scan the buffer
for charsets using a variant of the code proposed by Juan Manuel Macías
some time ago...
Sorry and Best, /PA
---------- Forwarded message ---------
From: Pedro Andres Aranda Gutierrez <paag...@gmail.com>
Date: Sun, 20 Apr 2025 at 15:34
Subject: Re: [PATCH]: Add font specifications when exporting to LaTeX
To: Ihor Radchenko <yanta...@posteo.net>
PS: I'm progressing with the font header generation:
The font configuration is done in two variables:
(defvar org-latex-font-mapping-alist
'(("main" . "Noto Serif")
("sans" . "Noto Sans")
("mono" . "Noto Sans Mono"))
"Set this alist for your font preferences when exporting to
LuaLaTeX/XeTeX.
. Initially, this will generate a list of strings, each one an expansion
like:
\=\set...font{font name}")
(defvar org-latex-font-fallback-alist
'(("emoji" . "Noto Color Emoji:mode-harf")
("han" . "Noto Sans CJK JP:")
("kana" . "Noto Sans CJK JP:"))
"Set this alist with your fallback fonts definitions when exporting to
LuaLaTeX/XeTeX.
This will be merged with the charset-font list generated when scanning the
document
and placed in the header in a directlua block.")
It's quite close to pandoc, but much more flexible (they don't consider
\setromanfont{}, which this setup
would allow).
I know I'm working with the Noto fonts and some people will scream, but
this should end up by being a couple of
defcustoms with something reasonable and documentation to help people set
up their environment.
And with this and some code, I generate
\directlua{
luaotfload.add_fallback("FallbackFonts", {
"Noto Color Emoji:mode-harf",
})
}
\setmainfont{Noto Serif}[RawFeature=Fallbackfonts]
\setsansfont{Noto Sans}[RawFeature=Fallbackfonts]
\setmonofont{Noto Sans Mono}[RawFeature=Fallbackfonts]
from an org buffer with UTF-8 and emojis.
Still a couple of weeks of work, now that we are at the end of the lecture
season here and we will start exams,
but this looks like a starting point for me.
WDYT, /PA
On Sun, 20 Apr 2025 at 15:24, Pedro Andres Aranda Gutierrez <
paag...@gmail.com> wrote:
> Hi,
>
> On Sun, 20 Apr 2025 at 13:51, Ihor Radchenko <yanta...@posteo.net> wrote:
>
>>
>> (Note that another option could be you creating a new git feature branch
>> and accumulating commits there. Then, you can put NEWS entry after a
>> series of commit, summarizing all the changes. We can merge that branch
>> after it is finished.)
>>
>> I remember that it was not easy to get git commit access. Could you
> please help me with that,
>
> Thx, /PA
> --
> Fragen sind nicht da, um beantwortet zu werden,
> Fragen sind da um gestellt zu werden
> Georg Kreisler
>
> Sagen's Paradeiser, write BE!
> Year 1 of the New Koprocracy
>
>
--
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Sagen's Paradeiser, write BE!
Year 1 of the New Koprocracy
--
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Sagen's Paradeiser, write BE!
Year 1 of the New Koprocracy
