Re: [xsl] XPath 2.0 is not XPath 2.0

You wrote:

> (BTW, I sent a copy to the XPath comments address, but it never showed up,
> at least not in the archives, maybe there is some latency and/or moderator
> sitting in between?)

I am the moderator, and it's true that I'm sometimes late forwarding
messages to the list, especially when I'm away from a computer. But
there is a way around: if you are subscribed to the mailing list you
message will make it through directly. My moderating posts from
non-subscribers is a way to filter spam out.

Max.

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

Current Thread
RE: [xsl] SAXON Fatal Error UTF-8 sequence (character code: 0x63), (continued) Chris Bayes - Fri, 21 Dec 2001 16:43:25 -0000 Michael Kay - Thu, 20 Dec 2001 22:25:55 -0000 David Rosenborg - Fri, 21 Dec 2001 12:21:06 +0100 Zarella Rendon - Fri, 21 Dec 2001 21:51:11 -0600 Max Froumentin - Fri, 28 Dec 2001 13:48:41 +0100 <=

<- Previous	Index	Next ->
RE: [xsl] XPath 2.0 is not XPath 2., Zarella Rendon	Thread	Re: [xsl] Should "//ename[n]" mean , Jonathan Robie
Re: [xsl] Simplest way to return an, David Carlisle	Date	Re: [xsl] Functional trim(), Adriano Rodrigues Fe
	Month

<-prev [Thread] next->	<-prev [Date] next->
Month Index \| List Home