Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: RDF to HTML with XSLT

From: JasonBurr@-----------.---------.---
To: NULL
Date: 1/7/2005 12:21:00 PM
Joe,

Tried 3.0 to no avail. Server does not have 4.0 installed so not an option. 
Though I don't think thats the core issue. 

I do response.write oXML.xml without setting contenttype to text/xml (which 
I wouldn't be doing anyway as the actual content type output to client would 
be text/html). Anyway I suspect based on what others have said that this may 
inacurately convey what the encoding type is. However doing this

strOutPut = oXHTTP.responseText 
Response.Write strOutPut
Produces this at client
<?xml version="1.0" encoding="utf-8"?>

Doing this
oXML.loadXML(strOutPut)
Response.Write oXML.xml
Produces this at client
<?xml version="1.0"?>

My assumption and possibly very wrong is that the same is true when I do the 
transformNodeToObject call and apply the xsl to it thus a different encoding. 

I will post full code in response to Martins post.

Thanks again to everyone for their comments and suggestions.

Jason


"Joe Fawcett" wrote:

> "Jason Burr" <JasonBurr@d...> wrote in message 
> news:00A280D4-63FB-4057-9B68-999FA0FE36ED@m......
> > Ok esplain this to me por favor. I don't get it.
> >
> > Using Msxml2.ServerXMLHTTP and retrieving the data then printing out the
> > responseText it shows encoding as utf-8 (as supplied by the data 
> > provider).
> >
> > After loading the responseText into the Microsoft.XMLDOM via the loadXML()
> > and printing out the .xml data it strips out the encoding type.
> >
> > Whats more puzzeling is that everything I have read seems to say that the
> > dom will default to utf-8 so why would it have stripped the encoding and 
> > not
> > work with it (the xsl)?
> >
> > Also for whatever reason I can not get resonpseXML to work in loading the
> > dom only responseText. I tried Set oXML = oXHTTP.responseXML and oXML =
> > oXHTTP.responseXML and loadXML(oXHTTP.responseXML) the list goes on to no
> > avail. At best I get nothing (though there is clearly an error) and at 
> > worst
> > it errors out. (where oXML is Microsoft.XMLDOM and oXHTTP is
> > Msxml2.ServerXMLHTTP)
> >
> > Why on gods green earth would the dom alter the contents of the xml loaded
> > into it without some explicit declaration to do so? Further what can I do 
> > to
> > avoid this. I realize that this has strayed off topic some but since it
> > started here.....
> >
> >
> >
> Try using the latest versions, msxml2.serverxmlhttp.4.0.
> 
> How do you know the encoding declaration is stripped? Showing dom.xml aways 
> shows in utf-16 without a declation because it's a string.
> 
> Joe (MVP-XML)
> 
> 
> 


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent