You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by dl...@locus.apache.org on 2000/06/23 23:39:16 UTC
cvs commit: xml-xalan/xdocs/sources/xalan BUGS DONE index.xml readme.xml
dleslie 00/06/23 14:39:15
Modified: xdocs/sources xalan.xml
xdocs/sources/xalan BUGS DONE index.xml readme.xml
Log:
updates for 1.1.D01.
Revision Changes Path
1.9 +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.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- xalan.xml 2000/06/22 17:01:47 1.8
+++ xalan.xml 2000/06/23 21:39:07 1.9
@@ -67,7 +67,7 @@
<separator/>
<document id="index"
- label="Xalan-Java 1.1.D01"
+ label="Xalan-J 1.1.D01"
source="xalan/index.xml"/>
<external href="getstarted.html#download" label="Downloads"/>
1.7 +28 -2 xml-xalan/xdocs/sources/xalan/BUGS
Index: BUGS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/BUGS,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- BUGS 2000/05/31 15:57:45 1.6
+++ BUGS 2000/06/23 21:39:10 1.7
@@ -1,6 +1,32 @@
-<s3 title="Bug reporting">
+<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/>
+<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>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>
+</ul>
+<p>Bug reports that we have not yet confirmed:</p>
+<ul>
+<li>We have a report that passing a long string value (somewhere over 128 characters) to a template via with-param caused an overflow problem under Solaris with a Sun JDK. We have not seen the problem under Sun's JDKs (1.1.8 and 1.2.2) on Win32. Additional reports are welcome.<br/><br/></li>
+<li>We have a report that external entities can affect xsl:copy in a DOM input scenario. An external entity that had no attributes was causing improper copying, and adding an attribute fixed the problem. To date we have been unable to create the bug situation in our lab.<br/><br/></li>
+</ul>
<p>Outstanding bugs are recorded in the Apache XML <jump href="http://xml.apache.org/bugs/">Bug Tracking System</jump>.
If you find a bug, please use this system to report it.</p>
<note>If the Apache XML Bug Tracking System is not working, please report the bug to the
<human-resource-ref idref="xalandev"/>.</note>
-</s3>
+</s3>
+
+
1.14 +28 -9 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- DONE 2000/06/23 13:03:54 1.13
+++ DONE 2000/06/23 21:39:10 1.14
@@ -2,16 +2,35 @@
<p>&xml4j; version 1.0.4 introduced some API changes that caused problems for &xslt4j; version 1.0.1. The two teams have collaborated to bring Xalan-Java and Xerces-Java back into synch with &xslt4j-current; and &xml4j-used;.</p>
<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.<br/><br/></li>
+<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 yet place a standalone document declaration in the output; this will be fixed soon.<br/><br/></li>
-<li>Text nodes with entity references are not handled correctly by the Document Table Model (<link idref="dtm">DTM</link>). We have not yet fixed this bug.<br/><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/><br/></li>
-<li>xsl:key declarations in imported stylesheets do not work. We have not yet fixed this bug.<br/><em>Workaround:</em>
-place all xsl:key declarations in the top-level stylsheet, even if used in the imported stylesheets.<br/><br/></li>
-<li>When key() function encountered an attribute set to a null string, keyt() ignored all subsequent nodes(). This has been fixed. <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.<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>
+<p><em>Ant</em></p>
<p>We have upgraded support for using Apache Ant to build &xslt4j;. For the details, see <link anchor="ant">Using Ant</link>.</p>
+<p><em>URI attributes in HTML output</em></p>
+<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.0D01 (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.D01 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>
</s3>
1.5 +5 -5 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.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- index.xml 2000/06/22 17:01:58 1.4
+++ index.xml 2000/06/23 21:39:10 1.5
@@ -58,8 +58,7 @@
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
-<s1 title="Xalan-Java Version 1.1.0">
-
+<s1 title="Xalan-Java Version 1.1.D01">
<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
@@ -67,9 +66,10 @@
<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>The primary motivation behind this release is to adjust to some changes in the &xml4j; API so you can use &xslt4j; with
- &xml4j-used;. This release also includes several bug fixes. For the details, see
- <link idref="readme" anchor="done">Changes in &xslt4j-current;</link>.</p>
+ <p><em>This is a Developer's release.</em> The primary motivation behind this release is to adjust to some
+ changes in the &xml4j; API so you can use &xslt4j; with &xml4j-used;. This release also includes several bug fixes.
+ We expect to provide a more extensively tested point release (1.1.0) with additional bug fixes in the near future.
+ For the details about this release, see <link idref="readme">Release Notes</link>.</p>
</s2>
<s2 title="How do I get it?">
1.13 +3 -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.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- readme.xml 2000/06/23 13:03:54 1.12
+++ readme.xml 2000/06/23 21:39:11 1.13
@@ -69,9 +69,11 @@
<s2 title="Status">
<ul>
<li><link anchor="done">Changes since version 1.0.1</link></li>
- <li><link anchor="bugs">Bug reporting</link></li>
+ <li><link anchor="bugs">Open bugs and bug reporting</link></li>
<li><link anchor="status">Version of Xerces to use</link></li>
</ul>
+ <p>&xslt4j-current; is a Developer's release. We plan to make a standard point release (Xalan-Java 1.1.0) with more extensive
+ testing and additional bug fixes shortly after the &xml4j; team releases &xml4j; 1.1.2.</p>
<anchor name="done"/>
&done-j;
<anchor name="bugs"/>