BURGHARD Éric wrote:
- handle the processing instruction by serializing
straight XML for those browsers that do support it, and process on the
server for others.
great idea !
By extension, why not having an XSLGenerator and an XSLReader ?
Hmm... you're starting to build p
>
> - handle the processing instruction by serializing
> straight XML for those browsers that do support it, and process on the
> server for others.
>
great idea !
>>By extension, why not having an XSLGenerator and an XSLReader ?
>>
>>
>
> Hmm... you're starting to build pipelines-in-one-com
BURGHARD Éric wrote:
Hi,
By looking at the XMLSerializer source code, i just realized that the
serialization was driven in fact by an xsl transformation (with no
stylesheet). So i wondered, why not giving this serialization a real
stylesheet ? That way i could overcome all the limitations of th
Hi,
By looking at the XMLSerializer source code, i just realized that the
serialization was driven in fact by an xsl transformation (with no
stylesheet). So i wondered, why not giving this serialization a real
stylesheet ? That way i could overcome all the limitations of the actual
XMLSerializer.
