Gnus development mailing list
 help / color / mirror / Atom feed
From: "Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov>
Subject: Re: highlighting and fontification
Date: Wed, 15 Sep 1999 18:13:31 -0400 (EDT)	[thread overview]
Message-ID: <199909152213.SAA72350@alderaan.gsfc.nasa.gov> (raw)
In-Reply-To: <m3d7vmpjr7.fsf@dexter.clara.co.uk> (message from Mick Gower on 13 Sep 1999 22:46:36 +0100)

Excerpts from mail: (13-Sep-99) Re: highlighting and fontification by Mick Gower
>>> A couple of others that I can think of: American typography
>>> (typographical convention) puts two spaces after the punctuation that
>>> ends a sentence, European typography tends to use only one[1].
>
>> Jan Tschichold recommends putting an extra space after a such a
>> punctuation (except for very dense lines, of course). So this isn't a
>> purely American convention.
>
> The British Military had a manual for typography and that, IIRC, is two
> spaces after the and of a sentence ie after full stop, question mark
> and exclamation mark and one space after a break in a sentence ie after
> a comma or semi-colon. I think the manual was known as the JSP101.

For what it's worth, it's not cut and dry here in the U.S. either, despite
what the Rat says.

According to MLA (Modern Language Association) guidelines (the standard most
universities follow), either one or two spaces are permissible following
end-of-sentence punctuation when typing a paper. Neither one nor two is
stated as the preferred choice.

However, other guidelines, such as the APA (American Psychological
Association) style, require only a single space after end-of-sentence
punctuation.

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.

The above information concerning the MLA and APA styles was obtained from _A
Writer's Reference_, 4th Edition, by Diane Hacker.


  reply	other threads:[~1999-09-15 22:13 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 [this message]
1999-09-19  2:56                   ` Greg Stark
1999-09-25  0:47                   ` Ken McGlothlen
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=199909152213.SAA72350@alderaan.gsfc.nasa.gov \
    --to=sabol@alderaan.gsfc.nasa.gov \
    /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).