RE: [xsl] MS XML Parser

["Ruane, Conleth" <Conleth dot Ruane at compaq dot com>]

Thanks Chris, that helped. Now I know where the escaped characters are
getting lost.

What I need now is an appropriate "StringStream" object to pass to
transformNodeToObject instead of a dom.

	doc.transformNodeToObject xsl, output

I've tried this:
--------
	dim FSO
	dim outFile
	set FSO = Server.CreateObject("scripting.FileSystemObject")
	set outFile =
fso.OpenTextFile(Server.MapPath("ttmp.txt"),2,true)
-------
but I get "Invalid procedure call or argument:
'doc.transformNodeToObject'".

Any suggestions?

Bye
Conleth Ruane
> COMPAQ  EMEA HQ IM, Munich
Telephone: +49-89-9392-4393
mailto:Conleth.Ruane@compaq.com

	

-----Original Message-----
From: Chris Bayes [mailto:chris@bayes.co.uk]
Sent: Friday, November 16, 2001 11:48 AM
To: xsl-list@lists.mulberrytech.com
Subject: RE: [xsl] 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


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