dleslie 01/01/02 13:51:47
Modified: java/xdocs/sources/xalan DONE index.xml readme.xml
Added: java/xdocs/sources/xalan history.xml
Log:
Updates for Xalan-J 2.0.D06.
Revision Changes Path
1.10 +19 -35 xml-xalan/java/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/DONE,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- DONE 2000/12/21 17:01:45 1.9
+++ DONE 2001/01/02 21:51:44 1.10
@@ -1,36 +1,20 @@
-<s3 title="Changes since &xslt4j; version 2.0.D01">
-<p>All of the bugs reported in &xslt4j; 2.0.D01 have been fixed. For a list
of tasks in the &xslt4j2; To-Do list that have been completed, see <jump
href="todo.html#release-date-completed">Tasks completed</jump>.</p>
-<p>The remainder of this section discusses two changes that we believe are
of particular importance:</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>
-<anchor name="outputprops"/><p><em>Output properties</em></p>
-<p>The handling of xsl:output properties has changed:
org.apache.xalan.serialize.OutputFormat and
apache.xalan.templates.OutputFormatExtended were removed and replaced with
org.apache.xalan.templates.OutputProperties. The SerializerFactory
getSerializer() method now takes Properties rather than a String indicating the
output method. You can replace <code>getSerializer("xml")</code>, for example,
with
<code>getSerializer(OutputProperties.getDefaultMethodProperties("xml"))</code>.</p>
-<p>HTML, XML, and text xsl:output properties are specified in property files
in org.apache.xalan.templates: output_html.properties, output_xml.properties,
and output_text.properties.</p>
-<p>You can start using the output properties defined in these files in your
stylesheets. For example, you can turn URL escaping off in HTML output
with<br/><code>{http\u003a//xml.apache.org/xslt}use-url-escaping=no</code><br/>
-and you can control indenting with<br/>
-<code>{http\u003a//xml.apache.org/xslt}indent-amount=<ref>n</ref></code></p>
-<note>The colon after the "http" protocol must be escaped.</note>
-<p>Character-to-entity mapping is specified in org.apache.xalan.serialize:
HTMLEntities.res and XMLEntities.res. You can override entity ref
-mapping from a stylesheet. For example:</p>
-<source><?xml version="1.0"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
- xmlns:xalan="http://xml.apache.org/xslt"; version="1.0">
-
- <xsl:output xalan:entities="myentities.ent"/>
-
- <xsl:template match="/">
- <out>&#125;</out>
- </xsl:template>
-
-</xsl:stylesheet></source>
-<p>=== myentities.ent ===</p>
-<source>quot 34
-amp 38
-lt 60
-gt 62
-lala 125</source>
-<p>The output is:</p>
-<source><?xml version="1.0" encoding="UTF-8"?>
-<out>&lala;</out></source>
-<p>See also <link idref="usagepatterns" anchor="outputprops">Setting output
properties in your stylesheets</link>.</p>
+<s3 title="Changes since &xslt4j; version 2.0.D05">
+<p>We have fixed he two bugs reported in &xslt4j; 2.0.D05. Along with
several other enhancements,
+we have also fixed a number of bugs found by our users:</p>
+<ul>
+<li>Fixed some threading problems and improved support for handling
Exceptions thrown in a secondary thread. To support incremental output,
+&xslt4j; performs the transformation in a second thread while building the
source tree in the main thread.<br/><br/></li>
+<li>Fixed problems utilizing transformation output as input for another
transformation.<br/><br/></li>
+<li><br/><br/></li>
+<li><br/><br/></li>
+<li>Fixed problems handling attributes and adding attributes to result
tree.<br/><br/></li>
+<li>Added defensive checking for null entities and namespaces.<br/><br/></li>
+<li>Adhere to SAX convention of representing null namespaces with empty
strings.<br/><br/></li>
+<li>Improved support for pruning source tree nodes when not
required.<br/><br/></li>
+<li>Fixed a bug evaluating a variable in a predicate expression applied to
child nodes.<br/><br/></li>
+<li>Changed names of serializers from FormatterTo<ref>Xxx</ref> to
SerializerTo<ref>Xxx</ref>. See
+<jump href="apidocs/org/apache/xalan/serialize/package-summary.html">Package
org.apache.xalan.serialize</jump>.<br/><br/></li>
+<li>Improved debugging support in a number of areas.</li>
+</ul>
+<p>For a list of tasks in the &xslt4j2; To-Do list that have been completed,
see <jump href="todo.html#release-date-completed">Tasks completed</jump>.</p>
</s3>
1.12 +2 -4 xml-xalan/java/xdocs/sources/xalan/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/index.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- index.xml 2000/12/19 16:02:38 1.11
+++ index.xml 2001/01/02 21:51:45 1.12
@@ -71,10 +71,8 @@
</s2>
<s2 title="How about this release?">
<p>&xslt4j-current; is a beta Developer's release of &xslt4j2;. It
represents a stable build that conforms to the XSLT
- and XPath 1.0 specifications.</p>
- <p>Since &xslt4j; 2.0.D01, TrAX has been revised and integrated with the
XMP Parser API in the Java API for XML Processing,
- so &xslt4j; has been revised accordingly. This release also includes
greatly expanded support for custom stylesheet control
- over output properties. For the details, see the <link
idref="readme">Release notes</link>. Please send your comments, bug reports,
+ and XPath 1.0 specifications, and it includes some enhaqncements along
with fixes for the bugs we and our users have found
+ in &xslt4j; 2.0.D05. For the details, see the <link
idref="readme">Release notes</link>. Please send your comments, bug reports,
and feedback to the <human-resource-ref idref="xalandev"/>.</p>
</s2>
<s2 title="How do I get it?">
1.18 +9 -7 xml-xalan/java/xdocs/sources/xalan/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/readme.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- readme.xml 2000/12/21 17:25:08 1.17
+++ readme.xml 2001/01/02 21:51:45 1.18
@@ -3,7 +3,7 @@
<!ENTITY done-j SYSTEM "DONE">
<!ENTITY status-j SYSTEM "STATUS">
<!ENTITY bugs-j SYSTEM "BUGS">
-<!ENTITY bugs-open SYSTEM "bugs.out">]>
+<!ENTITY history-j SYSTEM "history.xml">]>
<!--
* The Apache Software License, Version 1.1
@@ -67,11 +67,11 @@
<li><link anchor="status">Status</link></li>
<li><link anchor="build">Build Notes</link></li>
<li><link anchor="contact">Getting in touch</link></li>
- <!--li><link anchor="history">History of software changes</link></li-->
+ <li><link anchor="history">History of software changes</link></li>
</ul>
<s2 title="Status">
<ul>
- <li><link anchor="done">Changes since version 2.0.D01</link></li>
+ <li><link anchor="done">Changes since version 2.0.D05</link></li>
<li><link anchor="other">Other points of interest</link></li>
<li><link anchor="bugs">Open bugs and bug reporting</link></li>
<li><link anchor="status">Version of Xerces to use</link></li>
@@ -105,7 +105,8 @@
</ul>
</s3><anchor name="bugs"/>
<s3 title="Open bugs and bug reporting">
- &bugs-j;
+ <!--&bugs-j;-->
+ <p>Currently, there are no open bugs in &xslt4j;.</p>
<p>Xerces bug in &xml4j-used;:</p>
<ul>
<li>&xml4j; 1.2.3 does not process namespaces in SAX events when
parsing UTF-16 documents, which causes &xslt4j; to fail with UTF-16
@@ -269,8 +270,9 @@
<s2 title="Getting in Touch">
<p>Your feedback is more than welcome. Offers of help are even more so!
Perhaps you would like to take on an active role in the ongoing development,
testing, and documentation of &xslt4j;?</p>
<p>Please email your comments, questions, suggestions, and offers to join
the Xalan team to <human-resource-ref idref="xalandev"/>.</p>
- </s2><!--anchor name="history"/>
+ </s2><anchor name="history"/>
<s2 title="Cumulative history of software changes">
- <note>We started tracking the changes in earlier releases beginning with
&xslt4j; version 1.1.</note>
- </s2-->
+ <p>The following sections list the changes in each release since &xslt4j;
version 2.0.D01.</p>
+ &history-j;
+ </s2>
</s1>
1.1 xml-xalan/java/xdocs/sources/xalan/history.xml
Index: history.xml
===================================================================
<s3 title="Changes for &xslt4j; version 2.0.D05">
<p>All of the bugs reported in &xslt4j; 2.0.D01 have been fixed. The
remainder of this section discusses two changes that we believe are of
particular importance:</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>
<anchor name="outputprops"/><p><em>Output properties</em></p>
<p>The handling of xsl:output properties has changed:
org.apache.xalan.serialize.OutputFormat and
apache.xalan.templates.OutputFormatExtended were removed and replaced with
org.apache.xalan.templates.OutputProperties. The SerializerFactory
getSerializer() method now takes Properties rather than a String indicating the
output method. You can replace <code>getSerializer("xml")</code>, for example,
with
<code>getSerializer(OutputProperties.getDefaultMethodProperties("xml"))</code>.</p>
<p>HTML, XML, and text xsl:output properties are specified in property files
in org.apache.xalan.templates: output_html.properties, output_xml.properties,
and output_text.properties.</p>
<p>You can start using the output properties defined in these files in your
stylesheets. For example, you can turn URL escaping off in HTML output
with<br/><code>{http\u003a//xml.apache.org/xslt}use-url-escaping=no</code><br/>
and you can control indenting with<br/>
<code>{http\u003a//xml.apache.org/xslt}indent-amount=<ref>n</ref></code></p>
<note>The colon after the "http" protocol must be escaped.</note>
<p>Character-to-entity mapping is specified in org.apache.xalan.serialize:
HTMLEntities.res and XMLEntities.res. You can override entity ref
mapping from a stylesheet. For example:</p>
<source><?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
xmlns:xalan="http://xml.apache.org/xslt"; version="1.0">
<xsl:output xalan:entities="myentities.ent"/>
<xsl:template match="/">
<out>&#125;</out>
</xsl:template>
</xsl:stylesheet></source>
<p>=== myentities.ent ===</p>
<source>quot 34
amp 38
lt 60
gt 62
lala 125</source>
<p>The output is:</p>
<source><?xml version="1.0" encoding="UTF-8"?>
<out>&lala;</out></source>
<p>See also <link idref="usagepatterns" anchor="outputprops">Setting output
properties in your stylesheets</link>.</p>
</s3>
