Re: XSL and xml entities that need to be translated

Hi Mike,

Thanks for responding.

I have taken a step back and started using SSI to include the xml/xsl in a
standard html table/page.  It seems pretty fast when I am the only one
hitting the server :)

We have been trying to make a client side tool that reads/writes/edits
xsl/xml.  We are using different shells to display tabular data in many
different formats.

I was thinking there was a way to write nested xsl transformations.

oh well...

>
> XSL does not act on documents; it acts on node trees that are usually
> derived from documents. The trees are typically constructed using logical
> information about an XML document, as returned from an XML parser.
>
> Parsers report on logical, not physical, structures (for the most part).
> Entity references, when they point to parsed entities, are typically
> 'resolved' (swapped out with their replacement text) by the parser. There
> are some occasions when references to external general entities do not
> have to be resolved, but I doubt that's what's happening here.
>
> Without knowing further details I would guess that you're either using 2
> different parsers (unlikely, as you didn't say so but you're apparently
> using IE 5.0 for both cases), or something is amiss with your stylesheet.
> Either way, your XML is fine. Post your stylesheet and tell us what XSL
> processor and XML parser you're using.




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