Hi again, On Thu, 19 Jun 2025 at 15:38, Christian Moe <m...@christianmoe.com> wrote: > > - It would also be nice if we could rely on a single naming system for > languages in Org regardless of backend -- preferably, in my view, if > we could use only the language shortcodes already used by Org, and > have Org translate them to the language names expected by Polyglossia, > so we don't need to remember them (including quirks such as > capitalizing Arabic).
If you mean the definition in .dir-locals.el, it's implemented ... if you mean in the language blocks, then we need a new block, something like #+BEGIN_LANG ar #+END_LANG which in turn would have to look at org-latex-multi-lang-driver to understand how to produce the relevant code (depending on polyglossia vs. babel, latex_compiler, etc). It's feasible but I'd keep it as a TODO until we have sorted out the rest. What do people think? > Yours, > Christian Best, /PA PS: I'm currently polishing quirks and bringing back backwards compatibility to the feature branch. I appreciate any feedback (A LOT) ;-) -- 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
