emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: ox-latex: default packages cleaning
Date: Wed, 08 Jul 2015 18:06:30 +0200	[thread overview]
Message-ID: <87wpya3a7t.fsf@gmx.us> (raw)
In-Reply-To: 20150708154139.GG32342@chitra.no-ip.org

Hi,

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

>> +(defun org-latex-guess-polyglossia-language (header info)
>> +  "Set the Polyglossia language according to the LANGUAGE keyword.
>
> I'm in two-minds about this.  On the one had it is a nice thing, but on
> the other hand, it prevents the more fine grained control offered by
> polyglossia.  For example, I used this in my setup before:
>
>   \setdefaultlanguage[variant=british]{english}

It's a shame that Polyglossia is so much different from babel....  For
babel we translate en-gb to "british" which is a valid babel language.
But your example shows that org-latex-babel-language-alist does not work
for polyglossia.  Which means that somebody has to come up with a mapping
from language codes (en-gb) to (language . variant) pairs (your example).

Also, some mechanism needs to be in place to convey random options like
spelling={new, old} for German...  Unless polyglossia options can be set
afterwards via latex_headers.

> I don't see an easy way of passing the optional argument.  But on the
> other hand
>
>   \setmainlanguage{english}
>
> is plain, simple, and works in most (almost all) cases.

The only limitation here is whether somebody wants to contribute
org-latex-polyglossia-language-alist (≡ go through the manual and map all
pairs).  Conveying language-specific options in Org is what I worry about.

Rasmus

-- 
ツ

  reply	other threads:[~2015-07-08 16:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 14:53 ox-latex: default packages cleaning Rasmus
2015-07-07 15:48 ` Eric S Fraga
2015-07-07 19:35 ` Suvayu Ali
2015-07-07 20:05   ` Rasmus
2015-07-07 20:52     ` Suvayu Ali
2015-07-07 21:07       ` Rasmus
2015-07-08 12:53   ` Rasmus
2015-07-08 13:43     ` Suvayu Ali
2015-07-08 13:53       ` Rasmus
2015-07-08 14:09         ` Suvayu Ali
2015-07-08 14:26           ` Rasmus
2015-07-08 14:55             ` Suvayu Ali
2015-07-08 15:41     ` Suvayu Ali
2015-07-08 16:06       ` Rasmus [this message]
2015-07-08 18:35       ` Rasmus
2015-07-16  8:29         ` Suvayu Ali
2015-07-16  8:49           ` Rasmus
2015-07-27  8:22             ` Sebastien Vauban
2015-07-27  8:30               ` Rasmus
2015-07-27  9:22                 ` Sebastien Vauban
2015-07-27  9:31                   ` Rasmus
2015-07-29 16:21           ` Rasmus
2015-07-08 12:54   ` Rasmus
2015-07-08 13:44     ` Suvayu Ali
2015-07-14 22:31   ` Marcin Borkowski
2015-07-15  8:33     ` Rasmus
2015-07-10 11:25 ` Robert Klein
2015-07-11 10:48   ` Rasmus
2015-07-11 18:53     ` Robert Klein
2015-07-13 10:08 ` Rasmus
2015-07-14 22:16 ` Marcin Borkowski

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=87wpya3a7t.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.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).