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/04/06 16:17:17 UTC
cvs commit: xml-xalan/xdocs/sources/xalan STATUS readme.xml getstarted.xml dtm.xml
dleslie 00/04/06 07:17:17
Modified: xdocs/sources/xalan Tag: Bxalan_1_0_0 STATUS readme.xml
getstarted.xml dtm.xml
Log:
updated version number to 1.0.1 and fixed doc bugs per
SPR #DLEE4HNTG4
Revision Changes Path
No revision
No revision
1.3.2.4 +1 -1 xml-xalan/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/STATUS,v
retrieving revision 1.3.2.3
retrieving revision 1.3.2.4
diff -u -r1.3.2.3 -r1.3.2.4
--- STATUS 2000/03/17 12:46:45 1.3.2.3
+++ STATUS 2000/04/06 14:17:16 1.3.2.4
@@ -1,5 +1,5 @@
<s3 title="Version of Xerces to use">
-<p>Xalan-J version 1.0.0 has been tested with Xerces-j version 1.0.3. &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>Xalan-J version 1.0.1 has been tested with Xerces-j version 1.0.3. &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>
1.5.2.3 +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.5.2.2
retrieving revision 1.5.2.3
diff -u -r1.5.2.2 -r1.5.2.3
--- readme.xml 2000/03/17 12:46:46 1.5.2.2
+++ readme.xml 2000/04/06 14:17:16 1.5.2.3
@@ -89,7 +89,7 @@
If you want to rebuild xalan.jar, you can do the following:</p>
<ol>
<li>Set up GNU or the equivalent build environment on your workstation.<br/><br/>
- If you are running Windows 95/98/NT, you can use the Cygwin port of GNU. Be sure to put the
+ If you are running Windows 95/98/2000/NT, you can use the Cygwin port of GNU. Be sure to put the
appropriate Cygwin bin directory at the beginning of your system path. For information about
Cygwin, see <jump href="http://www.sourceware.cygnus.com/cygwin/">Cygwin</jump>.<br/><br/></li>
<li>Place <resource-ref idref="xerces-used"/> xerces.jar in the Java class path.<br/><br/></li>
1.6.2.5 +1 -1 xml-xalan/xdocs/sources/xalan/getstarted.xml
Index: getstarted.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/getstarted.xml,v
retrieving revision 1.6.2.4
retrieving revision 1.6.2.5
diff -u -r1.6.2.4 -r1.6.2.5
--- getstarted.xml 2000/03/17 12:46:46 1.6.2.4
+++ getstarted.xml 2000/04/06 14:17:16 1.6.2.5
@@ -18,7 +18,7 @@
<li>xerces.jar</li>
</ul>
<p>You can get the JDK or JRE from <jump href="http://www.ibm.com/java/jdk">ibm.com/java/jdk/</jump> or <jump href="http://www.java.sun.com">java.sun.com</jump>.</p>
-<p>Download <jump href="http://xml.apache.org/dist/xalan-j_1_0_0.zip">xalan-j_1_0_0.jar</jump> or <jump href="http://xml.apache.org/dist/xalan-j_1_0_0.tar.gz">xalan-j_1_0_0.tar.gz</jump>. Both of these files contain &xslt4j; 1.0.0 (with xalan.jar) and xerces.jar from Xerces-J 1.0.3. You can use a zip or tar utility to expand these files into a full build.</p>
+<p>Download <jump href="http://xml.apache.org/dist/xalan-j_1_0_1.zip">xalan-j_1_0_1.zip</jump> or <jump href="http://xml.apache.org/dist/xalan-j_1_0_1.tar.gz">xalan-j_1_0_1.tar.gz</jump>. Both of these files contain &xslt4j; 1.0.1 (with xalan.jar) and xerces.jar from Xerces-J 1.0.3. You can use a zip or tar utility to expand these files into a full build.</p>
<p>If you plan to run <link idref="extensions">XSLT extensions</link>, you need bsf.jar and bsfengines.jar, both of which are included in the &xslt4j; distribution. If you plan to run XSLT extensions implemented in JavaScript or another scripting language, you will need one or more additional files as indicated in <link idref="extensions" anchor="supported-lang">extensions language requirements</link>.</p>
</s2><anchor name="classpath"/>
1.5.2.2 +2 -2 xml-xalan/xdocs/sources/xalan/dtm.xml
Index: dtm.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/dtm.xml,v
retrieving revision 1.5.2.1
retrieving revision 1.5.2.2
diff -u -r1.5.2.1 -r1.5.2.2
--- dtm.xml 2000/03/16 18:50:09 1.5.2.1
+++ dtm.xml 2000/04/06 14:17:16 1.5.2.2
@@ -1,5 +1,5 @@
<?xml version="1.0" standalone="no"?>
-<!--
+<!--
* The Apache Software License, Version 1.1
*
*
@@ -65,7 +65,7 @@
with XML documents. &xslt4j; supports this interface. For large XML documents, however, this may involve considerable
overhead, since &xslt4j; must create one or more Java objects for each Node in the document DOM tree.</p>
<p>For the majority of cases -- your input and output are URLs, files, or streams, and you use the default Liaison
- (<resource-ref idref="DTMLiaisonDoc"/>) and XML parser, &xslt4j; avoids this overhead by implementing the Document Table
+ (<resource-ref idref="DTMLiaisonDoc"/>) and XML parser -- &xslt4j; avoids this overhead by implementing the Document Table
Model (DTM), a "pseudo-DOM" that uses integer arrays in place of the DOM. For larger input and output trees, the
performance improvements can be very significant.</p>
<p>The <resource-ref idref="XSLTProcessorFactoryGetProcessorDoc"/> sets up an XSLT processor to use the default DTM liaison