Lists Home |
Date Index |
Sanjay Goel wrote:
> ... if I put ™ or if I define a entity, the output in html
> is ™. So this html gets displayed differently on different
> browsers. I need ™ or ™ in the final html so that the
> browsers read it correctly.
This may be because you specified "xml" as the XSL output method but
serve the result as text/html. If you specify "html" as the output
method the transformer should include a content type with a charset
parameter in an http-equiv instruction in the generated HTML.
Ensure that you are serving the result correctly, with a charset
parameter the same as the charset you serialised the XSL result to.
So if you serialised to UTF-8 and you are serving as text/html you
should include the header
Content-Type: text/html; charset=UTF-8
for why you need to do this. The default for HTTP, without a charset
parameter, is ISO-8859-1, but this encoding does not contain the
trademark symbol and will therefore not work for you.
犬 Chris Burdess
"They that can give up essential liberty to obtain a little safety
deserve neither liberty nor safety." - Benjamin Franklin
This is a digitally signed message part