Hi again I don't want to sound pushy, just giving more points of view, pointers, possibilities, etc. that IHMO justify the :script tag in org-latex-polyglossia-font-config. @emacs-orgmode: Concentrating on Hindi because it is sort of the origin of this conversation, but please come forward with other languages with similar needs. The more we can find, the more complete a solution we can strive for. Bottom line: we can't cover all situations. Users might find it useful to be able to tweak the output to their personal preferences or constraints.
- Just a pointer to LaTeX/hindi Q(&A): https://tex.stackexchange.com/questions/tagged/hindi - This one shows the wealth of languages that _I perceive_ as hidden right now (caveat, it might not be the case) https://tex.stackexchange.com/questions/565173/how-to-help-polyglossia-find-a-font-of-choice-while-typesetting-devanagari-on-li - This one uses "hindi" for the font definitions https://tex.stackexchange.com/questions/697800/bold-and-italic-hindi-lohit-devanagri-fonts-in-latex-with-polyglossia - This one shows examples using hindi or devanagari https://tex.stackexchange.com/questions/199773/how-to-type-hindi-words-in-latex - This one is quite specific and a bit out of topic. We don't want to cover this right now and it's one of the things you would do with a #+LATEX_HEADER: \include{}. However it shows LRT/RTL markup. http://tex.stackexchange.com/questions/501194/numbering-pages-with-hindi-numerals-using-polyglossia Maybe something to think about to add as Org markup in the future? (Side note: like \textsf{} ??) Best,/PA On Tue, 25 Nov 2025 at 07:03, Pedro Andres Aranda Gutierrez < [email protected]> wrote: > Hi, > > Let’s leave this for further study. :polyglossia positive hits cover a > significant amount of languages. In cases they don’t, I’d rather have > people asking. > Thus we can suggest then to use their own name and report back. We, in > turn, can collect the alternatives and decide afterwards. > I have worked through the “canonical” examples in manuals, wiki books and > overleaf.com int the last months. There are some examples for languages > where you can go the way you prefer (i.e. use :language or :script _or even > a tag you define_). Look at the paragraph and example with Hindi. > My fear is that more experienced users will feel constrained and turn away. > It’s better to include this optional :script for this particular reason. > > /PA > > Enviado desde mi iPad > > > El 24 nov 2025, a las 20:44, Ihor Radchenko <[email protected]> > escribió: > > > > Ihor Radchenko <[email protected]> writes: > > > >> Pedro Andres Aranda Gutierrez <[email protected]> writes: > >> > >>> Isn’t it much safer to provide the extra information in the font > configuration for a start? > >> > >> I am not sure. It feels like it is not really related to font, but > >> simply some kind of per-language constant. Please let me know if I am > >> wrong. (I am quite confused about the intricacies of these font > thingies) > > > > Ok. I am wrong: > > ("hi" :babel "hindi" :polyglossia "hindi" :lang-name "Hindi" :script > "devanagari" :script-tag "deva") > > > > but we need to use "devanagari", not "hindi" that is the value of > > :polyglossia. > > > > Still, I feel like such kind of information belongs to > > `org-latex-language-alist' (maybe a new field like :polyglossia-script?). > > > > -- > > 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" (ORF: Als Radiohören gefährlich war) => write BE! Year 1 of the New Koprocracy
