Saxon never attempts to convert a newline to CRLF on output. It's possible
of course that the operating system (or Java runtime) might do so, but it
seems unlikely. If you open a file written by Saxon in a text editor, it's
always possible that the text editor has converted the newline to a CRLF.
Michael Kay
http://www.saxonica.com/
-----Original Message-----
From: Paul Venuti [mailto:venutip(_at_)hotmail(_dot_)com]
Sent: 03 May 2006 22:57
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] Cannot output CRLF
Hi Owen,
Sorry, just saw your message in my inbox after I replied to
Michael. I'm invoking Saxon from the command line on a
Windows XP Pro system, like so:
C:\BMtest>java net.sf.saxon.Transform -o bpam-out.txt
bpam.xml crlf.xsl
Warning: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor
Just so we're both on the same page, I upgraded to the latest
A version:
C:\BMtest>java net.sf.saxon.Transform -t Saxon 8.7.1J from
Saxonica Java version 1.4.0_04
and ran it again. Still the same result.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--