Hi, I see and I'm struggling to find a better approach for this. At this point, font management seems more tailored to people like myself, coming from a LaTeX world and regaining the control over my fonts without having to write a lot either in the LATEX_HEADER or in an extra .tex file to include.
A person "new" to this would have to resort to the manual of the backend [sz]?he chooses in the document to understand what can and what can't be done. My approach was to make it reasonably easy to map from the examples in the polyglossia/babel manuals to the configuration. Best, /PA On Sat, 27 Sept 2025 at 13:28, Ihor Radchenko <[email protected]> wrote: > > Pedro Andres Aranda Gutierrez <[email protected]> writes: > > > Let me see if I understand... in the example shared, we would replace > > ... > > with > > ``` > > (org-latex-babel-font-config > > . (("el-polyton" > > :fonts (("rm" :font "Noto Serif"))) > > (nil > > :fonts (("rm" :font "CMU Serif") > > ("sf" :font "Noto Sans") > > ("tt" :font "DejaVu Sans Mono" :props > > "Scale=MatchLowercase"))))))) > > Yes, but not exactly. > > > so that it matches with > > ``` > > (org-latex-polyglossia-font-config > > . (("el" :font "Noto Serif" :props "Script=Greek"))) > > What I am looking at is > > (org-latex-polyglossia-font-config . (("el" :font "Noto" :variant "tt"))) > > vs. > > (org-latex-babel-font-config . (("el" :fonts (("tt" :font "Noto))))) > > As you can see from the example, font variant definitions are currently > not the same. It may be confusing for users not familiar with > babel/polyglossia. > > -- > 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> -- 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
