From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [New exporter] Wrong export to LaTeX
Date: Fri, 12 Oct 2012 14:19:31 +0200 [thread overview]
Message-ID: <20121012121931.GF24769@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <87hapz3na9.fsf@gmail.com>
Hi Nicolas,
Your explanations below explains all the gaps in my understanding!
Thanks a lot and apologies for all the confusion.
:)
On Fri, Oct 12, 2012 at 02:09:02PM +0200, Nicolas Goaziou wrote:
> Hello,
>
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>
> > Okay, I do follow this. However, doesn't LaTeX_CLASS determine what
> > goes into the \documentclass{class name} directive?
>
> No. Key in `org-e-latex-class' is just a label. You can have an
> association like:
>
> ("foo" "\\documentclass{article}" ...)
>
> It is here to help you name different configurations.
>
> > If so, does having \begin{frames}..\end{frames} in the exported tex
> > make sense if the documentclass directive says, for example, article?
>
> You can use article, or book document classes along with Beamer, i.e.
> when you want to create handouts for your presentation. This requires to
> load "beamerarticle" package (cf. Beamer documentation).
>
> So, yes it can make sense to call Beamer back-end on an "article"
> documentclass.
>
> > What I'm getting at is, without the LaTeX_CLASS set to beamer, the
> > crucial \documentclass{beamer} directive is missing and the exported
> > LaTeX document won't be compilable[1]. Given the preceding comments are
> > correct, I would then say having a "beamer" class already defined in
> > org-e-beamer will save new users some trouble. Is my analysis valid, or
> > am I grossly wrong?
>
> Like in the LaTeX back-end, if you specify some class, you have to make
> sure it does match an association in `org-e-latex-classes'. Though,
> having a class named "beamer" isn't mandatory: you can have many classes
> named differently and all using internally "\\documentclass{beamer}".
>
> Also, I don't want to automatically modify a defcustom
> (`org-e-latex-classes') once `org-e-beamer' is loaded. It isn't very
> clean, even with careful checks.
>
> `e-beamer' could also default to some header when provided class doesn't
> match, but that looks ugly, too.
>
> > Footnotes:
> >
> > [1] I tried this with the LaTeX_CLASS set to article, and there were
> > errors in the exported pdf.
>
> Because, in that case, your header must contain:
>
> \usepackage{beamerarticle}
>
>
> Regards,
>
> --
> Nicolas Goaziou
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2012-10-12 12:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 13:04 [New exporter] Wrong export to LaTeX Sebastien Vauban
2012-10-11 13:21 ` Nicolas Goaziou
2012-10-11 16:52 ` Suvayu Ali
2012-10-11 17:54 ` Nicolas Goaziou
2012-10-12 10:24 ` Suvayu Ali
2012-10-12 11:06 ` Sebastien Vauban
2012-10-12 11:32 ` Sebastien Vauban
2012-10-12 11:51 ` Nicolas Goaziou
2012-10-12 12:15 ` Suvayu Ali
2012-10-12 12:05 ` Suvayu Ali
2012-10-15 20:23 ` Sebastien Vauban
2012-10-15 20:42 ` Nicolas Goaziou
2012-10-16 7:49 ` Sebastien Vauban
2012-10-12 12:09 ` Nicolas Goaziou
2012-10-12 12:19 ` Suvayu Ali [this message]
2012-10-11 13:45 ` Suvayu Ali
2012-10-11 14:41 ` Sebastien Vauban
2012-10-11 15:35 ` Suvayu Ali
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=20121012121931.GF24769@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.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).