[ http://issues.apache.org/jira/browse/XALANJ-2176?page=comments#action_12316395 ]
Henry Zongaro commented on XALANJ-2176: --------------------------------------- I've seen dumb editors and dumb IDEs do dumb things when they assumed ISO-8859-1 encoded files were really UTF-8 encoded (like refuse to display the files or mangle the offending characters upon saving the files), and I've seen a bug in a certain level of JDK produced by a certain vendor that caused javac to produce hard errors when it encountered what it thought were ill-formed UTF-8 characters which were really characters encoded in ISO-8859-1. I'd prefer to avoid the problem entirely. > Java source should avoid making assumptions about the platform default > encoding > ------------------------------------------------------------------------------- > > Key: XALANJ-2176 > URL: http://issues.apache.org/jira/browse/XALANJ-2176 > Project: XalanJ2 > Type: Bug > Components: Documentation > Versions: CurrentCVS > Reporter: Henry Zongaro > Assignee: Henry Zongaro > Priority: Trivial > Fix For: CurrentCVS > Attachments: patch.j2176.txt > > The files xml-xalan/java/src/org/apache/xml/utils/XMLString.java, > xml-xalan/java/src/org/apache/xml/utils/XMLString.java and > xml-xalan/java/src/org/apache/xpath/objects/XString.java all contain > characters that are encoded in ISO-8859-1. As they are contained in Javadoc > comments, I'd like to replace them with entity references in order to avoid > assumptions about the platform default encoding. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
