Nicolas Goaziou writes:
>> It changes behavior for your setup in that you can define a LANGUAGE
>> that isn't a known abbreviation.
>
> While I think your patch is overall an improvement, I'm not convinced by
> this particular point. Indeed #+LANGUAGE: expects a language code as
> value, not just
"Sebastien Vauban"
writes:
> That makes me think of another point: how do I say that the HTML exported
> document is in American English? By having a #+LANGUAGE: en-us specification.
>
> But that's not a valid language for Babel when exporting to LaTeX.
>
> So, I think we'd need some sort of ali
Hello,
Nicolas Goaziou wrote:
>> It changes behavior for your setup in that you can define a LANGUAGE
>> that isn't a known abbreviation.
>
> While I think your patch is overall an improvement, I'm not convinced by
> this particular point. Indeed #+LANGUAGE: expects a language code as
> value, not
Hello,
Rasmus writes:
Thanks for your patch. Here are a few comments:
> It changes behavior for your setup in that you can define a LANGUAGE
> that isn't a known abbreviation.
While I think your patch is overall an improvement, I'm not convinced by
this particular point. Indeed #+LANGUAGE: exp
Hi Sebastien,
>>> Behavior changes:
>>> 1. =("AUTO" "babel" t)= works like ("AUTO" "inputenc" t) in
>>> =`org-latex-default-packages-alist'=. I.e. the default
>>> language is choosen (sic).
>>> 2. if #+LANGUAGE: mylang then then \usepackage[mylang]{babel} in
>>> outpu (sic).
>>
>> Th
