From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: new (LaTeX) exporter and date formatting
Date: Fri, 15 Jun 2012 17:31:54 +0200 [thread overview]
Message-ID: <87aa048uc5.fsf@gmail.com> (raw)
In-Reply-To: <80k3z8ljzr.fsf@somewhere.org> (Sebastien Vauban's message of "Fri, 15 Jun 2012 16:36:56 +0200")
Hello,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> That's wrong a the main language is the latest loaded (here: english).
Good point.
>> Should it replace previous language instead?
>
> I would think so, or at least suffixed, instead of being prefixed.
From now, it will be suffixed.
> 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).
This is unrelated to HTML. Each back-end handles #+LANGUAGE: keyword as
needed, if at all. There's no global specification about that keyword.
Moreover, it's simpler to implement that way. So, if there is no
drawback with having two languages, let's keep it simple.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2012-06-15 15:35 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
2012-06-15 15:31 ` Nicolas Goaziou [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aa048uc5.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.