You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by dl...@apache.org on 2001/05/22 20:32:06 UTC
cvs commit: xml-xalan/java/xdocs/sources/xalan readme.xml
dleslie 01/05/22 11:32:06
Modified: java/xdocs/sources/xalan readme.xml
Log:
Minor editorial corrections.
Revision Changes Path
1.34 +2 -2 xml-xalan/java/xdocs/sources/xalan/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/readme.xml,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- readme.xml 2001/05/21 15:12:39 1.33
+++ readme.xml 2001/05/22 18:31:58 1.34
@@ -80,7 +80,7 @@
<anchor name="done"/>
<s3 title="Changes since &xslt4j; 2.0.1">
&xsltcdone;
- <p>This release also includes a number of bug fixes to the &xslt4j; and TrAX core and Xalan-Java 1 compability API.
+ <p>This release also includes a number of bug fixes to &xslt4j; and TrAX.
We have also enhanced the ApplyXSLT servlet. It can now be set up to use a compiled Templates object to respond to multiple
client transformation requests involving the same stylesheet.</p>
&done-j;
@@ -124,7 +124,7 @@
issues, we sincerely want (and need!) your active participation in the ongoing development of Xalan.</p>
<p>Xerces bug in &xml4j-used;:</p>
<ul>
- <li>&xml4j; 1.2.3 does not process namespaces in SAX events when parsing UTF-16 documents, which causes &xslt4j; to fail with UTF-16
+ <li>&xml4j-used; does not process namespaces in SAX events when parsing UTF-16 documents, which causes &xslt4j; to fail with UTF-16
documents. Xerces will post a fix shortly.<br/><br/></li>
</ul>
</s3>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-cvs-help@xml.apache.org