Gnus development mailing list
 help / color / mirror / Atom feed
From: Ken McGlothlen <mcglk@serv.net>
Cc: ding@gnus.org
Subject: Re: highlighting and fontification
Date: 24 Sep 1999 17:47:02 -0700	[thread overview]
Message-ID: <87wvtfrf5l.fsf@ralf.serv.net> (raw)
In-Reply-To: "Edward J. Sabol"'s message of "Wed, 15 Sep 1999 18:13:31 -0400 (EDT)"

"Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov> writes:

| Personally, I believe that having two spaces at the end of a sentence is an
| antiquated convention born in an era of typewriters and fixed-width fonts.
| With the advent of computers and proportional spacing, the two-space
| convention is virtually useless and people are moving away from it.
| Professional typesetting for books, etc. has never followed it to begin with.
| Pick up any book, and you won't find the spacing between sentences to be any
| larger than the spacing between words.

(I realize that I'm answering this kind of late.)

I must respectfully disagree.  It's there, but it's smaller than two normal
spaces between words on the same line.  In justified text, it was considered
better to expand the space between sentences "faster" than the space between
words; in English-style typesetting, uniform spacing was considered "lazy."
(Of course, the *French* never followed this convention, but c'est la vie.)

Even TeX, possibly the most careful computerized implementation of typesetting
known to date, took this into account.  In extremely tight lines, by default,
the spacing was uniform, but as the line got looser, the space after sentences
would stretch three times faster than the space between normal words.

TeX, of course, had a \frenchspacing command that would revert to the French
style of uniform spacing.

But at least in English and often in German, larger spacing after
end-of-sentence marks was common, accepted, and considered good style.  And
that is what led to the two-space convention in typewriting.

Obviously, I still prefer it.  Call me a traditionalist, I guess.  :)

							---Ken


  parent reply	other threads:[~1999-09-25  0:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-09 17:51 Daniel Monjar
1999-09-09 21:55 ` Jack Vinson
1999-09-09 22:34 ` Karl Kleinpaste
1999-09-10 15:35   ` Stainless Steel Rat
1999-09-10 16:24     ` Kai Großjohann
1999-09-10 16:32       ` Emerick Rogul
1999-09-10 18:29       ` Stainless Steel Rat
1999-09-10 19:01         ` Kai Großjohann
1999-09-12  5:16           ` Stainless Steel Rat
1999-09-13  9:17             ` Michael Piotrowski
1999-09-13 18:32             ` Florian Weimer
1999-09-13 21:46               ` Mick Gower
1999-09-15 22:13                 ` Edward J. Sabol
1999-09-19  2:56                   ` Greg Stark
1999-09-25  0:47                   ` Ken McGlothlen [this message]
1999-10-05  1:40                   ` François Pinard
1999-10-05 14:13                     ` Hrvoje Niksic
1999-10-05 22:49                       ` Russ Allbery
1999-10-06  0:45                         ` David Coe
1999-09-14 12:33               ` Toby Speight
1999-09-14  8:24             ` Tibor Simko
1999-09-11  1:44         ` Rene H. Larsen
1999-09-11  7:06           ` Graham Murray
1999-09-12  5:05             ` Stainless Steel Rat

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=87wvtfrf5l.fsf@ralf.serv.net \
    --to=mcglk@serv.net \
    --cc=ding@gnus.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.
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).