Dear all,

Please find enclosed a proposed patch (against master) to document the
need for babel/polyglossia in order to honor #+language in LaTeX
export.

This is purely a documentation patch. A better solution would be to
detect the use of a non-default #+language: and act accordingly.
Nicolas notes (rightly) that babel (and polyglossia, BTW) are too
"invasive" to be default, and is shy of auto-loading the necessary
package(s) "automagically.

I do not (yet) know how ti reconcile these imperative, hence the
present interim atch (which should disappear if/when a better solution
is created).

HTH,

--
Emmanuel Charpentier


Le jeudi 29 novembre 2018 à 20:12 +0100, Nicolas Goaziou a écrit :
> Emmanuel Charpentier <emanuel.charpentier@gmail.com> writes:
> 
> > This is *not* *documented* (not even in the `org-latex-packages-
> > alist''s
> > docstring).
> 
> I know. I fixed `org-latex-packages-alist''s docstring two days ago.
> 
> > Also agreed, with the reservation that "invasive" didn't mean the
> > same
> > thing in the 1980s (when the core size of computers was measured in
> > kilobytes) and in the 2010s (the current core measurement unit is
> > the
> > /giga/byte...).
> 
> Not invasive by its sheer size, but by the number of alterations it
> generates in the LaTeX default behaviour, and the incompatibilities
> it
> may introduce. For example there used to be issues between frenchb
> and
> KOMA-Script.
> 
> > Again, I think that the end user should *not* have to worry with
> > this only
> > when exporting to LaTeX (or beamer or PDF). 
> 
> Ideally, that would be nice.
> 
> > If this can be handled silently when exporting to ODT, HTML or
> > plain
> > text, it should be handled silently when exporting to LaTeX.
> 
> I disagree. Packages should not be loaded /silently/.
> 
> > I do not know how to handle this. My *hunch* is that the Latex
> > Export
> > function generating the preamble should check for language
> 
> It does already, in `org-latex-guess-babel-language'.
> 
> > and if not default, add the relevant package(s) to the preamble.
> 
> Don't. Anything that is in the header should be declared.
> 
> We could try and see if Babel causes trouble by adding it to default
> packages in "next" branch. I'd rather do that than inserting it
> magically.