Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
Subject: Re: Improved (non-annoying) underlining
Date: 18 May 2000 21:56:04 -0700	[thread overview]
Message-ID: <ylwvkrnnob.fsf@windlord.stanford.edu> (raw)
In-Reply-To: Karl Kleinpaste's message of "18 May 2000 21:41:16 -0400"

Karl Kleinpaste <karl@charcoal.com> writes:

> So _this_ /kind/ of *emphasis* is the "ASCII art" way of _*showing*_
> _/real/_ */typographical/* _*/variation/*_.

Well, no, actually, it's not.  It may have started that way, but it's
become a language in its own right.  Saying *strong* is not the same thing
as a bold "strong" or an italic "strong," just like an underlined "strong"
isn't the same thing as an italic "strong" (although it's sometimes used
as an approximation).  It's no longer ASCII art, although it may once have
been.  It's punctuation now, just like smilies are, punctuation that
imparts inflection.  I use it as punctuation, and think of it as
punctuation; when I write *strong*, I'm not thinking "I want a bold
'strong' here but I can't do that in plain text."  I'm actually expressing
a verbal inflection, and I read *strong* directly as representing that
verbal inflection.

It may be possible to impart the same inflection ranges via more
traditional typographic techniques, but I think it's a massive and
mistaken simplification to claim that _word_ or *word* is nothing more or
less than an ugly way of indicating underline, italic, or bold.  Over the
past twenty years of on-line culture, it's become it's own thing, separate
from typographical conventions.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



  parent reply	other threads:[~2000-05-19  4:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-16 21:19 Karl Kleinpaste
2000-05-16 22:03 ` Shenghuo ZHU
2000-05-17 11:41 ` Bill White
2000-05-17 12:09   ` Per Abrahamsen
2000-05-17 12:26     ` Hrvoje Niksic
2000-05-17 15:37       ` Steinar Bang
2000-05-17 12:29     ` Karl Kleinpaste
2000-05-17 12:39       ` Hrvoje Niksic
2000-05-17 12:58         ` Karl Kleinpaste
2000-05-17 13:35           ` François Pinard
2000-05-17 13:55           ` Kai Großjohann
2000-05-17 14:03             ` Karl Kleinpaste
2000-05-17 14:27               ` Alan Shutko
2000-05-17 14:40               ` Kai Großjohann
2000-05-17 14:42                 ` Karl Kleinpaste
2000-05-17 16:00                   ` Yair Friedman (Jerusalem)
2000-05-17 14:08           ` Karl Kleinpaste
2000-05-17 14:32             ` Shenghuo ZHU
2000-05-17 14:29           ` Toby Speight
2000-05-17 15:22           ` Yair Friedman (Jerusalem)
2000-05-19  0:22           ` Russ Allbery
2000-05-19  1:41             ` Karl Kleinpaste
2000-05-19  2:09               ` Dan McGuirk
2000-05-19  4:56               ` Russ Allbery [this message]
2000-05-17 13:30   ` François Pinard
2000-05-17 14:28     ` Bill White
2000-05-17 14:33       ` Bill White
2000-05-17 14:34         ` Karl Kleinpaste
2000-05-17 18:05         ` Per Abrahamsen
2000-05-17 15:36   ` Indicating hidden threads (Was: Improved (non-annoying) ...) Steinar Bang
2000-05-17 16:07     ` Bill White
2000-05-17 20:13       ` Steinar Bang
2000-05-20  9:26         ` Rade Markovic

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ylwvkrnnob.fsf@windlord.stanford.edu \
    --to=rra@stanford.edu \
    /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.
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 NNTP newsgroup(s).