W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 1999

Re: double spaces

From: Chris Maden <crism@oreilly.com>
Date: Tue, 19 Jan 1999 15:58:15 -0500 (EST)
Message-Id: <199901192058.PAA10525@ruby.ora.com>
To: w3c-wai-ig@w3.org
[Jamie Fox]
> FrontPage 98 (make sure you have the update patch installed) allows
> for the double spaces between sentences.  HoTMetaL 4.0 does not.
> The only problem I've encountered with this technique is the old AOL
> proprietary browser (2.0 maybe) didn't recognize &nbsp; and showed
> it as such in the document.  However, it is important enough to me
> attempt to use proper English that I use the technique anyway.  For
> the few users using the old AOL browser they just end up with a
> little bit garbage.  The word to HTML conversion utility doesn't
> seem to save the double spaces nor does pasting from the clipboard
> to FrontPage98. I don't know about the use of CSS to achieve this.
> Our user base doesn't have full enough support for CSS to justify
> its use yet so I haven't studied it.

From a design point of view, HTML documents are more like typeset
documents than like typewritten ones.  In typesetting, one usually
leaves only one space at the end of a sentence; the two spaces in
typing are to compensate for the weird look of monospaced type.

TeX applies an algorithm for finding the end of sentences, and
slightly increases the spaces there, but not to a full double space.

I'd recommend avoiding fooling with hard spaces and let the browser do
its best job.

<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
"<URL>http://www.oreilly.com/people/staff/crism/ <TEL>+1.617.499.7487
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>
Received on Tuesday, 19 January 1999 15:58:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:03 UTC