On 14/08/2012 14:35, Wolfgang Laun wrote:
If changing the file's encoding specification fixed the problem you
must have some byte sequences representing codepoints in
UTF-8, possibly besides others represented as entities.
No, it's pure 8-bit ASCII (well, 7-bit even); it's also the same
document being presented via two different paths. In one case it
was OK, in the other not. I'm completely baffled.
I have added "response.setEncoding("UTF-8")" to all my servlets
and the problem has gone away; I've also added a debug message
to my XSLT filter to display the encoding. (Oddly enough, my
error handling servlet still says ISO-8859-1 despite setting
the encoding.)
I hate it when something fixes a problem and I don't understand
what the original problem was or why the fix worked!
--
John English
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--