emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Titus von der Malsburg <malsburg@posteo.de>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Exporting to beamerposter
Date: Tue, 04 Aug 2015 22:24:58 -0700	[thread overview]
Message-ID: <87fv3ygvdh.fsf@posteo.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2285 bytes --]


I’d like to use org-mode to create an academic poster like this one
(random example found using Google):

  http://robjhyndman.com/images/PosterInterests_beamer-723x1023.png

As the LaTeX target, I use beamerposter which is basically just a skin
for Beamer:

  https://github.com/deselaers/latex-beamerposter
  https://www.ctan.org/pkg/beamerposter?lang=en

Such a poster typically consists of two columns (or more when landscape
format is used) and blocks stacked inside these columns.  Sometimes, I
also need something more fancy like a block in a column and more columns
inside that block but that’s rare.

What I would like to write in org is something like the following:

#+BEGIN_SRC org
    #+BEAMER: \begin{columns}
    #+BEAMER: \begin{column}{0.48\columnwidth}

    * Introduction
        :PROPERTIES:
        :BEAMER_ENV: block
        :END:
    This poster is about …

    * Design
        :PROPERTIES:
        :BEAMER_ENV: block
        :END:
    To test A we did B.

    #+BEAMER: \end{column}
    #+BEAMER: \begin{column}{0.48\columnwidth}

    * Discussion
        :PROPERTIES:
        :BEAMER_ENV: block
        :END:
    Our ground-breaking results show …

    #+BEAMER: \end{column}
    #+BEAMER: \end{columns}
#+END_SRC

However, this doesn’t work for two reasons:

1.) Org mode ignores that I want blocks and instead uses frame
environments.

2.) The closing \end{frame} macros are misplaced, e.g:

#+BEGIN_SRC latex
    …
    \begin{frame}[label={sec:orgheadline3}]{Discussion}
    Our ground-breaking results show …

    \end{column}
    \end{columns}
    \end{frame}
    …
#+END_SRC

My question: What do I have to do in org to get the desired structure in
Latex?  This structure would be something like the following:

#+BEGIN_SRC latex
    \begin{columns}
    \begin{column}{0.48\columnwidth}
    
    \begin{block}{Introduction}
    This poster is about
    \end{block}

    \begin{block}{Design}
    To test A we did B.
    \end{block}

    \end{column}
    …
#+END_SRC

Posters really are the only type of document that has consistently
resisted being taken over by org-mode.  So I would be great to have a
solution for this.
  
  Titus






[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

             reply	other threads:[~2015-08-05  5:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05  5:24 Titus von der Malsburg [this message]
2015-08-05  6:08 ` Exporting to beamerposter Julien Cubizolles
2015-08-05  8:08 ` Eric S Fraga
2015-08-06  3:26   ` Titus von der Malsburg
2015-08-06 11:00     ` Eric S Fraga

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=87fv3ygvdh.fsf@posteo.de \
    --to=malsburg@posteo.de \
    --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).