emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Kevin Brubeck Unhammer <p.ixiemotion@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: FR: make LaTeX export recognize LANGUAGE option
Date: Tue, 05 May 2009 10:19:37 -0400	[thread overview]
Message-ID: <9835.1241533177@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Kevin Brubeck Unhammer <p.ixiemotion@gmail.com> of "Tue, 05 May 2009 15:31:09 +0200." <96023f220905050631j4e990021q45f3aafcf3383a12@mail.gmail.com>

Kevin Brubeck Unhammer <p.ixiemotion@gmail.com> wrote:

> I couldn't find any references to babel in the mailing list nor in
> org-latex.el. I have various latex export class headers, but I
> sometimes write in English and sometimes in Norwegian, and this is not
> bound to the classes (beamer, ps-article, pdf-article). As it is, I've
> had
> \usepackage[nynorsk,english]{babel}
> in all my class headers, and then eg.
> \selectlanguage{nynorsk}
> in the org file.
> But before printout I've had to go into the .tex-file and remove
> whatever language I'm not using, deleting the .aux file and rerunning
> latex, since Apacite doesn't recognize the \selectlanguage within the
> literature list (eg. I get English "in" and "from" and such).
> So, I was wondering if we could have an option to let
> #+LANGUAGE: nn
> make the header say
> \usepackage[nynorsk]{babel}
> etc., so that, at least for monolingual documents, one doesn't have to
> do all this mucking about with \selectlanguage and deleting .aux
> files.
> If implemented, I think I might've read somewhere that babel should be
> loaded early on in the header, but other people probably know this
> better than me. (I guess it shouldn't be too hard to put it on the
> line right after \documentclass ?)
> Possibly "#+LANGUAGE: nn en" could be used for multilingual documents,
> but that seems low priority to me.

Part of the problem is that if you have previous runs, the aux file and such
are going to be present and they will need cleaning up no matter what you
do at the org level.

Purely at the org level, there may be a better way, but this is what I
came up with: you can hack around this by defining your own
"class". E.g. in your org file you say

#+LaTeX_CLASS: myclass

and you add a definition for ``myclass'' to org-export-latex-classes,
something like this (I just copied the ``article'' entry, modified the name
and added the babel stuff - and you probably still need to add
the \selectlanguage more-or-less by hand, but I guess you can do it at the
org level):

(add-to-list 'org-export-latex-classes
     ("\\section{%s}" . "\\section*{%s}")
     ("\\subsection{%s}" . "\\subsection*{%s}")
     ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
     ("\\paragraph{%s}" . "\\paragraph*{%s}")
     ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))

Does this help?


  reply	other threads:[~2009-05-05 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-05 13:31 FR: make LaTeX export recognize LANGUAGE option Kevin Brubeck Unhammer
2009-05-05 14:19 ` Nick Dokos [this message]
2009-05-06  7:17 ` Carsten Dominik

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:

  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=9835.1241533177@gamaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=p.ixiemotion@gmail.com \


* 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


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).