dleslie 00/12/18 14:24:47
Modified: java/xdocs/sources/xalan BUGS DONE Log: Updates for beta release. Revision Changes Path 1.8 +4 -24 xml-xalan/java/xdocs/sources/xalan/BUGS Index: BUGS =================================================================== RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/BUGS,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- BUGS 2000/12/18 14:27:42 1.7 +++ BUGS 2000/12/18 22:24:47 1.8 @@ -1,33 +1,13 @@ <s3 title="Open bugs and bug reporting"> <p>We are aware of the following limitations and problems in this beta release:</p> <ul> -<li>When format-number() should format NaN or infinity, it generates the wrong string if default strings are used. <em>Workaround:</em> declare the strings in an xsl:decimal-format instruction at the top of the stylesheet.<br/><br/></li> -<li>Text nodes containing entity references are split into multiple nodes.<br/><br/></li> - -<li>The contains() function does not always recognize a character entity.<br/><br/></li> <li>There are differences in the way 1.x and 2.0. handle space and linefeed characters.<br/><br/></li> -<li>In some cases, a named character (" etc.) will be output when the literal character would have worked.<br/><br/></li> -<li>In some cases, a named character (© etc.) will be output where 1.x would put out &#ddd; or %hh encoding.<br/><br/></li> +<li>In some cases, a named character (© etc.) will be output where 1.x would put out a literal character.<br/><br/></li> <li>In some cases, a linefeed will be output where 1.x put out &#10;.<br/><br/></li> -<li>In some cases, %hh encoding will be used in HTML attributes instead of a named character (e.g., ä).<br/><br/></li> -<li>In some cases, &#ddd; encoding will be used in HTML attributes instead of %hh encoding.<br/><br/></li> -<li>Sometimes an <?xml...?> header is not being output when it should be.<br/><br/></li> -<li>Sometimes a META tag is output as it should be, but sometimes it's still missing or in the wrong place.<br/><br/></li> -<li>Sometimes a namespace declaration is missing or placed differently than before.<br/><br/></li> +<li>In some cases, %hh encoding will be used in HTML URI attributes instead of a named character (e.g., ä) or a literal character.<br/><br/></li> <li>Sometimes a declaration for the default or XSLT namespace is added when not needed.<br/><br/></li> -<li>Some torturous axis paths came back with too many nodes.<br/><br/></li> -<li>The function-available and element-available tests don't report true for XSLT elements.<br/><br/></li> -<li>The namespace-alias capability is putting out the wrong prefix (needs research).<br/><br/></li> -<li>The name() function is not returning the null string for text and comments, as it should.<br/><br/></li> -<li>Some required CDATA markers are not being put out.<br/><br/></li> -<li>The special technique for generating boolean attributes in HTML doesn't work.<br/><br/></li> -<li>The xsl:version put out by system-property is not the spec version, as it should be.<br/><br/></li> -<li>A top-level variable/parameter declaration in an imported/included stylesheet is not global, as it should be.<br/><br/></li> -<li>Path steps beyond a union causes an invalid axis error.<br/><br/></li> -<li>Unable to select a variable with a QName.<br/><br/></li> -<li>Use of key() in match pattern has problems with descendants.<br/><br/></li> -<li>The unparsed-entity-uri() function fails.<br/><br/></li> -<li>The @namespace:* pattern is not assigned the appropriate priority for conflict resolution.</li> +<li>The <xsl:namespace-alias... does not output the correct prefix.<br/><br/></li> +<li>Some required CDATA markers are not being output.<br/><br/></li> </ul> <p>The Apache XML Bug Tracking System is currently not working. If you find a bug, please report it (with "Xalan-J 2 bug" in the subject line) to the <human-resource-ref idref="xalandev"/>. We strongly encourage you write patches for problems you find and submit them to <human-resource-ref idref="xalandev"/>. We review the patches we receive to make sure they do not break something else, and (assuming they do not) include them in our next release. In the interest of fixing bugs, adding enhancements, and addressing outstanding design issues, we sincerely want (and need!) your active participation in the ongoing development of Xalan.</p> </s3> 1.6 +3 -2 xml-xalan/java/xdocs/sources/xalan/DONE Index: DONE =================================================================== RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/DONE,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- DONE 2000/12/18 17:33:54 1.5 +++ DONE 2000/12/18 22:24:47 1.6 @@ -1,6 +1,7 @@ <s3 title="Changes since &xslt4j; version 2.0.D01"> -<p>For a list of completed to-do tasks, see <jump href="todo.html#release-date-completed">Tasks completed</jump>. The remainder of this -section discusses two changes that are especially visible:</p> +<p>Most of the bugs reported in &xslt4j; 2.0.D01 have been fixed. For a list of outstanding bugs, see <link anchor="bugs">Open Bugs</link>.</p> +<p>For a list of completed to-do tasks, see <jump href="todo.html#release-date-completed">Tasks completed</jump>.</p> +<p>The remainder of this section discusses two changes that are especially visible:</p> <p><em>TrAX</em></p> <p>The Transformation API for XML (TrAX) that &xslt4j2; implements has undergone substantial revisions since the release of &xslt4j; 2.0.D01. TrAX has joined the Java API for XML Parsing (JAXP) as part of the Sun® <resource-ref idref="jsr063"/>. Accordingly, the TrAX package names have changed. The conceptual organization has also changed somewhat: The primary transformation interfaces are defined in javax.xml.transform, with concrete classes for managing stream input/output, SAX parsers and ContentHandler, and DOM parsers and DOM trees in javax.xml.transform.stream, javax.xml.transform.sax, and javax.xml.transform.dom. For more information, see <resource-ref idref="trax"/>, and review <link idref="usagepatterns">Usage Patterns</link>.</p> <p><em>Output properties</em></p>
