Pedro Andres Aranda Gutierrez <paag...@gmail.com> writes:
>> 1. We introduce org-latex-fontsets variable that will hold pre-defined
>> set of fonts that we ship with Org mode.
>
> I see a small disadvantage in defining font sets in a generalised way,
> which I'm experiencing in my multi-OS and which was pointed out earlier.
> Sometimes fonts are not there. If we follow this path, people may need to
> install fonts they don't like/use/...
We need to choose some fonts as default anyway, right?
In any case, allowing to set fonts directly has to be there as the first step.
>> I see. So, "emoji", "han", and "kana" are the character sate names
>> internally used by Emacs, right? In this case, I think that we may also
>> want some kind of generic fallback; not just for specific character sets
>> (which is "unicode" charset as per 34.7 Character Sets section of Elisp
>> manual)
>>
> That "fallback" should be covered by the \set...font{}, right?
Ok. So those are latex's not Emacs's.
> An extra-thought for pdflatex.
> I'm intentionally leaving it out of the conversation, because it is another
> pair of shoes.
> My use case doesn't include LaTeX preview FTMB, so it is centered on UTF-8
> solutions with (lua|se)latex.
> That's also the reason why:
> 1.- I'm calling the control variable(s) after the packages they configure
> (i.e. fontspec and polyglossia)
> 2.- The code specifically returns an empty string if (equal compiler
> "pdflatex")
No problem. I just pointed that there is preliminary work on pdflatex we
can refer to.
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
