W3C home > Mailing lists > Public > www-amaya@w3.org > July to September 2009

Re: newbie &nbsp representation question

From: Stanimir Stamenkov <s7an10@netscape.net>
Date: Sat, 08 Aug 2009 14:34:43 +0300
Message-ID: <4A7D62D3.40301@netscape.net>
To: www-amaya@w3c.org
Mon, 3 Aug 2009 16:36:58 -0600, /J. Waldram/:

> Amaya 11.2, with the "Keep multiple 
> Spaces" option, the &nbsp is represented as a hex byte 0xa0 instead of 
> &#160; or &#xa0;.  Is this a mis-translation for the &nbsp that is 
> rendered by browsers?  Since XML does not allow &nbsp and the &#xa0 is 
> allowed could this be recoded as a text string not a hex byte?

It is not a "hex byte" but the NBSP character included literally in 
the text (if you choose UTF-8 or another UTF variant then the 
character will be represented by two or more bytes).  I guess it is 
included like that as it gets just one character in the source vs. 6 
(&nbsp; or &#160; or &#xA0;).  If you set your source encoding to 
US-ASCII then this character cannot be literally encoded therefore 
Amaya will write it as &nbsp;.

Received on Saturday, 8 August 2009 11:35:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:30:57 UTC