[ http://nagoya.apache.org/jira/browse/XALANJ-2029?page=comments#action_56972 ] Joe Kesselman commented on XALANJ-2029: ---------------------------------------
The XML spec says parsers *must* accept any of CR, LF, or CRLF and convert them to an XML newline character. As of XML 1.1, the EBCDIC newline character is also equivalent to these. So as a Xalan bug, this is INVALID. If Crimson isn't accepting a file which uses one of these line break sequences, that should be reported as a bug against Crimson. (Is anyone stil maintaining Crimson?) Having said that, it would be a useful feature to be able to tell the Xalan serializer which of these sequences you want used on output. I seem to remember that Xalan-J currently uses whatever the JVM says is the platform's default newline representation. I honestly can't remember whether we've already provided an override option or not. If not, this is a valid ENHANCEMENT request. > XML file must contain LF, CRLF or CR are unsupported > ---------------------------------------------------- > > Key: XALANJ-2029 > URL: http://nagoya.apache.org/jira/browse/XALANJ-2029 > Project: XalanJ2 > Type: Bug > Components: Other > Reporter: Webbird > > When running the XSLT transformation on an input file, which contains CRLF > instead of LF, the Crimson parser doesn't work correctly. It throws an > InternalError in InputEntity.java:545... > However, I didn't test it with CR, but I'm quite sure that it don't work as > well... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
