2008-October Archive by Thread

Messages are ordered newest-to-oldest in this index. The newest threads will be at the top of this page, the oldest will be at the bottom.

Within a single thread, the first mail note is the START of the thread; the notes following that are in the chronological order of when they were received. So globally, newest messages are at the top, but within a thread, the oldest (the start of the thread) is at the top.

If you think about it, it is confusing. Just go with the flow and everything will be all right.

  • [xslt] Possible parsing bug?, Dave Connet
  • [xslt] ancestor-or-self question, vincent leycuras
  • Re: [xslt] [xml] [PATCH] Build shared library on Win32, Daniel Veillard
  • [xslt] Problem with extension element namespaces and xsl:include?, Tony Graham
  • [xslt] Seg fault on something to do with predicates, maybe, Mark Howe
  • [xslt] Seg fault on something to do with predicates, Mark Howe
  • [xslt] Bug (?) in attribute set resolver?, Jonathan S. Shapiro
  • [xslt] data callbacks?, Paul Miller
  • Re: [xslt] xslt Digest, Vol 54, Issue 6, Subscribe, SAEID BESYARFARD
  • [xslt] Regarding Common Extension Function (EXSLT), Ashwin
  • [xslt] Conditional includes or definitions, Sam Liddicott
  • [xslt] libxslt fails, xsltproc works, Sam Liddicott
  • [xslt] Parsing and marking up text into xml with libxslt, Sam Liddicott
  • Re: [xslt] [PATCH] patterns.c can dereference NULL when node has no parent, Daniel Veillard
  • [xslt] threaded use with xsltCleanupGlobals(), Sam Liddicott

  • Mail converted by MHonArc