dleslie     00/11/10 10:40:20

  Modified:    xdocs/sources/xalan DONE
  Log:
  Updates fo Xalan-J 1.2.1
  
  Revision  Changes    Path
  1.31      +3 -3      xml-xalan/xdocs/sources/xalan/DONE
  
  Index: DONE
  ===================================================================
  RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
  retrieving revision 1.30
  retrieving revision 1.31
  diff -u -r1.30 -r1.31
  --- DONE      2000/11/10 18:27:23     1.30
  +++ DONE      2000/11/10 18:40:19     1.31
  @@ -1,10 +1,10 @@
   <s3 title="Changes since &xslt4j; version 1.2.">
   <p>We have applied a number of enhancements and bug fixes, including patches 
submitted by developers to <human-resource-ref idref="xalandev"/>. If you run 
across a problem with &xslt4j;, we strongly encourage you to write a patch and 
submit it to us. We will review it to make sure it doesn't break something 
else, and (assuming it doesn't) include it in our next release. In the interest 
of fixing bugs, adding enhancements, and addressing a host of thorny design 
issues, we sincerely want (and need!) your active participation in the ongoing 
development of Xalan.</p>
   <ul>
  -<li>Gary Peskin posted fixes to the node-set extension 
function.<br/><br/></li>
  -<li>Benoit Cerrina submitted a Tokezenizer extension function.<br/><br/></li>
  +<li>Gary Peskin posted fixes to the nodeset extension 
function.<br/><br/></li>
  +<li>Benoit Cerrina submitted a Tokenizer extension function. For more 
information, see <jump 
href="apidocs/org/apache/xalan/xslt/extensions/Tokenizer.html">Tokenizer</jump><br/><br/></li>
   <li>John Ky submitted a fix to improve how Xalan handles whitespace 
stripping and empty text nodes.<br/><br/></li>
  -<li>We fixed a bug in which a global variable was declared to be out of 
scope when referenced by another variable.<br/><br/></li>
  +<li>We fixed a bug in which a global variable was reported to be out of 
scope when referenced by another variable.<br/><br/></li>
   <li>We also fixed a bug evaluating global variables when processing SAX 
input.<br/><br/></li>
   <li>We fixed a bug in which the default XSLT processor was failing to shift 
to the Xerces liaison and DOM parser to process DOM input.<br/><br/></li>
   <li>Ritesh Kumar submitted a fix to the sample servlet to correctly obtain 
the server port from the HttpServletRequest object.</li>   
  
  
  

Reply via email to