I don’t dare to touch that, because lots of the legacy code may depend on it and that would mean breaking existing behaviour.
/PA Enviado desde mi iPhone > El 24 nov 2025, a las 18:57, Ihor Radchenko <[email protected]> escribió: > > Pedro Andres Aranda Gutierrez <[email protected]> writes: > >> I have just pushed a series of commits that (hopefully) show the rationale >> behind :tag, which I have renamed to :script, in order to avoid confusion. >> Unfortunately, the information in org-latex-language-alist doesn't seem >> appropriate to cover all cases auto-magically: >> >> All languages using Latin script can't use :script, specifically if you >> want to use different fonts for different languages. In this case you can >> to revert to :polyglossia. >> I have opted for :polyglossia and introduced the :script tag in >> org-latex-polyglossia-font-config to cater for specificalities (see >> org-manual.org for a longer explanation with external references). > > I see > > Languages that define a ~:polyglossia~ property that doesn't match the name > expected by ~polyglossia~ need to provide the expected family name > using the ~:script~ property in ~org-latex-polyglossia-font-config~. > > ":polyglossia property that doesn't match the name expected by > polyglossia" sounds like a bug in `org-latex-language-alist'. What do I > miss? Can't we simply make sure that all :polyglossia values are > appropriate? > > -- > 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>
