[
http://nagoya.apache.org/jira/browse/XALANJ-2029?page=comments#action_57003 ]
Brian Minchau commented on XALANJ-2029:
---------------------------------------
Joe is right. The serializer queries the JVM with
System.getProperty("line.separator");
Although this is not a documented, or supported way of doing this, you could
call System.setProperty with "line.separator" and specify a string with the
chacter(s) of interest before using Xalan. I'm not sure what will happen in a
server environment when you do this, you could impact all users!
If the serializer did have a public, supported API for setting the line
separator what would it be? A Xalan specific attribute/value pair on an
<xsl:output ..../> element?
<xsl:output ... xalan:line-sep="\u0008" .../>
where xalan is the prefix pointing to some Xalan
namespace URI, like xalan:indent-amount.
(see http://xml.apache.org/xalan-j/usagepatterns.html
for information on indent-amount ).
> 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]
