Ok,

I've just checked out, each of my CDATA sections is contained into an
element that I can easily parse. Thanks!

I still have no idea on how to save the contents of those CDATA
sections (that is XML code itself) into separate files for each CDATA
section I encounter... I suppose it is a common issue in XSL
transformation, but I cannot find examples in my searches....

Any idea?

Thanks again for the explanation of the CDATA section... as far as I
can understand the use of those sections allow me to freely insert all
the raw data I need in the resulting XML (resulting from the XSL
transformation i mean...)

On Apr 1, 2005 11:11 AM, Kirkham, Pete (UK) <pete.kirkham@xxxxxxxxxxxxxx> wrote:
> 
> CDATA sections are un-escaped character data, not elements.
> 
> They are transparent to XSLT applications, so
> 
> <foo><![CDATA[.....snip.....]]></foo>
> 
> and
> 
> <foo>.....snip.....</foo>
> 
> are logically the same.
> 
> Use the normal text selection mechansim to get the equivalent text content.
> 
> <value-of select="foo"/>
> 
> If you have a sequence of CDATA sections, you won't be able to use XSLT to separate them, as
> 
> <foo><![CDATA[text from section one]]><![CDATA[text from section two]]></foo>
> 
> and
> 
> <foo>text from section onetext from section two</foo>
> 
> are logically the same.
> 
> Pete
> 
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************