This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: encoding issues


> True, but   is a non-breaking-space in anyones markup.
Yes but that's what's in teh input, but it isn't like that in the output
it apears as character data:

#160 is two bytes in utf-8 so if you read those two bytes as latin-1 you
will see two characters, the first being an accented A.

An alternative to utf-8 if you don't want utf-16 is us-ascii
then #160 would be output as   and would, as you say,
be understood in any encoding.

But to get the html browser to detect the right encoding you need to add
a meta element to the head, the html output method does that
automatically but in XML you need to do it by hand (which is a bit risky
in general as you can not be sure that teh system will use the encoding
you ask for)

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]