"Pedro A. Aranda" <[email protected]> writes: > this is a bigger patch that adds more user control to the PDF Metadata > infrastructure, based on experience of switching back and forth betwee > MacTex2025 and 2026. > > I feel it needs some checking from your side... > ... > + When the document metadata include the shorthand ~DOC_LANGS~, it > + will be replaced by the main language declared with the ~LANGUAGE~ > + and ~OTHER_LANGUAGES~ keywords, formatted by > + ~org-latex-build-doclangs-function~. This custom variable points > + to either of the functions ~org-latex-doclang-full~ or > + ~org-latex-doclang-short~, or a user-defined function: > ... > + language=en, other-languages={es, fr}} > ... > +\DocumentMetadata{tagging=on, lang=en}
I feel that this is going in a wrong direction. The whole point of export backend is automating LaTeX export, so that users do not need to customize every possible detail, conditioned on exact details of the latex version used or the compiler. What you propose can be achieved much simpler - by supplying #+LATEX_DOC_METADATA: tagging=on, lang=en directly. The indirection with #+LATEX_DOC_METADATA: tagging=on, DOC_LANGS + yet another extra customization feels like over-engineering. If you want to support different latex versions, we should automatically detect it and use the appropriate format. -- 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>
