From: James Harkins <jamshark70@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: jamshark70@dewdrop-world.net, nicholas.dokos@hp.com,
emacs-orgmode@gnu.org
Subject: Re: New exporter, beamer confusion
Date: Wed, 6 Feb 2013 10:12:05 +0800 [thread overview]
Message-ID: <CAFniQ7WXLM5wUuo75-DUcrpxjg7vvUVG1HF6ODz-r59o6E-WcQ@mail.gmail.com> (raw)
In-Reply-To: <87fw1ashw5.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3554 bytes --]
Thanks for all this. I'll look at the new org markup later today. That
should help a lot.
On Feb 6, 2013 3:03 AM, "Nicolas Goaziou" <n.goaziou@gmail.com> wrote:
> > 3. Strong *emphasis* now renders in red, instead of keeping the text's
> > original color and switching to boldface.
>
> Indeed. Strong emphasis in Beamer's jargon is \alert{...} (see Beamer
> documentation about it). Letter are so large that \textbf{...} doesn't
> fill the job well enough. I'm not saying that \textbf{...} is useless
> (though I think it), but "alert" was preferred.
Ok. There was something about customizing this on the list just recently.
I'll use that. (FWIW, I had to produce a number of *gasp cough choke*
PowerPoint shows in my previous job, and they told us not to use red for
*anything* unless it really was a four-alarm-fire "you will really screw
things up if you ignore this" type of point, and I retain this aversion to
red text to this day.)
Btw, *who* preferred \alert? (Orwell, Politics and the English Language:
"Never use the passive [voice] where you can use the active.")
> Since you seem to like lists (you know that
> Till Tantau frowns upon the use of third level lists in presentations,
> don't you?)
I appreciate his contribution to LaTeX, but I'll make my own decisions
about style, thanks.
> Headlines will never, ever, become lists in the new Beamer back-end.
>
> If you want lists, use lists. There's a handy command to do that change:
> mark the subtree you want to change, and use "C-c -".
>
> New back-end is more block friendly than lists friendly.
Although I'm not happy about manual intervention to convert my prior work,
this is a good step toward consistency. It was odd, in the old framework,
to use headlines for bullet lists and org's numbered lists for numbered
lists. "An org list becomes an output list" is an easier rule to explain.
Still, I wonder if there is a way to make the new backend less unfriendly
toward lists. It's an interesting philosophical question: In what cases is
it better for the tool to adapt to the users' wishes, versus cases where
the tool should encourage (Are blocks in the result actually better than
lists? Who says so, and why should I take his or her word for it?)
> > At least, it would be good to clarify, with respect to the
> > announcement, if the new beamer exporter is intended to be reasonably
> > backward-compatible with the old (with not-too-intrusive tweaks).
>
> It all depends on what you mean by reasonably. You can obtain the same
> output, but there are changes to make in Org files.
"Reasonably" for me would mean tweaking some configuration options and
perhaps changing a few minor details of the markup. If you have to change
the org document's structure (e.g., converting headlines to lists), it
isn't backward compatible.
For comparison: Lilypond updates frequently break some details of backward
compatibility. So, they ship a "convert-ly" script to handle many of those
changes automatically.
> Oh, yes, and BEAMER_FRAME_LEVEL doesn't exist anymore. It's H:... in the
> OPTIONS line.
Right, covered in an earlier message in this thread. I included it here so
you could compile it using the old exporter, for comparison.
> I'm attaching an updated version of your simple document. Besides moving
> subtree to lists, there only other change was at the columns level.
Thanks for this, and the explanation of columns. Actually, I never was
really happy with columns in the old backend. It's quite likely to be
better here!
Really appreciate the details.
hjh
[-- Attachment #2: Type: text/html, Size: 4270 bytes --]
next prev parent reply other threads:[~2013-02-06 2:57 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 16:37 org-url-hexify-p is not respected James Harkins
2012-09-10 1:50 ` James Harkins
2012-09-10 4:58 ` Nick Dokos
2012-09-10 6:16 ` James Harkins
2012-09-10 6:37 ` Jambunathan K
2012-09-10 6:48 ` James Harkins
2012-09-10 7:12 ` Jambunathan K
[not found] ` <CAFniQ7W_5QMUawD2NObyhy2_Y647as-NthobZ9OgAX4NLcVJBw@mail.gmail.com>
2012-09-11 10:22 ` James Harkins
2012-09-11 13:10 ` Activating modules before org-install (was: org-url-hexify-p is not respected) Memnon Anon
2012-09-11 13:56 ` Jonathan Leech-Pepin
2012-09-11 17:06 ` org-url-hexify-p is not respected Charles Philip Chan
2012-09-23 10:05 ` Bastien
2012-09-26 17:59 ` Michael Brand
2012-09-26 21:50 ` Bastien
2012-09-27 6:18 ` Michael Brand
[not found] ` <jamshark70@gmail.com>
2012-08-12 2:55 ` MobileOrg, webdav, correct use of org-mobile-directory? James Harkins
2012-08-12 4:29 ` Nick Dokos
2012-08-12 7:12 ` James Harkins
2012-08-12 8:43 ` Bastien
2012-08-12 8:50 ` James Harkins
2012-08-12 13:11 ` Nick Dokos
2012-08-18 23:25 ` Adam Spiers
2012-08-19 1:35 ` Adam Spiers
2012-08-19 5:49 ` James Harkins
2012-08-20 20:03 ` Rémi Vanicat
2012-08-19 2:41 ` Nick Dokos
2012-08-12 11:38 ` James Harkins
2012-08-12 12:40 ` Nick Dokos
2012-08-12 13:12 ` Nick Dokos
2012-09-29 16:34 ` LaTeX beamer export: relative file links? Nick Dokos
2012-09-30 2:04 ` James Harkins
2013-01-10 3:40 ` <M-S-left/right> changed? Nick Dokos
2013-01-10 9:17 ` James Harkins
2013-02-05 7:21 ` New exporter, beamer confusion Nick Dokos
2013-02-05 9:01 ` James Harkins
2013-02-05 13:20 ` Sebastien Vauban
2013-02-05 13:55 ` Nick Dokos
2013-02-05 19:03 ` Nicolas Goaziou
2013-02-06 0:11 ` Eric S Fraga
2013-02-06 18:55 ` Nicolas Goaziou
2013-02-06 22:39 ` Eric S Fraga
2013-02-07 12:31 ` Nicolas Goaziou
[not found] ` <37646106030B4CA98C6A7717FBD89D50@gmail.com>
[not found] ` <87vca4jigj.fsf@gmail.com>
2013-02-07 14:49 ` Vincent Beffara
2013-02-07 14:58 ` Nicolas Goaziou
2013-02-07 17:08 ` Rasmus
2013-02-07 21:48 ` Nicolas Goaziou
2013-02-07 23:38 ` Rasmus
2013-02-08 21:41 ` Nicolas Goaziou
2013-02-08 13:40 ` Eric S Fraga
2013-02-06 2:12 ` James Harkins [this message]
2013-02-06 4:35 ` Eric S Fraga
2013-02-06 12:32 ` Rasmus
2013-02-06 13:12 ` Suvayu Ali
2013-02-06 13:45 ` Sebastien Vauban
2013-02-06 19:57 ` Nicolas Goaziou
2013-02-07 1:32 ` James Harkins
2013-02-05 9:36 ` Eric S Fraga
2013-02-25 6:25 ` How to make the new exporter open PDF using evince? James Harkins
2013-02-25 7:01 ` Mike Gauland
2013-02-25 6:52 ` Nick Dokos
2013-02-25 13:06 ` James Harkins
2013-02-26 2:40 ` Martin Marier
2013-02-27 9:51 ` James Harkins
[not found] <CAFniQ7UgwaQ5jO2r7iJ7PbakWfpvsJGZw2FNNf+sawwvKqSUqQ@mail.gmail.com>
2012-09-29 5:55 ` LaTeX beamer export: relative file links? James Harkins
-- strict thread matches above, loose matches on Subject: below --
2013-01-10 2:38 <M-S-left/right> changed? James Harkins
2013-02-04 4:00 New exporter, beamer confusion James Harkins
2013-02-04 6:39 ` Suvayu Ali
2013-02-04 8:55 ` James Harkins
2013-02-04 19:51 ` Nicolas Goaziou
2013-02-05 0:09 ` James Harkins
2013-02-05 12:32 ` Eric S Fraga
2013-02-05 18:06 ` Nicolas Goaziou
2013-02-05 23:49 ` 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=CAFniQ7WXLM5wUuo75-DUcrpxjg7vvUVG1HF6ODz-r59o6E-WcQ@mail.gmail.com \
--to=jamshark70@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
--cc=n.goaziou@gmail.com \
--cc=nicholas.dokos@hp.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).