DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27983>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27983 xalan-j 2.6.0 converts all characters in specified encoding to character references [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|Other |Medium ------- Additional Comments From [EMAIL PROTECTED] 2004-05-02 20:50 ------- In some sense, this could be viewed as a request for an enhancement, because the result is correct, whether characters are encoded as character references or appear explicitly. However, it's not an entirely satisfactory behaviour - you probably requested ISO-8859-7 for a reason; if you didn't care, you would have specified UTF-8 or US-ASCII. I think the reason for the current behaviour is that the serializer is only able to handle a single contiguous range of Unicode characters when it decides which characters can be represented in the requested encoding. For ISO-8859-7, the characters that can be represented are not a single contiguous range of Unicode characters. To top it off, I see that there is a bug in the serializer in the range of characters specified for ISO-8859-7. It indicates that characters up to U+00FF can be represented, but that includes many characters from the Latin-1 character set that cannot be represented in the ISO-8859-1 encoding. I'll open a separate bug report for that. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
