Answers inline, /PA On Sat, 22 Nov 2025 at 10:16, Ihor Radchenko <[email protected]> wrote:
> Pedro Andres Aranda Gutierrez <[email protected]> writes: > > > I'm getting a bit worried that this conversation is going in circles that > > only delay the real target, which should be having an alternative support > > for font configuration in ox-latex.el... > > > > Let me recap what has happened so far: > > ... > > Now, let's try a completely different approach to explaining the > > variables... > > ... > > Then you create your variable. In this case, as a loval variable, you can > > go for > > > > # org-latex-babel-font-config: '((nil :fonts (("rm" :font > > "NewComputerModern10")))) > > ... > > We are on the same page here. > OK > > The org-latex-... variables I have included (hopefully) make it easy to > map > > what you see in the manuals and in this and other sites to your needs. > > (At least easier than writing the whole stuff in LaTeX). > > My point is that I still believe that we can make the variables easier > to use. Recall that I first raised this topic in > https://list.orgmode.org/orgmode/87y0pxwpwo.fsf@localhost/ > We postponed that discussion at that time, and I am bringing it back > now, as I believe that we need to finish it before merging the branch. > N/C... > Before putting more concrete proposals on simplification, I would like > to make sure that I have a clear understanding about similarities and > differences between fontspec, polyglossia, and babel for font setup. As > of now, I feel that the font configuration has a lot in common: we have > default fonts per each script type, and we may have per-language fonts. > It has, but the details matter and <IMvvHO>should be highlighted</IMvvHO> There are differences, but I'd like to figure out if we really need to > map every single feature of polyglossia/babel into variables exposed to > Org users. > And don't remember people coming from LaTeX. If we put too many restrictions to them, they will not use this at all. And that <IMvvHO>would be a pity<(IMvvHO> As of now, for me, it looks like we do not need a special configuration > for default fonts for babel. Instead, we can simply use fontspec > defaults (babel falls back to them by default). > <WARNING>Most examples you can look up will not follow this pattern.</WARNING> That is (at the very least) confusing for most people... An example: https://github.com/latex3/babel/blob/main/samples/lua-polygreek.tex Further examples: the rest of that directory (and I have not looked at the official polyglossia examples) <IMvvHO>I have kept close to what is out there, not to confuse people</IMvvHO>. Further, :tag in polyglossia does not seem necessary. We should be > perfectly fine if we do not expose this feature to Org users. > Since that is secondary, I could concede, leaving it commented as a FIXME (FFS) . I wouldn't complete rule it out in the (perfect) future. Finally, it looks like we do not have to force users specifying > individual fonts for each rm/sf/tt script for babel. We can provide > default per-language font just as we do for polyglossia. > Here you may have misunderstood. You do not need the full spectrum, OK. But you still need to differenciate: Not providing the "sf" font and then using \textsf{} or setting the default font to \sfdefault will be cause of trouble, either as a non-intended presentation, missing characters or as errors in the compilation process. Thus, allowing for explicitly setting rm/sf/tt is needed. I'd be more cautious here. My understanding to contrast > With the above 3 points, font configuration will become more uniform: > 1. fontspec-config will set the defaults when per-language setting is > not provided + fallbacks for lualatex. > fontspec-config provides the font overrides for lualatex and xelatex. Additionally lualatex can do fallbacks. It can be used with babel and polyglossia. But it is not a _MUST_ and we shouldn't impose it. 2. polyglossia-config and babel-config will provide the same set > features - per-language font settings, optionally also specifying > language + script combinations. Then, the value formats for > polyglossia-config and babel-config can be made the same, reducing > the learning barrier. > My main concern with your understanding here is that you seem to be ruling out a babel-only or a polyglossia only configuration. What I could try is to explore using the same ((<lang> . (('rm' :font '<fname>' ...) ('sf' :font '<fname>' ...)))) scheme for polyglossia and babel and then see which properties are common and which are not. My earnest concern here is that people could try to add babel-specific properties in a polyglossia configuration or viceversa. But if you could live with that, it would be OK for me. > -- > 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> > /PA -- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler "Sagen's Paradeiser" (ORF: Als Radiohören gefährlich war) => write BE! Year 1 of the New Koprocracy
