Rodolphe VAGNER wrote:
> I think UTF-16 is not yet supported by FOP (UTF-8 since 0.20.3)
That's not a matter of support by FOP, because the
encoding matters only to the parser. Xerces, the
parser distributed with FOP, supports UTF-16.
Other parsers should do so as well, UTF-8 and
UTF-16 are the only two encodings *mandated*
by the spec (Section 2.2).
I think the issue is how it was generated by MSXML,
the XSLT processor overrides the xsl:output declaration
as well as the mandated default of UTF-8 by UTF-16 if
the result is temporarily written to a string, even if
it is written using UTF-8 (again, default) afterwards,
an puts an UTF-16 encoding into the XML declaration.
This is a common pitfall when using MSXML.
J.Pietschmann
