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/28 21:31:29 UTC
cvs commit: xml-xalan/xdocs/sources/xalan DONE index.xml readme.xml
dleslie 00/06/28 12:31:28
Modified: xdocs/sources/xalan DONE index.xml readme.xml
Log:
Updated for version 1.1
Revision Changes Path
1.15 +38 -6 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- DONE 2000/06/23 21:39:10 1.14
+++ DONE 2000/06/28 19:31:22 1.15
@@ -1,5 +1,36 @@
<s3 title="Changes since &xslt4j; version 1.0.1">
- <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>
+<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>
@@ -10,13 +41,11 @@
<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>
+</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.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><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>
@@ -33,4 +62,7 @@
processor.process(new XSLTInputSource(xmlName),
new XSLTInputSource(xslName),
new XSLTResultTarget(formatter));</source>
+</s4><anchor name="ant0"/><s4 title="">
+<p>We have upgraded support for using Apache Ant to build &xslt4j;. For the details, see <link anchor="ant">Using Ant</link>.</p>
+</s4>
</s3>
1.6 +2 -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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- index.xml 2000/06/23 21:39:10 1.5
+++ index.xml 2000/06/28 19:31:23 1.6
@@ -58,7 +58,7 @@
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
-<s1 title="Xalan-Java Version 1.1.D01">
+<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
@@ -66,10 +66,7 @@
<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><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>
+ <p>For the details about this release, see <link idref="readme">Release Notes</link>.</p>
</s2>
<s2 title="How do I get it?">
1.14 +1 -0 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.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- readme.xml 2000/06/23 21:39:11 1.13
+++ readme.xml 2000/06/28 19:31:23 1.14
@@ -96,6 +96,7 @@
Windows32 batch file (build.bat) and a UNIX shell file (build.sh). The build file defines the "targets" that you can use Ant
to build. The batch and shell files set up the classpath and launch Ant with the target (and any other arguments) you
provide.</p>
+ <note>We still use makefiles to build the distribution copy of &xslt4j;.</note>
<p><em>Instructions for using Ant</em></p>
<ol>
<li>Set the JAVA_HOME environment variable to the JDK root directory.<br/><br/>