Re: killing xslt

Hello!

By the way, here is more detailed explanation - "Why You Won't See XSLT2.0 or XPath 2.0 in the Next Version of the .NET Framework" by DareObasanjo, http://blogs.msdn.com/dareobasanjo/archive/2004/05/13/131166.aspx

--
Oleg Tkachenko
http://blog.tkachenko.com
Multiconn Technologies, Israel

<Prev in Thread]	Current Thread	[Next in Thread>
RE: killing xslt, (continued) RE: killing xslt, B Tommie Usdin error using number(), Mike Ferrando RE: error using number(), Michael Kay change stylesheet encoding, Mike Ferrando RE: change stylesheet encoding, Michael Kay Re: change stylesheet encoding, David Carlisle RE: killing xslt, Michael Kay Re: killing xslt, David Carlisle RE: killing xslt, Michael Müller-Hillebrand Re: killing xslt, David Carlisle Re: killing xslt, Oleg Tkachenko <= Re: killing xslt, Wendell Piez RE: killing xslt, Michael Kay RE: killing xslt, bry RE: killing xslt, M. David Peterson RE: killing xslt, David . Pawson RE: killing xslt, David . Pawson RE: killing xslt, Michael Kay RE: killing xslt, bry RE: killing xslt, M. David Peterson RE: killing xslt, Pieter Reint Siegers Kort

Previous by Date:	RE: two namespaces and a position problem, April Fleming
Next by Date:	RE: XSLT Disable-Output-Escaping Not Working, Michael Kay
Previous by Thread:	Re: killing xslt, David Carlisle
Next by Thread:	Re: killing xslt, Wendell Piez
Indexes:	[Date] [Thread] [Top] [All Lists]