* Beamer handouts, pgfpages, no love
@ 2013-06-17 7:30 James Harkins
2013-06-17 14:26 ` Nicolas Goaziou
0 siblings, 1 reply; 3+ messages in thread
From: James Harkins @ 2013-06-17 7:30 UTC (permalink / raw)
To: orgmode
Hi,
Today I was playing around with exporting a beamer presentation for handouts, following the advice online to use pgfpages for saving dead trees. I'm not sure if it's an org problem or a LaTeX problem.
Exporting to a presentation is no problem:
#+startup: beamer
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [presentation]
#+BEAMER_THEME: default
For handouts, I tried changing it like this:
#+startup: beamer
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [handout]
#+BEAMER_THEME: default
#+LATEX_HEADER: \usepackage{pgfpages}
#+LATEX_HEADER: \pgfpagesuselayout{2 on 1}[a4paper,border shrink=5mm]
One problem: if I use any :BMCOL: tags, I get strange errors like this:
! LaTeX Error: \begin{minipage} on input line 117 ended by \end{altenv}.
... where the entity that is \ended could be several different things.
So I tried :noexport:ing all the sections that have columns, and now the export completes without fatal errors, but pgfpages then ends up making each frame about twice as large, instead of half. As far as I can see, it is actually trying to put two slides on each page (I can see only every other one), but each frame is so much larger than it's supposed to be that I can only see part of one of the two.
I'm using xelatex, if that makes any difference.
I could find list messages from about a year ago where somebody was successfully using pgfpages. I have no idea why it was working for him but not for me. His latex_header stuff was pretty similar to what I have above.
Thanks,
hjh
PS Belated thanks to Nick for answering the question of mine about emphasis markup and footnote tags. I haven't had a chance to try yet, but I did see the reply.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Beamer handouts, pgfpages, no love
2013-06-17 7:30 Beamer handouts, pgfpages, no love James Harkins
@ 2013-06-17 14:26 ` Nicolas Goaziou
[not found] ` <CAFniQ7X_-m=SYTc1_jQDteAqVhy_e1qMvEgFsCbkHS77EnByBw@mail.gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Nicolas Goaziou @ 2013-06-17 14:26 UTC (permalink / raw)
To: James Harkins; +Cc: orgmode
Hello,
James Harkins <jamshark70@gmail.com> writes:
> Today I was playing around with exporting a beamer presentation for
> handouts, following the advice online to use pgfpages for saving dead
> trees. I'm not sure if it's an org problem or a LaTeX problem.
>
> Exporting to a presentation is no problem:
>
> #+startup: beamer
> #+LaTeX_CLASS: beamer
> #+LaTeX_CLASS_OPTIONS: [presentation]
> #+BEAMER_THEME: default
>
> For handouts, I tried changing it like this:
>
> #+startup: beamer
> #+LaTeX_CLASS: beamer
> #+LaTeX_CLASS_OPTIONS: [handout]
> #+BEAMER_THEME: default
> #+LATEX_HEADER: \usepackage{pgfpages}
> #+LATEX_HEADER: \pgfpagesuselayout{2 on 1}[a4paper,border shrink=5mm]
>
> One problem: if I use any :BMCOL: tags, I get strange errors like this:
>
> ! LaTeX Error: \begin{minipage} on input line 117 ended by \end{altenv}.
>
> ... where the entity that is \ended could be several different things.
An ECM could be useful. By the way, does the generated LaTeX code look
wrong?
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-06-30 12:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-06-17 7:30 Beamer handouts, pgfpages, no love James Harkins
2013-06-17 14:26 ` Nicolas Goaziou
[not found] ` <CAFniQ7X_-m=SYTc1_jQDteAqVhy_e1qMvEgFsCbkHS77EnByBw@mail.gmail.com>
[not found] ` <87d2r3sv1c.fsf@gmail.com>
2013-06-30 12:58 ` James Harkins
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).