Thanks to all for pointing me in the right direction.
The problem indeed turned out not to be saxon related at all. It was
WebLogic changing the response header content type to "text/html;
charset=ISO-8859-1" just before the data got sent out to the browsers.
The working fix was to reset the content type (at the last possible
moment) back to "text/xml; charset=UTF-8".
I spent the majority of time scrutinizing innocent code since it
turned out to be an assumption error (that the other parts of the code
were correct). We never discovered this issue before because we never
returned any character beyond the US-ASCII set (any special characters
were escaped by returning the entity references instead).
Again, many thanks to all.
On 12-May-09, at 4:06 AM, Stefan Krause <stf@...> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Michael Kay schrieb:
>> Well, if the DTD containing the definition of the entity has been
>> mis-encoded, then this is a possibility. You haven't said whether
>> the DTD is
>> internal or external. If it's internal, then yes, saxon:parse()
>> accepts a
>> string as input, and someone has to decode bytes to create that
>> string, and
>> if they decode the bytes using the wrong encoding (follow me?) then a
>> problem could arise at this point. So it rather depends where your
>> comes from.
>>> So I'm guessing the encoding type is somehow determined by
>>> the environment default? If this is not the case then I
>>> don't have a clue what else may be causing this anomaly.
> Victor, please check how • is defined. If the definition is
> like "•" (from the Windows-1252 encoding), try to use
> "•" (Unicode-Codepoint) instead.
> Best regards,
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances!
> production scanning environment may not be a perfect world - but
> thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW
> KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> saxon-help mailing list archived at http://saxon.markmail.org/