"Pedro A. Aranda" <[email protected]> writes: >> It is not clear what "the beginning of the generated LaTeX output" >> refers to. > > Reworded
I think it is worth clarifying that it is latex preamble. Somehow, "LaTeX output" feels more like body when I read it in this sentence. >> We should probably refer to LATEX_MULTI_LANG export option (which >> includes keyword + variable) > > OK LATEX_MULTI_LANG export option implies setting keyword or variable. We should mention this fact in the =LATEX_MULTI_LANG= description in "LaTeX specific export settings". >>> If you do not want or need any specific configuration for the >>> ~fontspec~ package, make sure that ~org-latex-fontspec-config~ is set >>> to ~nil~ (this is the default value). This is normally the case when >>> exporting to ~beamer~, where you most probably want to use the fonts >>> defined in the template. >> >> If beamer requires special font handling, I recommend making >> fontspec-config into an export option that can be overridden by derived >> backends. WDYT? > > Wouldn't this complicate things? You manage everything with the > [FONTSPEC] in the templates. I do not think so. Consider a user who wants to set org-latex-fontspec-config for latex export and then happen to export to beamer. The export will be broken unless the variable is temporarily set to nil. This is awkward. Our canonical way to deal with such conflicts between derived backends is overriding parent backend option. Like how beamer does it for LATEX_CLASS option. >> I am wondering if the missing scripts should be displayed in *Warnings* > > No IMHO... because you will get it when the PDF is produced correctly. Ok. -- 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>
