RE: [xsl] data vs. xml

Subject: RE: [xsl] data vs. xml
From: "Passin, Tom" <tpassin@xxxxxxxxxxxx>
Date: Thu, 3 Apr 2003 12:32:34 -0500
[bix xslt]All,
> 
> Is there a way to identify a node as containing cdata?
> 
> eg.
> <node>
> <dataNotNewXMLTag1, dataVala, dataValb, moreData, ...>
> <dataNotNewXMLTag2, dataVala, dataValb, moreData, ...>
> <dataNotNewXMLTag3, dataVala, dataValb, moreData, ...>
> <dataNotNewXMLTag4, dataVala, dataValb, moreData, ...>
> <dataNotNewXMLTag5, dataVala, dataValb, moreData, ...>
> </node>
> 

> I want to write a simple xsl script that would translate the 
> above into 
> something more manageable for XSLT processing:
> 
> eg.
> <node>
> &lt;dataNotNewXMLTag1, dataVala, dataValb, moreData, ...&gt;
> &lt;dataNotNewXMLTag2, dataVala, dataValb, moreData, ...&gt;
> &lt;dataNotNewXMLTag3, dataVala, dataValb, moreData, ...&gt;
> &lt;dataNotNewXMLTag4, dataVala, dataValb, moreData, ...&gt;
> &lt;dataNotNewXMLTag5, dataVala, dataValb, moreData, ...&gt;
> </node>
> 

You had better explain more about what you really want to do.  If you
simply want to not process those elements, that is easy (assuming that
they really are in xml, unlike what you wrote above).  If they are not
well-formed xml, and they are not escaped, then your stylesheet will
never get to see them.

Also, what do you mean "more manageable for XSLT processing"?  That
depends on __what__ processing you have in mind.

As it stands, your question is unintelligble and will require anyone who
tries to answer it to make a lot of assumptions that will probably not
match what you are thinking of.


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


Current Thread