From: tsd@tsdye.com (Thomas S. Dye)
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
Marcin Borkowski <mbork@wmi.amu.edu.pl>
Subject: Re: Rationale for *text* -> \alert{text} for Beamer export?
Date: Wed, 01 May 2013 11:41:49 -1000 [thread overview]
Message-ID: <m1fvy62x9e.fsf@poto.myhome.westell.com> (raw)
In-Reply-To: <CA+M2ft9ETREf0d=jUEhSGT4o=QQSGNJwCMRAz-KSwoMHONpzAQ@mail.gmail.com> (John Hendy's message of "Wed, 1 May 2013 15:50:13 -0500")
Hi John,
Jumping in late here, with apologies if that's left me wide of the mark.
John Hendy <jw.hendy@gmail.com> writes:
> On Wed, May 1, 2013 at 10:00 AM, Marcin Borkowski <mbork@wmi.amu.edu.pl> wrote:
> Can you explain semantic vs. visual? As in you can more easily
> customize the meaning of \alert{} or \emph{} whereas \textbf{} and
> \textit{} only has one meaning? Sort of like using a css tag which can
> be later customized vs. specifically calling out exactly what you're
> thinking you want to do at the moment?
IMHO, the best discussion of this difference is the first chapter of
Lamport's LaTeX User's Guide and Manual. Here is the gist as I
understand it:
1) A principle of typesetting is that the layout of a document should
reflect its logical structure.
2) A computer typesetting program can achieve this if it knows what key
parts of the document mean.
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
The :: separator lets Org (and ultimately LaTeX) know that the part
before the separator is the term that is being described.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2013-05-01 21:42 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 [this message]
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=m1fvy62x9e.fsf@poto.myhome.westell.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.com \
--cc=mbork@wmi.amu.edu.pl \
/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).