dleslie 00/11/10 11:59:32
Modified: xdocs/sources/xalan DONE index.xml
Log:
Updates fo Xalan-J 1.2.1
Revision Changes Path
1.32 +5 -2 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- DONE 2000/11/10 18:40:19 1.31
+++ DONE 2000/11/10 19:59:32 1.32
@@ -1,9 +1,12 @@
<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 nodeset extension
function.<br/><br/></li>
+<li>Gary Peskin upgraded &xslt4j; to work with Xerces-Java
1.2.1.<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>Benoit Cerrina also submitted an enhancement to improve error reporting
when an extension element is not found.<br/><br/></li>
+<li>Gary Peskin fixed a bug where the procesor reset method() was not
resetting the list of stylesheet parameters passed in from a Java
program.<br/><br/></li>
+<li>Gary Peskin fixed a bug so that xsl:fallback elements are no longer
executed when the parent extension function is implemented and it processes its
own children (like redirect:write).<br/><br/></li>
+<li>John Ky submitted a fix to improve how Xalan handles whitespace
stripping and empty text nodes. As a result the HTMLFormatter no longer inserts
line breaks before font, s, strike, and nobr elements.<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>
1.13 +1 -1 xml-xalan/xdocs/sources/xalan/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/index.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- index.xml 2000/11/10 18:06:06 1.12
+++ index.xml 2000/11/10 19:59:32 1.13
@@ -64,7 +64,7 @@
is a complete and robust implementation of the W3C Recommendations for
XSL Transformations (XSLT) and the XML Path Language
(XPath).</p>
<p>Xalan can be used from the command line, in an applet or a servlet,
or as a module in other program. By default, it uses the Xerces XML parser, but
it can interface to any XML parser that conforms to the DOM level 2 or SAX
level 1 specification.</p>
- <p>This release incorporates a number of performance enhancements and bug
fixes, including patches submitted to the <human-resource-ref
idref="xalandev"/>. For example, we have added support for new extension
functions, and we have fixed a couple of bugs pertaining to the evaluation of
variables. For the details, see <link idref="readme">Release Notes</link>.</p>
+ <p>This release incorporates a number of performance enhancements and bug
fixes, including patches submitted to the <human-resource-ref
idref="xalandev"/>. For example, we have added a Tokenizer extension function,
and we have fixed a couple of bugs pertaining to the evaluation of variables.
For the details, see <link idref="readme">Release Notes</link>.</p>
</s2>
<s2 title="How do I get it?">
