dleslie 00/08/22 12:42:43
Modified: xdocs/sources xalan.xml
xdocs/sources/design design2_0_0.xml
xdocs/sources/xalan BUGS DONE STATUS history.xml index.xml
readme.xml
Log:
Draft of updates for 1.2.D02
Revision Changes Path
1.12 +1 -1 xml-xalan/xdocs/sources/xalan.xml
Index: xalan.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- xalan.xml 2000/07/19 21:26:39 1.11
+++ xalan.xml 2000/08/22 19:42:27 1.12
@@ -67,7 +67,7 @@
<separator/>
<document id="index"
- label="Xalan-J 1.2.D01"
+ label="Xalan-J 1.2.D02"
source="xalan/index.xml"/>
<external href="getstarted.html#download" label="Downloads"/>
1.4 +1 -1 xml-xalan/xdocs/sources/design/design2_0_0.xml
Index: design2_0_0.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/design/design2_0_0.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- design2_0_0.xml 2000/07/28 16:21:09 1.3
+++ design2_0_0.xml 2000/08/22 19:42:30 1.4
@@ -68,7 +68,7 @@
<p>Xalan 2.0 is divided into four major modules, and various smaller
modules. The main modules are:</p>
<gloss>
- <label><code><jump
href="http://xml.apache.org/xalan-j/apidocs/org/apache/xalan/processor/package-summary.html";>org.apache.xalan.process</jump></code></label>
+ <label><code><jump
href="http://xml.apache.org/xalan-j/apidocs/org/apache/xalan/processor/package-summary.html";>org.apache.xalan.processor</jump></code></label>
<item>The module that processes the stylesheet, and provides
the main
entry point into Xalan.</item>
</gloss>
1.10 +0 -7 xml-xalan/xdocs/sources/xalan/BUGS
Index: BUGS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/BUGS,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- BUGS 2000/07/25 22:14:37 1.9
+++ BUGS 2000/08/22 19:42:33 1.10
@@ -1,12 +1,6 @@
<s3 title="Open bugs and bug reporting">
<p>Open bugs:</p>
<ul>
-<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>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>
@@ -19,7 +13,6 @@
<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.<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>
1.21 +11 -10 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- DONE 2000/07/25 22:14:36 1.20
+++ DONE 2000/08/22 19:42:33 1.21
@@ -1,14 +1,15 @@
<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>
+<p>For this release, we have applied several bug fixes, including patches
submitted by developers 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 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 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>
+<li>The Xalan DTM (Document Table Model) was splitting text nodes containing
entity references into multiple nodes. We have fixed this problem, and Xalan
now it produces a single text node for output.<br/><br/></li>
+<li>Norm Walsh submitted patches enabling Xalan to accept URI substitutions
set by a custom EntityResolver.<br/><br/></li>
+<li>Gary Peskin submitted a patch enabling Xalan to process expressions with
path steps following a union. As a result, Xalan can now transform documents of
the DocBook document type.<br/><br/></li>
+<li>We believe we have fixed encoding problems handling characters above 127
in URI attributes. We are still soliciting input on how to handle special URI
characters between 32 and 127.<br/><br/></li>
+<li>The use of position() in sort expressions now works as expected, which
makes it easy to reverse node order. When the primary sort fails completely, we
no longer fall through to a sort with the secondary key.<br/><br/></li>
+<li>Sergei Ivanov submitted a patch to avoid including a minus sign an ID in
the rare case when a negative number was appearing in the ID.<br/><br/></li>
+<li>We believe we have fixed XPath retrieval of attributes qualified with a
namespace prefix. Other namespace fixes enable the name() and namespace-uri()
functions to be applied to namespace nodes.<br/><br/></li>
+<li>Ed Staub submitted a patch so that a message about processing
instruction names now appears as a warning rather than an error.<br/><br/></li>
+<li>A thread-safety issue in pattern matching was identified and
fixed.<br/><br/></li>
+<li>The output of very small decimal fractions has been improved.</li>
</ul>
</s3>
1.16 +3 -3 xml-xalan/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/STATUS,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- STATUS 2000/07/26 13:01:10 1.15
+++ STATUS 2000/08/22 19:42:34 1.16
@@ -12,12 +12,12 @@
<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 <jump
href="http://trax.openxml.org/";>TRaX (Transformations for XML)</jump>
interfaces.</li>
+ <li>Begin the adoption of the <jump
href="http://trax.openxml.org/";>TRaX (Transformations for XML)</jump>
interfaces</li>
+ <li>Take advantage of the <jump
href="http://www.megginson.com/SAX/Java/index.html";>SAX 2</jump> and <jump
href="http://www.w3.org/TR/DOM-Level-2/";>DOM level 2</jump> packages</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,
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>
+ &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.2 +14 -0 xml-xalan/xdocs/sources/xalan/history.xml
Index: history.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/history.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- history.xml 2000/07/20 17:42:55 1.1
+++ history.xml 2000/08/22 19:42:34 1.2
@@ -1,3 +1,17 @@
+<s3 title="Changes for &xslt4j; version 1.2.D01">
+<p>We applied patches submitted by a number of developers to
<human-resource-ref idref="xalandev"/>.</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 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 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>
<s3 title="Changes for &xslt4j; version 1.1">
<ul>
<li><link anchor="synch">Updates to stay in synch with &xml4j;</link></li>
1.8 +3 -8 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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- index.xml 2000/07/21 17:39:27 1.7
+++ index.xml 2000/08/22 19:42:35 1.8
@@ -60,14 +60,9 @@
<s1 title="&xslt4j-current;">
<s2 title="What is it?">
- <p>Xalan is an XSLT processor for transforming XML documents into HTML,
text, or other XML document types. &xslt4j-current;
- represents a complete and robust reference implementation of the W3C
Recommendations for XSL Transformations
- (XSLT) and the XML Path Language (XPath).</p>
- <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>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>
+ <p>Xalan is an XSLT processor for transforming XML documents into HTML,
text, or other XML document types. &xslt4j-current; represents a complete and
robust reference implementation of the W3C Recommendations for XSL
Transformations (XSLT) and the XML Path Language (XPath).</p>
+ <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>This developer's release incorporates a number of bug fixes,
including patches submitted to <human-resource-ref idref="xalandev"/>. One of
these patches fixes a problem that &xslt4j; was having processing documents of
the DocBook document type. For the details, see <link idref="readme">Release
Notes</link>.</p>
</s2>
<s2 title="How do I get it?">
1.17 +1 -1 xml-xalan/xdocs/sources/xalan/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/readme.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- readme.xml 2000/07/20 17:42:14 1.16
+++ readme.xml 2000/08/22 19:42:35 1.17
@@ -71,7 +71,7 @@
</ul>
<s2 title="Status">
<ul>
- <li><link anchor="done">Changes since version 1.0.1</link></li>
+ <li><link anchor="done">Changes since version 1.2.D01</link></li>
<li><link anchor="bugs">Open bugs and bug reporting</link></li>
<li><link anchor="status">Version of Xerces to use</link></li>
<li><link anchor="to-do">To-do tasks for future &xslt4j;
releases</link></li>
