xsl-list
[Top] [All Lists]

Re: 1.0 and 2.0 and suitability for tasks

2005-08-24 15:04:45
Access to an XSLT 2.0 processor through scripting doesn't seem that
difficult to implement without any browser developer involvement.

Cheers,
Dimitre Novatchev.

On 8/25/05, Manfred Staudinger <manfred(_dot_)staudinger(_at_)gmail(_dot_)com> 
wrote:
I would like to use XSLT 2.0 only. But as the client side
processing depends on browser support, I have to split
my application and keep the stylesheets for the browser
at XSLT 1.0.
Or is support for XSLT 2.0 coming soon in any browser?

Regards, Manfred

On 8/24/05, Dimitre Novatchev <dnovatchev(_at_)gmail(_dot_)com> wrote:
So I think the best thing we XSLTers can do for now is try 2.0 and assess
it on our own, not paying too too much attention to the marketers either 
way.

Cheers,
Wendell


Tried.

Assessed.

Remarkable results produced...

Just try to compare FXSL for XSLT 2.0  with FXSL for XSLT 1.0.


Cheers,
Dimitre Novatchev

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--




-- 
Cheers,
Dimitre Novatchev
---------------------------------------
Harry did not ask how Dumbledore knew; ...but Harry had long since
learned that bangs and smoke were more often the marks of ineptitude
than expertise.

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



<Prev in Thread] Current Thread [Next in Thread>