Dear Nicolas,
Thanks a lot for bearing with my nitpicking. A couple remarks below
Le jeudi 29 novembre 2018 à 15:07 +0100, Nicolas Goaziou a écrit :
> Hello,
>
>
> > AFAICT, polyglossia is to be preferred to babel for use with
> > xelatex or
> > lualatex. I'll see if this can be accomodated.
>
> What I mean is that you can also add compiler dependant packages in
> `org-latex-packages-alist'.
This is *not* *documented* (not even in the `org-latex-packages-alist''s docstring).
I *checked* that one can add 4-element "cells" to this list (i. e. (list argument package, snippet-flag, list-of-compilers)), but could not *guess* it : I'm still running /H sapiens sapiens L./ v 1.0, no telepathic interface, no oracular coprocessor. The only way would have been to read the source code : not exactly the first reflex of the average end-user.
> No need to change the default package list.
I dispute that, since this "special configuration" is needed for LaTeX export *only* , and *only* with non-English #+language:s. This "exceptional" treatment should be handled silently by org-mode (as it does with ODT, HTML and plain text export...). But see below.
> > > it should be ("AUTO" "babel" t).
> >
> > OK. That's much clearer. And does what is intended, BTW.
> >
> > Shouldn't that be default ?(No, I don't (yet) know *how* to do
> > that..).
>
> Babel is no small package.
Agreed. And polyglossia is worse...
> I think it would be a bit invasive as
> a default package.
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...).
> However, it is a good candidate for user-defined
> packages, i.e., `org-latex-packages-alist'.
Again, I think that the end user should *not* have to worry with this only when exporting to LaTeX (or beamer or PDF). If this can be handled silently when exporting to ODT, HTML or plain text, it should be handled silently when exporting to LaTeX.
I do not know how to handle this. My *hunch* is that the Latex Export function generating the preamble should check for language, and if not default, add the relevant package(s) to the preamble. I'll need to dive in the source code to be more precise (not anytime soon, though...).
> > Thus introducing a serious problem : exporting to text or ODT works
> > as
> > described, whereas export to latex needs (undocumented)
> > supplementary
> > steps.
> >
> > At the very minimum, this need for further config should be
> > mentioned
> > in the docs ; preferably, a default should be proposed.
>
> See above about the default. However, please feel free to suggest
> documentation improvements, however.
I'll propose a documentation attempt. But this should be considered as a workaround, the real solution being the implementation of automatic handling...
Cordially yours,
--
Emmanuel Charpentier
> Regards,
>