It's not the browser that is the problem. It's the xslt output that doesn't get right. I get the characters ?? instead of WWW&. "AffWrsluncher" commes out as "Aff??rsluncher".

How can you be sure?  When the application you are viewing the result
in doesn't having a mapping in the specified encoding for the byte
sequence, it may use a ? equally if it does have a mapping but the
font you are using doesn't have a glyph for the character then it may
use a ?

The only to way know for certain is to check the bytes using a hex
editor - if the byte is 0x3F then it really is a question mark,
otherwise it's just one of the above reasons.

cheers
andrew