From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: new (LaTeX) exporter and date formatting
Date: Fri, 15 Jun 2012 16:36:56 +0200 [thread overview]
Message-ID: <80k3z8ljzr.fsf@somewhere.org> (raw)
In-Reply-To: 87ipes8xrw.fsf@gmail.com
Hi Nicolas,
Nicolas Goaziou wrote:
> Andreas Leha <andreas.leha-A1rZ2h3LdSKGMSlLMZIubhS11BummzK+@public.gmane.org> writes:
>
>> I do not mind. I can have '#+LATEX_HEADER: \usepackage[en]{babel}' in
>> all my .org files by default and have the exporter override the language
>> setting based on the '#+LANGUAGE:' tag.
>
> I've pushed the patch. Thanks for the language list.
>
> Note that LANGUAGE doesn't override Babel package's options, but append
> another language to them if not already specified.
>
> Hence,
>
> #+LATEX_HEADER: \usepackage[english]{babel}
> #+LANGUAGE: fr
>
> will produce
>
> \usepackage[frenchb,english]{babel}
That's wrong a the main language is the latest loaded (here: english).
> Should it replace previous language instead?
I would think so, or at least suffixed, instead of being prefixed.
Of course, this is related to the question: do we allow or want multiple
languages in one document? If the answer is yes in LaTeX, how do we do in Org,
and for the HTML export (for which the value of #+LANGUAGE is also used).
Honestly, I don't care that much about one or the other, as I don't have to
type documents with multiple languages inside them. Or, if I would, I would
accept to insert LaTeX code inside my Org file to fix whatever needs to!
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-06-15 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 6:55 new (LaTeX) exporter and date formatting Andreas Leha
2012-05-23 13:24 ` Nicolas Goaziou
2012-05-23 21:33 ` Andreas Leha
2012-06-14 11:42 ` Nicolas Goaziou
2012-06-14 13:16 ` Sebastien Vauban
2012-06-14 16:49 ` Nicolas Goaziou
2012-06-15 12:42 ` Andreas Leha
2012-06-15 14:17 ` Nicolas Goaziou
2012-06-15 14:36 ` Sebastien Vauban [this message]
2012-06-15 15:31 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80k3z8ljzr.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).