This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: MS XML Parser


> I'm not looking for a *special* CR I want to output the 
> escaped characters that represent the CR. SAXON does it and 
> XML-Spy does it (and that actually uses MS XML Parser).
> 
Well in fact you are. What you are doing with 
<xsl:text
disable-output-escaping="yes">XXXX&amp;#x0D;&amp;#x0A;YYYY</xsl:text>
is generating XXXX&#x0D;&#x0A;YYYY in the output. When you do this with
saxon or xml-spy you are usually writing out to a file so it stays as
is. With your asp you are transforming it to another dom and I suspect
that it sees the string XXXX&#x0D;&#x0A;YYYY and converts that to a
single lf.
You can test that by doing a doc.transformNodeToObject xsl, Request
which should stream the XXXX&#x0D;&#x0A;YYYY directly to the client. If
you really need to go via the third dom then you could try
XXXX&amp;amp;#x0D;&amp;amp;#x0A;YYYY.

Ciao Chris

XML/XSL Portal
http://www.bayes.co.uk/xml


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]