From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: [dev] About a beamer back-end
Date: Thu, 21 Jun 2012 18:03:20 +0200 [thread overview]
Message-ID: <87obocodo7.fsf@gmail.com> (raw)
In-Reply-To: <807gv01zwh.fsf@somewhere.org> (Sebastien Vauban's message of "Thu, 21 Jun 2012 16:51:42 +0200")
Hello,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> - Sectioning and packages are extracted from `org-e-latex-classes'.
>> Since calling Beamer back-end is explicit, it can be applied on any
>> tex file, not only when that file starts with
>> "\documentclass{beamer}". Additionally, an equivalent to
>> `org-beamer-use-parts' is unnecessary.
>
> I did not understand that one.
At the moment, beamer exporter is hooked into regular latex exporter
when latex class is "beamer". This restriction is unnecessary when you
consider beamer as an independent back-end (i.e. you can call beamer
export even on your "article" setup).
> I'm wondering, though, how you support the special case of "beamer frame
> level" set to 0, where we need to add the tag "B_frame" (in fact, the
> property) to show where the frame really begins.
Would you mind providing an example for that? I am not aware of that
special case.
> I liked the fact we had 2 types of highlighting (bold, in black, and
> alert, in red, in my case).
>
> I would say that, as Beamer has those 2 different highlightings, we should be
> able to still support both. Is this a problem?
Not really a problem, but Org limits text markup to six elements. You
can easily choose to use another one for bold (i.e. with filters),
though.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-06-21 16:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 15:08 [dev] About a beamer back-end Nicolas Goaziou
2012-06-15 16:41 ` suvayu ali
2012-06-15 16:47 ` Avdi Grimm
2012-06-18 7:50 ` Eric S Fraga
2012-06-18 12:35 ` suvayu ali
2012-06-19 13:21 ` Nicolas Goaziou
2012-06-19 21:04 ` Eric S Fraga
2012-06-20 6:23 ` Greg Tucker-Kellogg
2012-06-20 11:55 ` Sebastien Vauban
2012-06-20 15:20 ` Eric S Fraga
2012-06-21 14:37 ` Nicolas Goaziou
2012-06-21 14:51 ` Sebastien Vauban
2012-06-21 16:03 ` Nicolas Goaziou [this message]
[not found] ` <87obocodo7.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-06-21 21:14 ` **: " Sebastien Vauban
2012-06-25 22:39 ` Andreas Leha
2012-06-21 14:55 ` Rasmus
2012-06-21 15:56 ` Nicolas Goaziou
2012-06-21 16:36 ` Rasmus
2012-06-21 16:49 ` suvayu ali
2012-06-22 7:54 ` Eric S Fraga
2012-06-18 6:32 ` Daniel Bausch
2012-06-18 10:17 ` Rasmus
2012-06-18 10:35 ` Sebastien Vauban
2012-06-18 12:00 ` Rasmus
2012-06-28 10:40 ` Andreas Leha
2012-06-28 10:47 ` suvayu ali
2012-06-28 10:50 ` Andreas Leha
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=87obocodo7.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.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).