Re: [xsl] XSL > XSL trans. and Characher Encoding

Subject: Re: [xsl] XSL > XSL trans. and Characher Encoding
From: David Carlisle <davidc@xxxxxxxxx>
Date: Tue, 16 Oct 2001 23:33:08 +0100


> please explain to me why I do not get a nbsp charachter when my XSL has 
> &#160 ?

you do get the non breaking space character. But characters are logical
entities, and files are just streams of bytes, it is th efile encoding
that matches the two. In a latin-1 encoded file nbsp is a single byte
with value 160. In a utf-8 encoded file that single character is encoded
as two bytes. If you look at the file in a system that understands the
file encoding you will see a (non breaking) space, if you look at the
file in a system set up for the wrong encoding of course the bytes in
the file are displayed as the wrong characters. The bytes that denote
nbsp happen to appear as an accented A and a space, but essentialy it is
just random junk caused by your system incorrectly decoding the byte
stream.  

David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread