Subject: Re: [xsl] Character substitution From: Jim Fuller <jim.fuller@xxxxxxxxxxxxxx> Date: Mon, 10 Jan 2005 12:31:46 -0500 |
Your input has a reference to unicode 128. that is a control character (on the meaning of which you explitly shouldn't depend).
control character (ie byte 128). If your browser happens to decide to be non conformant but friendly and show that as a euro, that's either good or bad, depending on your point of view. If you output to Windows-1252 then that doesn't have those control characters (as the space is taken
up with extra printing symbols) so you should get a fatal encoding error
telling you that you can't linearise character 128 into the windows encoding (as that slot is taken up to linearise character 8364). If however the encoding support silently lineraises both 128 and 8364 on to the same slot (so destroying the round tripping that is supposed to be preserved by linearisation) you will see a euro, but whether that is good or bad depends on your point of view...
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Character substitution, David Carlisle | Thread | Re: [xsl] Character substitution, David Carlisle |
Re: [xsl] Stylesheet optimisation, Jim Fuller | Date | Re: [xsl] Character substitution, Jim Fuller |
Month |