Right, so far I came up with this:
in the resulting source using 'serialize html' the NO-BREAK-SPACE shows up as (i.e. the string, not the character), using 'serialize xhtml' it shows up as  (the character) followed by (the string).
Originally my XSL file added a metatag ...iso-8859-1, but I removed this. No effect. Close examination of the code: Internet Explorer 6.0 SP2 adds a metatag ...iso-8859-1 (when I changed the metatag in the XSL file to UTF-8 IE6 changed it to ISO-8859-1). I haven't found any setting in IE6 where I could change the encoding. Opera 7.21 displays the same results, whether with or without the metatag. In Opera I set the option 'encoding to assume for pages lacking encoding' to utf-8, but still the same result.
I use both browsers on my home pc too with the same results (I cannot say whether they are the exact same versions, but it is IE6.X and Opera 7.X)
I have never heard of such a strange effect and I can't imagine what the reason for it should be. You must have a crazy encoding specified somewhere if #160 is not nbsp. Are you using another encoding than UTF-8 or ISO-8859-1? Maybe only because of a typo?
Furthermore the meta tag *must* be removed from the XSLT, otherwise that's a possible root of many of errors of this type. The meta tag is added by the serializer, not by IE.
Have a look at your serializer declaration in the sitemap. What's the difference between 'html' and 'xhtml'?
And please test if you are using a recent Xalan using the environment check stylesheet: http://xml.apache.org/xalan-j/faq.html#environmentcheck.
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
