From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: emacs-orgmode@gnu.org
Subject: Re: Rationale for *text* -> \alert{text} for Beamer export?
Date: Wed, 1 May 2013 17:00:06 +0200 [thread overview]
Message-ID: <20130501170006.57df8cf2@aga-netbook> (raw)
In-Reply-To: <CA+M2ft8_NOSBUheAWVvy7nwr1RXuSLwcPb=UGr1wnvN77+1SoA@mail.gmail.com>
Dnia 2013-05-01, o godz. 09:17:23
John Hendy <jw.hendy@gmail.com> napisał(a):
> Greetings,
>
> Just wondering about the rationale behind using *bold* markup for
> \textbf{} in LaTeX export and to \alert{} in Beamer. Was this a
> frequently voiced request? I'm sure I can dig into this somewhere and
> change it, but if the majority prefers bold (not saying they do!),
> should that be the default?
>
> I'd prefer bold, personally. I don't like red table column titles or
> in lists.
Just my 2 cents:
* In general, you shouldn't use boldface in printed documents (unless
you have a good reason. A /very/ good, thought out reason. And
usually you haven't one;).).
* In presentations, things are indeed quite different.
* Keeping that in mind, \alert{...} is /better/ than \textbf{...}, just
like \emph{...} is better than \textit{...}: it is semantic, not
visual markup.
* If you do insist on boldface as "alerting", just say
\setbeamerfont{alerted text}{series=\bfseries}
in your preamble. Keep in mind, however, that this will break things
if you use alert<...>{...}. Take this document, for instance:
\documentclass{beamer}
\begin{document}
\begin{frame}
This is \alert{alerted} text.
And this is \alert<2>{alerted} only on the second slide.
\end{frame}
\end{document}
In it, text will "wobble" when changing slides. This is ugly.
* So, what you probably want, is to say
\setbeamercolor{alerted text}{fg=red!50!black}
in your preamble, so \alert{...} means a color in the midpoint (in RGB
linear space) between red and black (you might want to experiment with
percentages other than 50% or wholly different colors, of course).
> Thanks,
> John
HTH,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
next prev parent reply other threads:[~2013-05-01 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 14:17 Rationale for *text* -> \alert{text} for Beamer export? John Hendy
2013-05-01 15:00 ` Marcin Borkowski [this message]
2013-05-01 20:50 ` John Hendy
2013-05-01 21:41 ` Thomas S. Dye
2013-05-01 22:09 ` Marcin Borkowski
2013-05-02 10:44 ` Suvayu Ali
2013-05-02 2:48 ` James Harkins
2013-05-02 8:20 ` Nicolas Goaziou
2013-05-02 11:44 ` James Harkins
2013-05-02 9:53 ` Marcin Borkowski
2013-05-02 10:28 ` Suvayu Ali
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=20130501170006.57df8cf2@aga-netbook \
--to=mbork@wmi.amu.edu.pl \
--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).