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...@locus.apache.org on 2000/06/22 23:27:56 UTC
cvs commit: xml-xalan/xdocs/sources/xalan DONE
dleslie 00/06/22 14:27:56
Modified: xdocs/sources/xalan DONE
Log:
updates for 1.1.D01.
Revision Changes Path
1.12 +5 -1 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- DONE 2000/06/22 17:01:58 1.11
+++ DONE 2000/06/22 21:27:55 1.12
@@ -7,7 +7,11 @@
<li>&xslt4j; was not using the xsl:output standalone attribute to place document standalone declarations in the output. If the standalone attribute is set to "yes", &xslt4j; now includes a standalone document declaration in the output. If the standalone attribute is set to "no", &xslt4j; does not yet place a standalone document declaration in the output; this will be fixed soon.<br/><br/></li>
<li>Text nodes with entity references are not handled correctly by the Document Table Model (<link idref="dtm">DTM</link>). We have not yet fixed this bug.<br/><em>Workaround:</em> instantiate the XSLTProcessor as follows so it uses the <resource-ref idref="XercesLiaisonDoc"/> and the Xerces DOM parser:<br/>
<code>org.apache.xalan.xslt.XSLTProcessor xsltProc =</code><br/> <code>org.apache.xalan.xslt.XSLTProcessorFactory.getProcessor(</code><br/>
-<code> new org.apache.xalan.xpath.xdom.XercesLiaison());</code></li>
+<code> new org.apache.xalan.xpath.xdom.XercesLiaison());</code><br/><br/></li>
+<li>xsl:key declarations in imported stylesheets do not work. We have not yet fixed this bug.<br/><em>Workaround:</em>
+place all xsl:key declarations in the top-level stylsheet, even if used in the imported stylesheets.<br/><br/></li>
+<li>When key() function encountered an attribute set to a null string, keyt() ignored all subsequent nodes(). This has been fixed. <br/><br/></li>
+<li>We fixed a namespace resolution problem in the XPathAPI eval() method (included with the ApplyXPath sample).<br/><br/></li>
</ul>
<p>We have upgraded support for using Apache Ant to build &xslt4j;. For the details, see <link anchor="ant">Using Ant</link>.</p>
</s3>