Re: What about  ?

Arnoud (
Tue, 30 Jul 1996 19:43:37 +0200

From: (Arnoud "Galactus" Engelfriet)
Subject: Re: What about  ?
Date: Tue, 30 Jul 1996 19:43:37 +0200
Message-ID: <Jnk/>

In article <960730142439_100320.1303_JHF122-1@CompuServe.COM>,
Jonathan Rosenne <100320.1303@CompuServe.COM> wrote:
> Arnoud "Galactus" Engelfriet wrote:
> >The reason I asked is because RFC 1866 is less than clear about the use
> >of &nbsp;. 
> I think it is very clear: It just says nothing at all. Therefor, NBSP is just a 
> regular character with no special handling, just like the RFC does not say 
> anything specific about the letter G.

It's called "non-breaking SPACE". Elsewhere, it says that multiple spaces
should be collapsed. I don't think it's unreasonable to assume that the
nbsp entity should be treated as a space because it's named as such.
And given the statement in the expired HTML 3.0 draft[0]

Non-breaking Space (&nbsp;)

   This should be treated in the same way as the space character (ASCII
   character code 32 decimal), except that the user agent should never
   break lines at this point.  It is useful when you want to ensure that
   neigbouring words always stay together and don't get split across

> But the RFC does discourage the use of NBSP. I thing it is not useful to elaborate
> on the use of something the use of which is discouraged.

I think that part of the RFC is slightly outdated right now; most if not
all current browsers support non-breaking spaces in the manner they were
intended for - preventing linebreaks at that point.

[0] <URL:>
To find out more about PGP, send mail with HELP PGP in the SUBJECT line to me.
E-mail: - Please PGP encrypt your mail if you can.
Finger for public key (key ID 0x416A1A35).
Anonymity and privacy site: <>