Subject: Re: [xsl] encoding issues From: David Carlisle <davidc@xxxxxxxxx> Date: Wed, 3 Jul 2002 12:20:32 +0100 |
> 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
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] encoding issues, Julian Reschke | Thread | Re: [xsl] encoding issues, David Carlisle |
RE: [xsl] encoding issues, Julian Reschke | Date | Re: [xsl] encoding issues, David Carlisle |
Month |