Pedro Andres Aranda Gutierrez <[email protected]> writes:
> From what I read you would prefer to have fonts as the keyword.
> However that goes _against_ the philosophy of *all* LaTeX packages (and
> compilers) I'm trying to handle.
> They all map LaTeX font families and/or a human languages to system font
> files.
Let me explain my logic. I am not coming from LaTeX at all.
I am coming from a simple thinking: I have an org file to be exported to
pdf (by whatever means). I need to specify font for that file.
So, I want to do (setq org-latex-<something> "My font") or even
#+LATEX_FONT: My font. I was hoping that we may (at least sometimes)
avoid setting individual fonts for main/sans/mono/math. That's why I
found ("family" :font "name") construct awkward - if family may be
omitted, then (nil :font "name") is worse than simple ("name").
I am now digging into the topic again, and it looks like regardless of
fontspec/polyglossia/babel, we *must* specify main/sans/mono/math fonts
separately. There is theoretically
% If the font has sans and mono variants, this may work automatically
\setmainfont{TeX Gyre Termes}[
UprightFont = *-Regular,
BoldFont = *-Bold,
ItalicFont = *-Italic,
BoldItalicFont = *-BoldItalic,
% Sans and mono variants would be auto-detected if they exist
]
but that is not recommended and is not universal.
Somehow, I thought that we may get along with a single font for
main/sans/mono for polyglossia via
\newfontfamily\greekfont{⟨font⟩}
However, after more research, it looks like \greekfont is simply an
equivalent of \setmainfont, so it does not do anything about sans/mono,
which need to be specified regardless.
Can we modify the manual, saying upfront both for font configuration and
per-language font configuration that user MUST specify 3-4 font
variants: main, sans, mono, and (maybe) math?
> And for the script is it approx. the same... Our example translates to
> "human" as:
>
> If Emacs finds an emoji, load "noto color emoji" and delegate to lualatex
> to see if that contains the missing character.
> The extra property there (mode=harf) tells lualatex to use the HarfBuzz
> renderer for glyphs contained in this font file if they are needed.
> Which, I think, is easier to understand.
I have no problem with mode=harf. (I am not sure what is the
disagreement about font features/properties).
Where I do have slight problem is "emoji" (or other script
name). Consider
("math" :font "Stix Two Math")
("main" :font "FreeSerif"
:fallbacks (("mathematical" "Noto Serif")))
Isn't math/mathematical confusing?
> PS: Look at the latest commits in the feature branch. I hope they clarify
> your doubts a bit more.
Commit c2ba3fe72 is a mess. You somehow moved inline footnotes from
non-latex sections into numbered footnotes. Also, I see changes like
-#+texinfo: @noindent
+# +texinfo: @noindent
that have no clear purpose (accidental?)
Then, there is
+[fn:48] DEFINITION NOT FOUND.
??
Please consider reverting and re-applying changes cleanly.
--
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>
