Re: Collapsing breaks & non-beaking spaces.

Liam Quinn (liam@htmlhelp.com)
Sun, 13 Jul 1997 23:36:45 -0400


Message-Id: <3.0.2.32.19970713233645.0088baa0@undergrad.math.uwaterloo.ca>
Date: Sun, 13 Jul 1997 23:36:45 -0400
To: www-html@w3.org
From: Liam Quinn <liam@htmlhelp.com>
Subject: Re: Collapsing breaks & non-beaking spaces.
In-Reply-To: <19970713.79728F0.11A2C@contessa.phone.net>

-----BEGIN PGP SIGNED MESSAGE-----

At 07:53 PM 13/07/97 PST, Mike Meyer wrote:
>> CSS1 removes the need for &nbsp;
>
>Well, using CSS1 instead of multiple &nbsp;'s in hopes they won't
>collapse is certainly an improvement. The intended use of &nbsp; - as
>an indicator that some space is not a candidate for word wrapping -
>would seem to be better done with &nbsp; than a SPAN and a style to
>keep it from wrapping. For a single space, anyway.
>
>Of course, removing the reason for abuse also removes the reason for
>wanting a statement about whether or not it collapses. After all, you
>should just use CSS1, which we want to encourage, right?

We've established that there is no use for multiple non-breaking spaces 
except as a presentation hack, so why not define the non-breaking space as 
collapsible?  The other alternatives are to define it as non-collapsible, 
which would give justification to the abuse, or to avoid a statement, 
which still leaves many people assuming that whatever Netscape does is the 
standard, de facto or otherwise.

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQB1AwUBM8meyw/JhtXygIx1AQENxQMAoHsukitV27HUaiaj1OhpKmAqAUGBm7FU
eHp7flymJXhPWHElBOCzJ40gTy1Wb7I3pLNVDszLGLdkXe4RFIi4OuXMUIA78pKE
xVX/6gvw+AZUy+CU2fWH5I2pkFk0D4IC
=3sKO
-----END PGP SIGNATURE-----

Liam Quinn
===============  http://www.htmlhelp.com/%7Eliam/  ===============
Web Design Group            Enhanced Designs, Web Site Development
http://www.htmlhelp.com/    http://enhanced-designs.com/
======  PGP Key at http://www.htmlhelp.com/%7Eliam/pgp.html  =====