emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Austin Frank <austin.frank@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: exporting typefaces
Date: Tue, 06 Jun 2006 10:55:18 -0400	[thread overview]
Message-ID: <44859756.2040307@gmail.com> (raw)
In-Reply-To: <71a070a2608a81e06f9021529536ddce@science.uva.nl>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Carsten Dominik wrote:

> I have never even once in my lifetime applied two different styles to
> a piece of text.  What is the application of this?

Looking through a few O'Reilly books on my shelf, I see that different
books use constant-width bold (<b><pre>text</pre></b>) and
constant-width italics (<i><pre>text</pre></i>) to indicate where a user
should enter input in example code.

I've been writing a tutorial for use in my lab, and have wanted the
ability to typographically distinguish between optional and required
parts of our in-house scripting language.  I'd like to say

    All *bold* terms are properties of a certain part.  All
    /*italic bold*/ terms are required properties of that part.

I don't know if this request is common enough to warrant inclusion, or
how much of a pain it would be to add to the parser, but that's the
first example off the top of my head of where I'd use this kind of
formatting.

Thanks,
/au

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEhZdVlHMl2/XbR4ERAh7AAKCexPBqwT5cXTmeeIv0GeiIT7dx8gCgtF5p
ODgsAQccvx72clftxlD3J3s=
=lRQH
-----END PGP SIGNATURE-----

next prev parent reply	other threads:[~2006-06-06 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 14:26 exporting typefaces Austin Frank
2006-06-06 14:33 ` Carsten Dominik
2006-06-06 14:55   ` Austin Frank [this message]
2006-06-07 10:21     ` Carsten Dominik

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=44859756.2040307@gmail.com \
    --to=austin.frank@gmail.com \
    --cc=dominik@science.uva.nl \
    --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

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).