dleslie 00/07/21 10:39:27
Modified: xdocs/sources/xalan BUGS DONE STATUS index.xml
Log:
For version 1.2.D01
Revision Changes Path
1.8 +6 -6 xml-xalan/xdocs/sources/xalan/BUGS
Index: BUGS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/BUGS,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- BUGS 2000/06/23 21:39:10 1.7
+++ BUGS 2000/07/21 17:39:26 1.8
@@ -1,22 +1,22 @@
<s3 title="Open bugs and bug reporting">
<p>Open bugs:</p>
<ul>
- <li>Complex XPath expressions including steps after a union raise an
unknown access error and do not return the correct
- node-set.</li>
- <li>Text nodes with entity references are not handled correctly by the
Document Table Model (<link idref="dtm">DTM</link>). An entity reference in a
text node causes the node to be split at that entity. A problem was also
reported with the contains() function; contains(String, entity) was returning
false when it should return true. <em>Workaround:</em> instantiate the
XSLTProcessor as follows so it uses the <resource-ref
idref="XercesLiaisonDoc"/> and the Xerces DOM parser:<br/>
+<li>Text nodes with entity references are not handled correctly by the
Document Table Model (<link idref="dtm">DTM</link>). An entity reference in a
text node causes the node to be split at that entity. A problem was also
reported with the contains() function; contains(String, entity) was returning
false when it should return true. <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><br/>
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>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 explicilty 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>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>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>
<li>The id() function doesn't work in some complex match
patterns.<br/><br/></li>
<li>If you specify HTML output and encoding via xsl:output, and if a
<HEAD> element is generated, then the encoding should be represented in a
<META> tag inside the <HEAD> element. We do not put out the META
tag nor any representation of the encoding in this case.<br/><br/></li>
<li>If you are generating processing instructions (PIs) in XML output, and
you attempt to insert a literal "?>" in it, the spec says that "? >" should be
generated, inserting a space to prevent interpretation as the end of the PI. We
do not take this special step, so "?>" is generated.<br/><br/></li>
-<li>When outputting URI attributes in HTML, almost all "control" characters
below decimal 32 will cause an error to be raised, rather than silently being
discarded. Most characters above decimal 127 will be output as that character.
Percent should be output as %25 at all times (it is currently output as a
literal percent); this will be fixed later.</li>
+<li>When outputting URI attributes in HTML, almost all "control" characters
below decimal 32 will cause an error to be raised, rather than silently being
discarded. Most characters above decimal 127 will be output as that character.
Percent should be output as %25 at all times (it is currently output as a
literal percent); this will be fixed later.<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>Need to verify which HTML element attributes should be treated as
URIs.<br/><br/></li>
</ul>
<p>Bug reports that we have not yet confirmed:</p>
<ul>
1.18 +11 -5 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- DONE 2000/07/20 17:42:14 1.17
+++ DONE 2000/07/21 17:39:26 1.18
@@ -1,13 +1,19 @@
<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
fixsing 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>
+<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 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 submitted by Kent Tamura: Fixed SimpleNodeLocator.findNamespace()
so that the namespace axis includes all namespace nodes in scope in the context
node (including namespace declarations from ancestor nodes).<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 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 DTMLiaison.java submitted by Morgan Delagrange: dynamic
validation (validation of internal DOCTYPE declaration) is turned off by
default.<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 L. Peskin:
GetTypeString() method changed from private to protected, so that it returns an
appropriate message for each node type.<br/><br/></li>
-</ul>
+<li>Patch to SimpleNodeLocator.java submitted by Gary L. 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>
</s3>
1.13 +3 -3 xml-xalan/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/STATUS,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- STATUS 2000/07/20 17:42:14 1.12
+++ STATUS 2000/07/21 17:39:26 1.13
@@ -10,14 +10,14 @@
<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>Improvide performance and simplify optimization.</li>
- <li>Produce more localized, less-intertangled modules</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>
</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
the xml.apache projects, including Xalan, Xerces, Cocoon, and FOP.</p>
- <p>The more individuals who join in the design, development, testing,
documention, and use of
+ <p>The more individuals who join in the design, development, testing,
documentation, and use of
&xslt4j; the better for us all in the xml.apache.org open source
community! Watch the <human-resource-ref idref="xalandev"/>
for more information and for ideas about how you can get involved.</p>
</s3>
1.7 +2 -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.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- index.xml 2000/06/28 19:31:23 1.6
+++ index.xml 2000/07/21 17:39:27 1.7
@@ -66,7 +66,8 @@
<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>For the details about this release, see <link idref="readme">Release
Notes</link>.</p>
+ <p>This developer's release incorporates a number of patches submitted
to <human-resource-ref idref="xalandev"/>.
+ For the details, see <link idref="readme">Release Notes</link>.</p>
</s2>
<s2 title="How do I get it?">
