W3C home > Mailing lists > Public > www-xsl-fo@w3.org > June 2003

Bug in XSLT processors ?

From: Dorfschmid, Jürgen <j.dorfschmid@msh.de>
Date: Tue, 17 Jun 2003 16:03:34 +0200
Message-ID: <B56A3A4C735ED2118F25000083687FBB0114A85A@mshnts04-tok.intern.msh.de>
To: "'www-xsl-fo@w3.org'" <www-xsl-fo@w3.org>
Hi there,
I'm desperately searching for some solution that seems
to be implementation specific for different XSLT processors. 

I've a XSL stylesheet that contains a single Linefeed character in a CDATA
section (no other characters in brackets). This linefeed is not translated
into the
result textfile (using Oracle Parser v2) unless at least
one other -printable- character stands beside the linefeed. The linefeed is
only translated correctly
if the CDATA contains more than this character.

Is there a setting to configure the XSLT processor or is this simply a bug ?
Need to produce x0Dx0A (CRLF) sequences platform independently. (Using
XMLspy 5.0 with default XSLT works perfectly). Is any
patch/update/workaround/help/suggesstion available out there ???

Thanks in advance

Received on Tuesday, 17 June 2003 10:58:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:58:27 UTC