emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Alexander Vorobiev <alexander.vorobiev@gmail.com>
Cc: Bastien <bzg@altern.org>,
	Orgmode Mailing List <emacs-orgmode@gnu.org>,
	Gary Oberbrunner <garyo@oberbrunner.com>
Subject: Re: LaTeX export problem
Date: Sat, 22 Sep 2012 10:07:39 +0200	[thread overview]
Message-ID: <87wqzmcwfo.fsf@gmail.com> (raw)
In-Reply-To: <CAGOCFPUp8GodquFjG3tV7yU-WKQb8fzhX8T1tBfhY9NU_06j0Q@mail.gmail.com> (Alexander Vorobiev's message of "Fri, 21 Sep 2012 14:47:21 -0500")

Hello,

Alexander Vorobiev <alexander.vorobiev@gmail.com> writes:

> I tried the new exporter (using today's snapshot of the sources) and
> it produced invalid LaTeX (it calls hypersetup without loading
> hyperref package).

The export back-end doesn't load any package on its own. You have to
make sure hyperref is properly loaded (AFAIK, it is by default).

> It also ignored the #+LaTeX_CLASS: and all the
> #+LaTeX_HEADER:lines in my file.

Those lines shouldn't be ignored. You probably don't have any matching
entry in `org-e-latex-classes' for your #+LATEX_CLASS: specification.

I'm not sure about #+LaTeX_HEADER: lines. Do you have an example?

> Are there any examples of org files which show how to customize the
> new LaTeX exporter?

Try first:

M-x customize-group RET org-export-e-latex RET


Regards,

-- 
Nicolas Goaziou

  parent reply	other threads:[~2012-09-22  8:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 16:47 LaTeX export problem Gary Oberbrunner
2012-09-19  7:57 ` Bastien
2012-09-20 14:59   ` Alexander Vorobiev
2012-09-21  8:48     ` Bastien
2012-09-21 19:47       ` Alexander Vorobiev
2012-09-21 21:21         ` Thomas S. Dye
2012-09-22  8:01           ` Nicolas Goaziou
2012-09-22  8:07         ` Nicolas Goaziou [this message]
2012-09-24 16:40           ` Alexander Vorobiev
2012-09-24 21:15             ` Nicolas Goaziou
2012-09-24 21:32               ` Alexander Vorobiev
2012-09-26 18:48                 ` Nicolas Goaziou
  -- strict thread matches above, loose matches on Subject: below --
2014-07-13 21:25 Thomas S. Dye
2014-07-16 14:36 ` Nicolas Goaziou
2014-07-16 16:35   ` Thomas S. Dye
2012-01-09 15:45 Piotr Kaźmierczak
2012-01-10  0:13 ` Nick Dokos
2012-01-17 13:35   ` Piotr Kaźmierczak
2012-01-17 17:00     ` Nick Dokos
2012-01-17 19:00       ` Piotr Kaźmierczak
2012-01-17 20:45     ` Eric S Fraga
2010-09-30 14:55 latex " Jörg Hagmann
     [not found] ` <4CA4C29B.1060404@christianmoe.com>
2010-10-01  7:30   ` Jörg Hagmann
2010-10-01  7:32 ` Noorul Islam K M
2010-10-01  7:40   ` Jörg Hagmann
2010-10-01  9:03     ` Noorul Islam K M
2010-10-01  9:17       ` Noorul Islam
2010-10-01 11:38         ` Jörg Hagmann
2010-10-01 12:05           ` Jörg Hagmann

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=87wqzmcwfo.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=alexander.vorobiev@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=garyo@oberbrunner.com \
    /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).