Let me see if I understand... in the example shared, we would replace
```
(org-latex-babel-font-config
. (("el-polyton"
:fonts (("rm" . "Noto Serif")))
(nil
:fonts (("rm" . "CMU Serif")
("sf" . "Noto Sans")
("tt" . ("DejaVu Sans Mono" "Scale=MatchLowercase")))))))))
```
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")))))))
```
so that it matches with
```
(org-latex-polyglossia-font-config
. (("el" :font "Noto Serif" :props "Script=Greek")))
```
In all cases, :props is either a string or a list of strings. It could
make sense... if that is want you mean.
It would be more verbose, but it would make it easier for non LaTeX
people to transpose the manual to their configurations...
Waiting for confirmation, /PA
On Mon, 28 Jul 2025 at 19:48, Ihor Radchenko <yanta...@posteo.net> wrote:
>
> Pedro Andres Aranda Gutierrez <paag...@gmail.com> writes:
>
> >> I am also wondering if we can unify this variable with
> >> `org-latex-polyglossia-font-config' and `org-latex-babel-font-config'.
> >
> > I'd rather keep them apart. The mechanics are different, the font options
> > too.
> > A unification may have result in people using the wrong options for
> > the LaTeX package they intend to use.
> > Let's spare a couple pain-killers ;-)
>
> What about at least keeping the value format the same?
>
> --
> 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
