[ http://issues.apache.org/jira/browse/XALANJ-2176?page=comments#action_12316391 ]
elharo commented on XALANJ-2176: -------------------------------- While this wouldn't hurt anything, it seems unnecessary. The javadoc tool allows one to specify both the input encoding of the source documents and the output encoding of the generated documents. No assumptions about the platform default encoding are necessary at any point. > 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]
