From 7fa155f018687a3395c972661c42159dbfc35fe6 Mon Sep 17 00:00:00 2001 From: Emmanuel Charpentier Date: Sun, 2 Dec 2018 21:01:08 +0100 Subject: [PATCH] org-manual.org: document the need for babel when setting #+language: * Add a note to Export Variables. * Describe the use of org-latex-packages-alist for loading babel (or polyglossia) with the right argument in LaTeX specific export settings. --- doc/org-manual.org | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/doc/org-manual.org b/doc/org-manual.org index 458e59a4a..349d01e48 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -11249,6 +11249,10 @@ global variables, include: example, Org translates =Table of contents= to the French =Table des matières=. + For export to LaTeX format (or LaTeX-related formats such as PDF + or =beamer=), the =org-latex-package-alist= variable needs + configuration in [[LaTeX specific export settings]] ([[LatexSetupForLanguage][description)]] + - =SELECT_TAGS= :: #+cindex: @samp{SELECT_TAGS}, keyword @@ -12973,6 +12977,26 @@ general options (see [[*Export Settings]]). the document's front matter. Use multiple =DESCRIPTION= keywords for long descriptions. +- =LANGUAGE= :: + #+cindex: @samp{LANGUAGE}, keyword + #+vindex: org-export-default-language + #+vindex: org-latex-package-alist + <>LaTeX-specific setting: in order to be + effective in LaTeX export, the =babel= or =polyglossia= packages + (according to the LaTeX compiler used) must be loaded with the + appropriate language as argument. + + These packages being too invasive for loading them by default, + this is not currently done by default. This can be accomplished + by setting (or adding to) the =org-latex-package-alist= variable + the following snippet: + +#+BEGIN_EXAMPLE +'(("AUTO" "babel" t '("pdflatex")) + ("AUTO" "polyglossia" t '("xelatex" "lualatex"))) +#+END_EXAMPLE + + - =LATEX_CLASS= :: #+cindex: @samp{LATEX_CLASS}, keyword -- 2.19.2