From: Bastien <bzg@gnu.org>
To: Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com>
Cc: "Liste-emacs-orgmode@gnu.org " <emacs-orgmode@gnu.org>
Subject: Re: org export for both latex and beamer, a recipe?
Date: Mon, 20 Jan 2014 12:27:41 +0100 [thread overview]
Message-ID: <87lhyayjte.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87d2k0131v.fsf@gmail.com> (Joseph Vidal-Rosset's message of "Fri, 10 Jan 2014 12:36:44 +0100")
Hi Joseph,
Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> writes:
> It's very nice that an org file can be exported both to a .tex file with
> article class as well as to beamer class.
>
> Here is my question: does anyone knows how mixing in the same org file
> what is supposed to be in the paper.tex and what is only for a talk with help of beamer?
>
> I would be very happy to be able to write a draft in org-mode with
> saying to myself for example «this list must be in my talk». But I know
> that showing a list with beamer in a talk does not require exactly the
> same properties than writing a list for a paper (with beamer class the
> exposition of the list can be dynamic).
> The best would be to succeed to write the same org file, in order to
> have only to change the Latex class: beamer or article, the export would
> make all. Is it possible?
This cannot be straightforward.
Maybe you can start a list of differences that you want to handle for
such a dual-target export?
Dynamic lists comes as one first example.
ox-beamer.el could have an option so that plain lists are always
converted as dynamic lists (using the <1-> <2-> syntax) -- one problem
would be solved, at least.
--
Bastien
next prev parent reply other threads:[~2014-01-20 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 11:36 org export for both latex and beamer, a recipe? Joseph Vidal-Rosset
2014-01-20 11:27 ` Bastien [this message]
2014-01-20 12:38 ` Nicolas Goaziou
2014-01-20 12:43 ` Bastien
2014-01-22 9:07 ` Joseph Vidal-Rosset
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=87lhyayjte.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=joseph.vidal.rosset@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).