Hi,

thanks. I've read the article, in fact I read the entire thread, but either
New Year's wine is still in my system (I don't drink :-)) or I've stumbled
onto a configuration problem/bug in <map:serialize type='xhtml'/>

Point is this: whether I enter &#160; or &#xA0; directly in my XSL
stylesheet or through an entity reference 
<!ENTITY nbsp "&#160;"> (or the hex code), when I tell the serializer to use
type xhtml I get an &Acirc; instead of &nbsp; when I change the type back to
'html' it works as expected.

Bye, Helma

> -----Original Message-----
> From: Martijn Bouterse [mailto:[EMAIL PROTECTED] 
> Sent: Monday, 05 January 2004 00:02
> To: [EMAIL PROTECTED]
> Subject: Re: Sudden difference in interpretation of #160 - update
> 
> 
> [EMAIL PROTECTED] wrote:
> 
> > Hi,
> > 
> > Good guess, but unfortunately both ideas don't work. In 
> character entity
> > references xhtml is similar to html 4, so both use the same 
> code for nbsp
> > (#160). As far as I can deduct from all the information, 
> UTF-8 includes
> > Latin-1, which includes the code for nbsp. 
> > 
> > So, in all encodings (ISO-8859-1 as well as UTF-8) the code 
> for nbsp is 160.
> > 
> > 
> > Any other ideas, guesses?
> 
> All things you wanted to know about nbsp:
> 
http://www.biglist.com/lists/xsl-list/archives/200211/msg00276.html

Hope that helps,

Martijn Bouterse


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to