RE: [xsl] Variables and HTML

Subject: RE: [xsl] Variables and HTML
From: Carmelo Montanez <carmelo@xxxxxxxx>
Date: Fri, 11 Mar 2005 13:33:10 -0500
Hey All:

Thanks for the help and ideas and the rationale behind d.o.e.  Its been
a very insightful experience.  I think I will build the elements on the fly
and build elements rather than strings.  I may revisit this issue
next week.

Thanks,
Carmelo


At 12:23 PM 3/11/2005 -0600, Pieter Reint Siegers Kort wrote:
I wrote:

> I must say I learn a lot of things about XSLT since I joined the list.
Thanx again both of you for serving so intensive this list.

I forgot to add that other persons as well serve this list a lot. :-)

Cheers,
<prs/>

-----Original Message-----
From: Pieter Reint Siegers Kort [mailto:pieter.siegers@xxxxxxxxxxx]
Sent: Viernes, 11 de Marzo de 2005 12:19 p.m.
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [xsl] Variables and HTML

Thanx for the answer!

> Note that Michael is an editor and WG member so his answers are
> informed

Yeah, I know that, he's an incredible person

> I'm neither and my answers are guesses

:-) hey, common, we all know that your answers are not guesses - you know a
lot about the subject!

I must say I learn a lot of things about XSLT since I joined the list. Thanx
again both of you for serving so intensive this list.

Cheers,
<prs/>

-----Original Message-----
From: David Carlisle [mailto:davidc@xxxxxxxxx]
Sent: Viernes, 11 de Marzo de 2005 11:59 a.m.
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Variables and HTML



  OK, thanx Michael and David - you both are a complementing answering
machine
  :-)

Note that Michael is an editor and WG member so his answers are informed,
I'm neither and my answers are guesses:-)


That leaves me with the question why it is not encouragable to couple transformers and serializers... may we assume that serializers are kept out of the spec's domain is because serializers are too system specific?


See how one of the faq's of the microsoft implementation is that settings on xsl:output are ignored. the reason being that msxsl has output a DOM which has then been (possibly) further processed and then finally serialised using DOM methods. XSLT rather encourages this tree-in tree-out view of the XSLT transform process but if you to output a tree then currently (and perhaps always) you don't get to control the final serialisation. That's not necessarily bad, just a consequence of a pipelineing approach to the transformation, but it does mean that essentially everything about serialisation in XSLT is slightly second class as the spec wants to allow conforming systems that never serialise but always just pass on a result tree as a tree.

David


________________________________________________________________________ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________

Current Thread