From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [ox-beamer] Frame subtitles are not handled anymore
Date: Mon, 25 Feb 2013 22:57:06 +0100 [thread overview]
Message-ID: <86621ggiq5.fsf@somewhere.org> (raw)
In-Reply-To: 878v6q95ag.fsf@gmail.com
Hi Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>>
>> It took me quite some time, but I'm at the end of converting a 90 slides
>> presentation from the old to the new exporter.
>>
>> In that presentation, there is (just!) one thing which does not work
>> anymore: the frame subtitles.
BTW, it has to be emphasized: just ONE thing for which I could not find a
direct mapping toward a solution; that's pretty excellent!
>> Before, I could write:
>>
>> * News \\ Technology
>>
>> ...
>>
>> and get that exported as:
>>
>> \begin{frame}
>> \frametitle{News}
>> \framesubtitle{Technology}
>> ...
>> \end{frame}
>>
>> (or similar.)
>>
>> Now, such a title is simply cut over 2 lines; hence, the use of a bad font
>> (in LaTeX) for the subtitle (font as big as the one customized for the
>> title itself).
>>
>> How could we write subtitles again in Beamer presentations?
>
> It was discussed a few months ago.
I must have missed it.
> To sum it up, I don't like that syntax, because it's very close to line
> breaks.
But the advantage was that you could almost not expect that markup as a valid
string. While, would we opt for:
- [Title] Subtitle
- Title > Subtitle
you wouldn't be so sure.
Note that, to be closer to the real Beamer syntax, one could think of:
- {Title} Subtitle
- Title {Subtitle}
Such syntax have the advantage to stay readable and quite explicit, even if
translated "verbatim" in other backends (such as HTML): that was already the
case of the old syntax: in HTML, "Title \\ Subtitle" was very readable, even
if not processed in any particular way (and one could image a CSS-only
solution to even present it more as a real subtitle).
> But I'm not against some easy way to add a subtitle to a frame.
>
> A special property isn't satisfactory either, because those aren't
> parsed. So
>
> :beamer_subtitle: *bold*
>
> will probably not give you what you expect. Do you have any suggestion
> about it?
No, it would not be really satisfactory, not really for bold (as, anyway,
titles are generally bold), but more for = markups: "Code for =org-agenda=",
for an example of subtitle.
> Meanwhile, doesn't the following work?
>
> #+BEAMER: \framesubtitle{Technology}
Yes, meanwhile, that does work.
Best regards,
Seb
--
Sebastien Vauban
prev parent reply other threads:[~2013-02-25 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 13:05 [ox-beamer] Frame subtitles are not handled anymore Sebastien Vauban
2013-02-14 17:25 ` Nicolas Goaziou
2013-02-25 21:57 ` Sebastien Vauban [this message]
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=86621ggiq5.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.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).