From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Rationale for *text* -> \alert{text} for Beamer export?
Date: Thu, 2 May 2013 12:44:31 +0200 [thread overview]
Message-ID: <20130502104431.GD17914@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <m1fvy62x9e.fsf@poto.myhome.westell.com>
On Wed, May 01, 2013 at 11:41:49AM -1000, Thomas S. Dye wrote:
> John Hendy <jw.hendy@gmail.com> writes:
>
> > On Wed, May 1, 2013 at 10:00 AM, Marcin Borkowski <mbork@wmi.amu.edu.pl> wrote:
>
> 3) So, markup should be semantic, rather than visual.
>
> It is possible to achieve identical results using visual markup, of
> course, but why not let the computer keep track of things instead?
> >
> > Sure, and understood. In general, I'm using *text* simply to call
> > attention to something important. I work in product development, so
> > something like:
> >
> > Customer response to product sampling:
> > - *US:* blah blah blah
> > - *China:* blah blah blah
> > - *India: blah blah blah
>
> Here, to achieve semantic markup, you would use description lists
>
> - US :: blah
> - China :: blah
> - India :: blah
Description lists align at the "::", which can look weird when you have
headings of very different lengths. So I often use \structure{..}. I
have a filter that translates +strikethrough+ text to structure[1].
Footnotes:
[1] <http://orgmode.org/worg/exporters/beamer/ox-beamer.html#export-filters>
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-05-02 10:44 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
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 [this message]
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=20130502104431.GD17914@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--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).