dleslie 00/07/20 10:42:16
Modified: xdocs/sources/xalan DONE STATUS readme.xml
Log:
1st drafts (not complete) for version 1.2.D01
Revision Changes Path
1.17 +11 -66 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- DONE 2000/06/29 12:47:44 1.16
+++ DONE 2000/07/20 17:42:14 1.17
@@ -1,68 +1,13 @@
-<s3 title="Changes since &xslt4j; version 1.0.1">
+<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>
<ul>
-<li><link anchor="synch">Updates to stay in synch with &xml4j;</link></li>
-<li><link anchor="bugfixes">Bug fixes</link></li>
-<li><link anchor="uriattrib">URI attributes in HTML output</link></li>
-<li><link anchor="ant0">Ant</link></li>
-</ul>
-<anchor name="synch"/><s4 title="Updates to stay in synch with &xml4j;">
-<p>&xml4j; version 1.0.4 introduced some API changes that caused problems
for &xslt4j; version 1.0.1. The two teams collaborated to bring Xalan-Java and
Xerces-Java back into synch with &xslt4j; version 1.1.D01 (a Developer's
release) and &xml4j; version 1.1.1.</p>
-<p>&xml4j-used; replaced java.net.URL with a new URI class to resolve system
IDs for external entities. As a result, &xml4j; no longer accepts OS file path
names for URIs. If, for example you used "c:\foo\bar.xml" to designate a URI in
an earlier release of &xml4j;, you must now use "file:///c:/foo/bar.xml".</p>
-<p>We have updated the command-line utility (org.apache.xalan.xslt.Process)
so that it will continue to accept file path names.</p>
-<p>When you use the API to instantiate an XSLTInputSource object, you must
use the correct String designation for the URI. For example:<br/><br/>
-<code>XSLTInputSource =</code><br/>
-<code> new
XSLTInputSource("file:///c:/foo/bar.xml");</code></p>
-<p>If you really want you use a file name, you must do something along the
lines of the following code fragment:</p>
-<source>
-import java.net.URL;
-import org.apache.xalan.xslt.*;
-...
-// Must escape "\" character.
-String fileName="c:\\foo\\bar.xml";
-
-// Create a URL object and use it to generate
-// a string in the correct URI format.
-URL url = new URL(fileName);
-String urlIn = url.toExternalForm();
-
-// Now have the correct string for an XSLTInputSource object.
-XSLTInputSource = new XSLTInputSource(urlIn);
-...</source>
-<note>This change has no effect on the creation of an XSLTOutput object. You
can still use a file name. You may also continue to use a file name with the
XSLTProcessor setStylesheet() method.</note>
-
-</s4><anchor name="bugfixes"/><s4 title="Bug fixes">
-<p>We have also addressed several bugs found in &xslt4j; version 1.0.1:</p>
- <ul>
-<li>A function or variable reference on the left-hand-side of a union was
sometimes incorrectly evaluated. This has been fixed. The fix, however,
introduces a new bug that we have not yet fixed: complex XPath expressions
including steps after a union raise an unknown access error and do not return
the correct node-set.<br/><br/></li>
-<li>Numbered entity references were sometimes output in hexadecimal, not
decimal. Numbered entity references are now always output in
decimal.<br/><br/></li>
-<li>&xslt4j; was not using the xsl:output standalone attribute to place
document standalone declarations in the output. If the standalone attribute is
set to "yes", &xslt4j; now includes a standalone document declaration in the
output. If the standalone attribute is set to "no", &xslt4j; does not place a
standalone document declaration in the output.<br/><br/></li>
-<li>xsl:key declarations in imported stylesheets did not work. This has been
fixed.<br/><br/></li>
-<li>When the key() function encountered an attribute set to a null string,
key() ignored all subsequent nodes. This has been fixed. <br/><br/></li>
-<li>The local-name function now returns the correct string for text and
comment nodes.<br/><br/></li>
-<li>We fixed a namespace resolution problem in the XPathAPI eval() method.
XPathAPI provides an API for executing XPath expressions and is included with
the ApplyXPath sample application.</li>
-</ul>
-</s4><anchor name="uriattrib"/><s4 title="URI attributes in HTML output">
-<p>In response to requests, we have added a boolean SpecialEscapeURLs
property to FormatterToHTML and changed the way we output certain characters in
URI attributes (such as HREF) when the output method is HTML.</p>
-<p><em>What we did in version 1.0.1:</em> Non-ASCII characters, space, and
double quote("), were output as <code>%hh</code>, where <code>hh</code> is the
hex value of the character. Ampersand (&) was output literally.</p>
-<p><em>What we do by default in version 1.1 (the SpecialEscapeURLs is set to
false):</em> Non-ASCII characters are output as <code>&#nnn</code>, where
<code>nnn</code> is the decimal value of the character, and HTML special
characters are output as <code>&xyz;</code>, where <code>xyz</code> is the
named entity for this character (such as &quot; for "). Space is
output as a literal space.</p>
-<p><em>What we do in version 1.1 if you set the FormatterToHTML
SpecialEscapeURLs property to true:</em> Non-ASCII characters and space are
output as <code>%hh</code>, where <code>hh</code>is the hex value of the
character, and double quote is output as <code>&quot;</code> (instead of
<code>%22</code>). Ampersand is output as a literal ampersand.</p>
-<p>Given our reading of the XSLT and HTML specs, we are not sure this is
appropriate output to support, so we are soliciting feedback from the XSL
community.</p>
-<p>Here is code fragment indicating one technique for setting
SpecialEscapeURLs to true.</p>
-
-<source>// Manually set up a FormatterToHTML
-OutputFormat format = new OutputFormat( "html", "UTF-8", false );
-org.apache.xalan.xpath.xml.FormatterToHTML formatter =
- new FormatterToHTML();
-formatter.init(writer, format);
-
-// New! Turn on the new special HTML URL attr escaping
-formatter.setSpecialEscapeURLs(true);
-
-// Perform the process, using the Formatter as a target
-processor.process(new XSLTInputSource(xmlName),
- new XSLTInputSource(xslName),
- new XSLTResultTarget(formatter));</source>
-</s4><anchor name="ant0"/><s4 title="Ant">
-<p>We have upgraded support for using Apache Ant to build &xslt4j;. For the
details, see <link anchor="ant">Using Ant</link>.</p>
-</s4>
+<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 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>
</s3>
1.12 +3 -2 xml-xalan/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/STATUS,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- STATUS 2000/06/23 13:03:54 1.11
+++ STATUS 2000/07/20 17:42:14 1.12
@@ -2,18 +2,19 @@
<p>The &xslt4j-current; has been tested with &xml4j-used;. &download; For
information about including xerces.jar on the system class path, see <link
idref="getstarted" anchor="classpath">Setting up the system class
path</link>.</p>
<p><em>Important</em> You may experience unpredictable anomalies if your
Xalan and Xerces builds are not in synch. If you download an update to Xalan,
check the release notes to determine which version of Xerces you should use.</p>
<note>You can use Xalan with other XML parsers, but it is up to you to
implement liaisons to those parsers. Your liaison class should extend
<resource-ref idref="XMLParserLiaisonDefaultDoc"/> and implement <resource-ref
idref="XMLParserLiaisonDoc"/>.</note>
-</s3>
+</s3><anchor name="to-do"/>
<s3 title="To-do tasks for future &xslt4j; releases">
<p>The &xslt4j; team is hard at work on &xslt4j; version 2.0, which
represents a major redesign of the Xalan XSLT Processor.
The main goals of this redesign are as follows:</p>
<ol>
- <li>Improvide ease of access and usability of &xslt4j;, and
encourage greater participation from the open source community
+ <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>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
1.16 +11 -2 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.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- readme.xml 2000/06/29 12:47:44 1.15
+++ readme.xml 2000/07/20 17:42:14 1.16
@@ -2,7 +2,8 @@
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd"[
<!ENTITY done-j SYSTEM "DONE">
<!ENTITY status-j SYSTEM "STATUS">
-<!ENTITY bugs-j SYSTEM "BUGS">]>
+<!ENTITY bugs-j SYSTEM "BUGS">
+<!ENTITY history-j SYSTEM "history.xml">]>
<!--
* The Apache Software License, Version 1.1
@@ -61,16 +62,19 @@
* <http://www.apache.org/>.
-->
<s1 title="Release Notes">
+<p>&xslt4j-current;</p>
<ul>
<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>
</ul>
<s2 title="Status">
<ul>
<li><link anchor="done">Changes since version 1.0.1</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="status">Version of Xerces to use</link></li>
+ <li><link anchor="to-do">To-do tasks for future &xslt4j;
releases</link></li>
</ul>
<anchor name="done"/>
&done-j;
@@ -80,6 +84,7 @@
&status-j;
</s2>
<anchor name="build"/>
+
<s2 title="Build Notes">
<ul>
<li><link anchor="ant">Using Ant</link></li>
@@ -214,5 +219,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 title="Cumulative history of software changes">
+ <note>We started tracking the changes in earlier releases beginning with
&xslt4j; version 1.1.</note>
+ &history-j;
</s2>
</s1>
