2002-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 bug in libxslt HTMl serialization, Elliotte Rusty Harold
  • [xslt] [xslt]: Who has a real world use for a high --maxdepth?, Jean T. Anderson
  • [xslt] xsltproc bugreport (1.0.22/2.4.26) : key() call returns no nodes (DocBook XSL), Peter Bray
  • [xslt] xsltproc and zlib, Steinborn Thomas
  • [xslt] An URI, not a namespace, Igor Zlatkovic
  • [xslt] release of libxslt-1.0.22, Daniel Veillard
  • [xslt] cdata section, Panard
  • [xslt] nasty, Bernhard Zwischenbrugger
  • [xslt] [ENHANCEMENT REQUEST] give URI Resolver hooks in Python API accessto per-invocation data, Craeg K Strong
  • [xslt] New security features and Windows, Igor Zlatkovic
  • [xslt] Beginning for a security framework for libxslt, Daniel Veillard
  • [xslt] Bad link on http://xmlsoft.org/XSLT/docbook.html, Yves Pratter
  • [xslt] Re: [xml] Search engine is complete, Daniel Veillard
  • [xslt] xsl:value-of disable-output-escaping='yes' no longer working?, Garrett Wollman
  • [xslt] namespace prefix missing for root element in generated xml file, Dan Gohman
  • [xslt] xsltproc and include failure, Scott G. Brauer
  • [xslt] Non-existent variable => error?, Jerome Pesenti

  • Mail converted by MHonArc