curcuru 00/07/25 15:14:38
Modified: xdocs/sources/xalan STATUS DONE BUGS
Log:
Last minute updates for upcoming 1.2D01 build (which patch is which)
Revision Changes Path
1.14 +3 -3 xml-xalan/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/STATUS,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- STATUS 2000/07/21 17:39:26 1.13
+++ STATUS 2000/07/25 22:14:36 1.14
@@ -10,9 +10,9 @@
<li>Provide ease of access and usability of &xslt4j;, and
encourage greater participation from the open source community
in the ongoing design and development process</li>
<li>Reduce code size and complexity</li>
- <li>Improve performance and simplify optimization.</li>
- <li>Produce more localized, less intertangled modules</li>
- <li>Begin the adoption of the TRaX (Transformations for XML)
interfaces.</li>
+ <li>Improvide performance and simplify optimization.</li>
+ <li>Produce more localized, less-intertangled modules</li>
+ <li>Begin the adoption of the <jump
href="http://trax.openxml.org/";>TRaX (Transformations for XML)</jump>
interfaces.</li>
</ol>
<p>For an overview of the 2.0 design, see <jump
href="http://xml.apache.org/xalan/design/design1_1_0.html";>Xalan-J 2.0
Design</jump>. The source tree (still pre-alpha) is in the <jump
href="http://xml.apache.org/websrc/cvsweb.cgi/xml-xalan/java/src/";>Apache CVS
Repository: xml-xalan/java/src</jump>. Pre-alpha Xalan-J 2.0 <jump
href="http://xml.apache.org/xalan-j/apidocs/index.html";>Javadoc</jump> is also
periodically updated on the xml.apache.org Website.</p>
<p>As part of the xml.apache team, members of the &xslt4j; team are also
exploring options to upgrade the integration of all
1.20 +7 -12 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- DONE 2000/07/21 18:17:08 1.19
+++ DONE 2000/07/25 22:14:36 1.20
@@ -1,19 +1,14 @@
<s3 title="Changes since &xslt4j; version 1.1">
<p>For this release, we have applied patches that a number of developers
have submitted 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>Patch submitted by Sergei Ivanov: Fixed XNumber.java so that the string
function does not apply the current locale setting when formatting numbers. In
other words, the locale setting will not override the format applied in the
string function.<br/><br/></li>
-<li>Patch to FormatterToDOM.java and StylesheetRoot.java submitted by Bernd
Köcke: Enables transformation of a DOM beginning with an Element-Node or
DocumentFragment-Node.<br/><br/></li>
+<li>Patch submitted by Sergei S. Ivanov: Fixed XNumber.java so that the
string function does not apply the current locale setting when formatting
numbers. In other words, the locale setting will not override the format
applied in the string function.<br/><br/></li>
+<li>Patch submitted by Bernd Köcke: Fixed FormatterToDOM.java and
StylesheetRoot.java so can transform a DOM beginning with an Element-node or
DocumentFragment-Node.<br/><br/></li>
+<li>Patch to SimpleNodeLocator.java submitted by Gary Peskin: Fixes the
problem with complex XPath expressions including steps after a union that were
raising an access error and not returning the correct node-set.<br/><br/></li>
<li>Patch to XMLParserLiaisonDefault.java submitted by Bernd Köcke:
Changed ProblemListener variable to non-static, so users working in a
multithreaded environment can can log errors from multiple
ProblemListeners.<br/><br/></li>
<li>Patch to FuncFormatNumb submitted by Dimitry Voytenko: Supplied missing
curly braces in an else clause.<br/><br/></li>
<li>Patch to XPath.java submitted by Naohiko Uramoto: Increased
MAXTOKENQUEUSIZE from 500 to 2000 to support longer XPath
expressions.<br/><br/></li>
-<li>Patches to XObject.java, XBoolean.java, XNodeSet.java, XNull.java,
XNumber.java, XtreeFrag.java, and XString.java submitted by Gary Peskin:
GetTypeString() method changed from private to protected, so that it returns an
appropriate message for each node type.<br/><br/></li>
-<li>Patch to SimpleNodeLocator.java submitted by Gary Peskin: Fixes the
problem with complex XPath expressions including steps after a union that were
raising an access error and not returning the correct node-set.<br/><br/></li>
-</ul>
-<p>A couple of other patches are still under investigation.</p>
-<ul>
-<li>Patch to DTMLiaison.java submitted by Morgan Delagrange: This patch
turns off dynamic validation (validation of internal DOCTYPE declaration).
<br/>Problem with the patch: The Xerces parser does not process ID declarations
if validation is not run. We have raised this issue with the Xerces-J team.
Note that if dynamic validation is turned on (as is currently the case)
processing does occur -- at least with the command-line utility -- even if the
processor reports validation errors. Perhaps someone could provide a temporary
workaround patch that provides an API for turning off dynamic validation, with
the warning that this disables use of the id() function.<br/><br/></li>
-<li>Patch to SimpleNodeLocator.java submitted by Kent Tamura: This patch
uses a new internal AttrProxy class to ensure that the findNamespace() method
returns all namespace nodes in scope for the context node, including namespace
declarations from ancestor nodes. <br/>Problems with the patch:
-(1)This patch works for the Xerces DOM parser, but not the high-performance
DTM liaison; (2) Multiple invocations do not return the same node objects,
which is a problem for creating unique IDs. We can modify the patch so that it
also works with DTM. The other problem requires more
investigation.<br/><br/></li>
-</ul>
-<p>We have not included other patches that we consider too risky or that we
think should be addressed in the scope of &xslt4j; version 2.0.</p>
+<li>Patches to XObject.java, XBoolean.java, XNodeSet.java, XNull.java,
XNumber.java, XtreeFrag.java, and XString.java submitted by Gary L. Peskin:
GetTypeString() method changed from private to protected, so that it returns an
appropriate message for each node type.<br/><br/></li>
+<li>Some updates to XNumber to attempt to address formatting issues with
jview.<br/><br/></li>
+<li>We have not included other patches that we consider too risky or that we
think should be addressed in the scope of Xalan-Java version 2.0.<br/><br/></li>
+</ul>
</s3>
1.9 +5 -0 xml-xalan/xdocs/sources/xalan/BUGS
Index: BUGS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/BUGS,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- BUGS 2000/07/21 17:39:26 1.8
+++ BUGS 2000/07/25 22:14:37 1.9
@@ -7,6 +7,11 @@
If you are running org.apache.xalan.xslt.Process from the command line,
include<br/>
<code>-parser org.apache.xalan.xpath.xdom.XercesLiaison</code><br/>
on the command line.<br/><br/></li>
+<li>When format-number() should format NaN or infinity, it generates the
wrong string if default strings are used. Workaround: declare the strings in an
xsl:decimal-format instruction at the top of the stylesheet.<br/><br/></li>
+<li>A "not serializable exception" occurs when you attempt to run a
precompiled stylesheet that expects parameter values to be passed in. If you
encounter this problem, you should forego the use of precompiled stylesheets
until a fix is available.<br/><br/></li>
+<li>The namespace::* axis only selects namespaces that were declared locally
on the context node. Inherited namespaces are in effect; the only known flaw is
the lack of their presence on this rarely-used axis. The name() function, when
applied to a namespace node, returns a string that disagrees with other
processors, and the XPath spec is vague on this point.<br/><br/></li>
+<li>UTF-8 output is improperly escaped in the 128-255 range.<br/><br/></li>
+<li>In a multithreaded environment, some threads may lose track of xsl:key
elements.<br/><br/></li>
<li>UTF-16 output encoding is not yet supported. Under Sun's JDK 1.2.2, a
suitable message is issued, but a stack dump occurs under JDK 1.1.8 due to
differences in ByteToCharConverter.<br/><br/></li>
<li>Implied HTML output (the output begins with <HTML>, but the output
method has not been explicitly set to HTML) is not thread-safe, due to a "late"
change of output method. <em>Workaround:</em> put an explicit <xsl:output
method="html".../> declaration in the stylesheet.<br/><br/></li>
<li>In some cases, exclude-result-prefixes takes effect even when the
specified prefix appears in sub-elements, causing output of unresolved
prefixes. If you experience this, please adjust your exclude-result-prefixes
attribute.<br/><br/></li>
