dleslie 00/05/31 08:57:57
Modified: xdocs/sources entities.ent xalan.xml xalandesign.xml
xdocs/sources/xalan BUGS DONE STATUS commandline.xml dtm.xml
extensions.xml faq.xml getstarted.xml index.xml
javadocOverview.xml org-apache-xalan-xpath-dtm.xml
overview.xml readme.xml resources.xml
usagepatterns.xml
Log:
partial update for upcoming 1.1 release.
Revision Changes Path
1.4 +4 -2 xml-xalan/xdocs/sources/entities.ent
Index: entities.ent
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/entities.ent,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- entities.ent 2000/03/16 21:21:48 1.3
+++ entities.ent 2000/05/31 15:57:43 1.4
@@ -1,7 +1,9 @@
<?xml encoding="US-ASCII"?>
-<!ENTITY xslt4j "Xalan">
+<!ENTITY xslt4j "Xalan-Java">
+<!ENTITY xslt4j-current "Xalan-Java version 1.1.0">
<!ENTITY xml4j "Xerces-Java">
+<!ENTITY xml4j-used "Xerces-Java version 1.1.0">
<!ENTITY xslt4c "Xalan-C++">
<!ENTITY xml4c "Xerces-C++">
<!ENTITY done-j SYSTEM "sbk:/sources/xalan/DONE">
@@ -10,5 +12,5 @@
<!ENTITY done-c SYSTEM "sbk:/sources/xalan/c/DONE">
<!ENTITY status-c SYSTEM "sbk:/sources/xalan/c/STATUS">
<!ENTITY bugs-c SYSTEM "sbk:/sources/xalan/c/BUGS">
-<!ENTITY download "The Xalan download from xml.apache.org includes
xerces.jar from Xerces-j version 1.0.3.">
+<!ENTITY download "The &xslt4j-current; download from xml.apache.org
includes xerces.jar from &xml4j-used;.">
1.7 +5 -4 xml-xalan/xdocs/sources/xalan.xml
Index: xalan.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- xalan.xml 2000/04/06 14:31:08 1.6
+++ xalan.xml 2000/05/31 15:57:44 1.7
@@ -67,7 +67,7 @@
<separator/>
<document id="index"
- label="Xalan-J 1.0.1"
+ label="Xalan-Java 1.1.0"
source="xalan/index.xml"/>
<external href="getstarted.html#download" label="Downloads"/>
@@ -125,10 +125,11 @@
<separator/>
<external href="http://xml.apache.org/bugs/"; label="Bug reporting"/>
+
+<separator/>
- <document id="xslt4c"
- label="Xalan C++"
- source="xalan/c/xslt4c.xml"/>
+
+<external href="design/design1_1_0.html" label="Xalan 2.0 Design"/>
</book>
1.2 +1 -1 xml-xalan/xdocs/sources/xalandesign.xml
Index: xalandesign.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalandesign.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- xalandesign.xml 2000/04/21 14:17:24 1.1
+++ xalandesign.xml 2000/05/31 15:57:44 1.2
@@ -61,7 +61,7 @@
<book title="Xalan 1.0.1 Design" copyright="2000 The Apache Software
Foundation">
<document id="design1_1_0"
- label="Xalan-J 1.1.0 Design"
+ label="Xalan-J 2.0.0 Design"
source="design/design1_1_0.xml"/>
</book>
1.6 +4 -2 xml-xalan/xdocs/sources/xalan/BUGS
Index: BUGS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/BUGS,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- BUGS 2000/04/11 16:17:29 1.5
+++ BUGS 2000/05/31 15:57:45 1.6
@@ -1,4 +1,6 @@
-<s3 title="Outstanding bugs">
+<s3 title="Bug reporting">
<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>
+ 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>
1.10 +10 -12 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- DONE 2000/04/12 17:59:48 1.9
+++ DONE 2000/05/31 15:57:46 1.10
@@ -1,14 +1,12 @@
-<s3 title="Bugs fixed since Xalan-J version 1.0.0">
- <p>The following bugs were found in version 1.0.0. They have been fixed,
and the fixes tested for version 1.0.1.</p>
+<s3 title="Changes since &xslt4c; 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>
+<p>We have also addressed several bugs found in version 1.0.1:</p>
<ul>
-<li>XPath expressions containing repeated multiplications (*) or divides
(div) without parentheses gave incorrect answers.</li>
-<li>The rendering of various characters to HTML sometimes crashed or gave
out-of-bounds error, and also caused erroneous Greek characters.</li>
-<li>A variable set within a template was de-scoped too soon, causing an
xsl:sort that used that variable and that appeared in an xsl:apply-templates to
work incorrectly.</li>
-<li>xsl:sort attributes failed to accept attribute value templates.</li>
-<li>FormatterToText incorrectly closed the output stream (this bug did not
apply to other formatters).</li>
-<li>In a for-each loop that selects but does not sort a node-set filtered by
a predicate, position() returned incorrect data.</li>
-<li>An imported stylesheet that used a relative path to include another
stylesheet did not work.</li>
-<li>A problem concerning the redeclaration of namespaces with the same
prefix has been fixed (Bugzilla bug 105).</li>
-<li>A problem with repeated use of an XPath object was fixed; repeated calls
to the XPathProcessorImpl.initXPath() method with different length XPath
expressions threw an ArrayIndexOutOfBoundsException.</li>
- </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>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></li>
+</ul>
</s3>
1.9 +3 -3 xml-xalan/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/STATUS,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- STATUS 2000/04/06 14:24:25 1.8
+++ STATUS 2000/05/31 15:57:46 1.9
@@ -1,9 +1,9 @@
-<s3 title="Version of Xerces to use">
-<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>
+ <s3 title="Version of Xerces to use">
+<p>The &xslt4j-current; has been tested with &xml4j-used; <ref>(the match in
version numbers is coincidental; as a general rule, the version numbers do not
match)</ref>. &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 title="To-do tasks for future Xalan releases">
+<s3 title="To-do tasks for future &xslt4j; releases">
<p>A top priority for the &xslt4j; team in the ongoing development of
&xslt4j; is to improve performance. This includes
enhanced support for SAX and incremental transformations, more efficient
trees than current implementations of the DOM
interfaces provide, and a number of possibilities pertaining to the
compilation of stylesheets, preprocessing XML/XPaths,
1.8 +5 -4 xml-xalan/xdocs/sources/xalan/commandline.xml
Index: commandline.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/commandline.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- commandline.xml 2000/03/16 18:59:32 1.7
+++ commandline.xml 2000/05/31 15:57:46 1.8
@@ -77,7 +77,7 @@
stylesheet, and the output file:<br/><br/>
<code>java org.apache.xalan.xslt.Process -IN foo.xml -XSL foo.xsl -OUT
foo.out</code>
</li></ol>
- <p>The command line utility can take the following flags and
arguments:</p>
+ <p>The command line utility can take the following flags and arguments
(the flags are case insensitive):</p>
<source>-IN inputXMLURL
-XSL XSLTransformationURL
-OUT outputFileName
@@ -111,9 +111,10 @@
<p>Use -TEXT if you want the output to include only element values
(not element tags with element names and
attributes).</p>
<p>Use -HTML to write 4.0 transitional HTML (some elements, such as
<br>, are
- not well formed.</p>
- <p>To set stylesheet parameters from the command line, use -PARAM name
expression. If
- you want to set the parameter to a string value, enclose the string in
single quotes (') to
+ not well formed XML.</p>
+ <p>To set stylesheet parameters from the command line, use <br/>
+ <code>TestXSLT -PARAM <ref>name expression</ref></code><br/>
+ To set the parameter to a string value, enclose the string in single
quotes (') to
make it an expression.</p>
<p><anchor name="compiledstylesheet"/><em>Using a compiled
stylesheet</em></p>
<p>If you are using a stylesheet repeatedly, you can improve
performance by compiling the stylesheet the first time
1.7 +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.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- dtm.xml 2000/03/16 18:59:32 1.6
+++ dtm.xml 2000/05/31 15:57:47 1.7
@@ -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
1.8 +1 -1 xml-xalan/xdocs/sources/xalan/extensions.xml
Index: extensions.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/extensions.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- extensions.xml 2000/03/16 18:59:32 1.7
+++ extensions.xml 2000/05/31 15:57:47 1.8
@@ -1,5 +1,5 @@
<?xml version="1.0" standalone="no"?>
-<!--
+<!--
* Copyright (c) 1999 Lotus Development Corporation, Inc. All Rights
Reserved.
* This software is provided without a warranty of any kind.
*
1.9 +4 -4 xml-xalan/xdocs/sources/xalan/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/faq.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- faq.xml 2000/03/17 12:49:41 1.8
+++ faq.xml 2000/05/31 15:57:47 1.9
@@ -9,7 +9,9 @@
<a><p>The definitive sources are the W3C XSLT and XPath recommendations:
<resource-ref idref="XSLT"/> and
<resource-ref idref="XPath"/>.</p>
<p>For general questions not specific to &xslt4j;, see Dave Pawson's
<jump
- href="http://freespace.virgin.net/b.pawson/xsl/index.html#top";>XSL
Frequently Asked Questions</jump>.</p>
+ href="http://freespace.virgin.net/b.pawson/xsl/index.html#top";>XSL
Frequently Asked Questions</jump> and
+ Michael Kay's <jump
href="http://www.wrox.com/Consumer/Store/Details.asp?ISBN=1861003129";>XSLT
Programmer's
+ Reference</jump>.</p>
<p>For a brief listing of tutorials, discussion forums, and other
materials, see <link idref="overview"
anchor="uptospeed">Getting up to speed with XSLT</link>.</p></a>
</faq>
@@ -99,7 +101,7 @@
<q>What can I do to speed up transformations?</q>
- <a><p>In the ongoing development of &xslt4j;, enhancing performance is
the primary goal of the &xslt4j; team.
+ <a><p>In the ongoing development of &xslt4j;, enhancing performance is
the primary goal of the &xslt4j; team.
Here are some preliminary
suggestions for you to keep in mind as you set up your
applications:</p><ul>
<li>Use the default DTM liaison and XML parser unless you need to read
or write a DOM. DOM is expensive in terms of memory,
@@ -120,8 +122,6 @@
<li>Be careful using the last() function.<br/><br/></li>
<li>The use of index predicates within match patterns can be
expensive.<br/><br/></li>
<li>Decoding and encoding is expensive.<br/><br/></li>
- <li>The serializer must check each character for escaping; 30% to
60% or processing time is typically spent in
- the serializer.</li>
</ul>
<li>For the ultimate in server-side scalability, perform transform
operations on the client. For an example, see
<link idref="samples"
anchor="appletxmltohtml">AppletXMLtoHTML</link>.</li>
1.15 +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.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- getstarted.xml 2000/04/10 18:55:23 1.14
+++ getstarted.xml 2000/05/31 15:57:47 1.15
@@ -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/xalan-j_1_0_1.zip";>xalan-j_1_0_1.zip</jump>
or <jump
href="http://xml.apache.org/dist/xalan-j/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>Download <jump
href="http://xml.apache.org/dist/xalan-j/xalan-j_1_1_0.zip";>xalan-j_1_1_0.zip</jump>
or <jump
href="http://xml.apache.org/dist/xalan-j/xalan-j_1_1_0.tar.gz";>xalan-j_1_1_0.tar.gz</jump>.
Both of these files contain <resource-ref idref="xalan-current"/> (with
xalan.jar) and xerces.jar from <resource-ref idref="xerces-used"/>. 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.3 +10 -8 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.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.xml 2000/04/10 18:55:23 1.2
+++ index.xml 2000/05/31 15:57:48 1.3
@@ -58,29 +58,31 @@
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
-<s1 title="Xalan-J Version 1.0.1">
+<s1 title="Xalan-Java Version 1.1.0">
<s2 title="What is it?">
- <p>Xalan is an XSL processor for transforming XML documents into HTML,
text, or other XML document types. Xalan-J Version
- 1.0.1 represents a complete and a robust reference Java implementation
of the W3C Recommendations for XSL Transformations
+ <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
(XSLT) and the XML Path Language (XPath).</p>
<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>
</s2>
<s2 title="How do I get it?">
<p>Download and unzip either of the following:</p>
<ul>
- <li><jump
href="http://xml.apache.org/dist/xalan-j/xalan-j_1_0_1.zip";>xalan-j_1_0_1.zip</jump></li>
- <li><jump
href="http://xml.apache.org/dist/xalan-j/xalan-j_1_0_1.tar.gz";>xalan-j_1_0_1.tar.gz</jump></li>
+ <li><jump
href="http://xml.apache.org/dist/xalan-j/xalan-j_1_1_0.zip";>xalan-j_1_1_0.zip</jump></li>
+ <li><jump
href="http://xml.apache.org/dist/xalan-j/xalan-j_1_1_0.tar.gz";>xalan-j_1_1_0.tar.gz</jump></li>
</ul>
</s2>
<s2 title="Where do I get the Xerces XML parser?">
- <p>The Xalan dowload includes xerces.jar from Xerces-J 1.0.3. This is
all you need to run Xalan. You can, however, download
- the complete Xerces distribution from the xml.apache.org <jump
href="http://xml.apache.org/dist/xerces-j/";>Xerces-J
- Distribution directory</jump>.</p>
+ <p>The Xalan dowload includes xerces.jar from &xml4j-used;. This is all
you need to run Xalan.
+ You can, however, download the complete Xerces distribution from the
<resource-ref idref="xerces-j-dist"/>.</p>
</s2>
<s2 title="What else do I need?">
<p>You need the Java Development Kit or Java Runtime 1.1.8 or 1.2.2,
which you can obtain from <jump
1.8 +1 -1 xml-xalan/xdocs/sources/xalan/javadocOverview.xml
Index: javadocOverview.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/javadocOverview.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- javadocOverview.xml 2000/03/16 18:59:33 1.7
+++ javadocOverview.xml 2000/05/31 15:57:48 1.8
@@ -1,4 +1,4 @@
-<?xml version="1.0" standalone="no"?>
+<?xml version="1.0" standalone="no"?>
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
<!--
1.6 +1 -1
xml-xalan/xdocs/sources/xalan/org-apache-xalan-xpath-dtm.xml
Index: org-apache-xalan-xpath-dtm.xml
===================================================================
RCS file:
/home/cvs/xml-xalan/xdocs/sources/xalan/org-apache-xalan-xpath-dtm.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- org-apache-xalan-xpath-dtm.xml 2000/03/16 18:59:33 1.5
+++ org-apache-xalan-xpath-dtm.xml 2000/05/31 15:57:49 1.6
@@ -1,4 +1,4 @@
-<?xml version="1.0" standalone="no"?>
+<?xml version="1.0" standalone="no"?>
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
<!--
1.10 +24 -13 xml-xalan/xdocs/sources/xalan/overview.xml
Index: overview.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/overview.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- overview.xml 2000/03/06 13:31:48 1.9
+++ overview.xml 2000/05/31 15:57:49 1.10
@@ -79,7 +79,7 @@
transforming XML documents from one document type into another document
type (XML, HTML, or other). In structural
terms, an XSL stylesheet specifies the transformation of one tree of
nodes (the XML input) into another tree of nodes
(the output or transformation result).</p>
- <note>The XSL stylesheet may include cascading style sheets (CSS) in the
result.</note>
+ <note>The XSL stylesheet may generate and refer to cascading style
sheets (CSS) as part of its output.</note>
<p>In the following example, the foo.xsl stylesheet is used to transform
foo.xml into foo.out:</p>
<p>foo.xml:</p>
<source><?xml version="1.0"?>
@@ -106,7 +106,8 @@
<li>Interfaces directly to the <jump
href="http://xml.apache.org/xerces-j/index.html";>&xml4j; XML parser</jump></li>
<li>Can interface to a SAX document handler or to any XML parser that
produces Java DOM Trees</li>
<li>Can output to SAX or DOM</li>
- <li>May be run from the <link idref="commandline">command
line</link></li>
+ <li>May be run from the <link idref="commandline">command
line</link> for convenient file-to-file
+ transformations<br/><br/></li>
<li>Includes an <link idref="getstarted" anchor="applet">applet
wrapper</link></li>
<li>May be used in a <link idref="samples"
anchor="servlet">servlet</link> to transform XML documents into HTML
and serve the results to clients</li>
@@ -139,31 +140,40 @@
<br/><br/></li>
<li>OASIS (the Organization for the Advancement of Structured
Information Standards):
<jump href="http://www.oasis-open.org/cover/xsl.html";>Extensible
Stylesheet Language (XSL)</jump> by Robin
- Cover</li>
+ Cover<br/><br/></li>
<li>Donald Ball's <jump
href="http://www.webslingerZ.com/balld/xsl/designer_manual.xml";>A Guide to XML
and XSL for Designers</jump><br/><br/></li>
+ <li>XSLT - XSL Transformations in
+ <jump href="http://www.brics.dk/~amoeller/XML/";>The XML Revolution:
Technologies for the future Web</jump> by
+ Anders Møller and Michael I. Schwartzbach<br/><br/></li>
+ <li>Michael Kay's <jump
href="http://www.wrox.com/Consumer/Store/Details.asp?ISBN=1861003129";>XSLT
Programmer's
+ Reference</jump>, Wrox Press, April 2000</li>
</ul>
<p>When you come across other useful introductory or background
materials, please email <human-resource-ref
idref="dleslie"/>, so he can add them to this list.</p>
</s2><anchor name="glossary"/>
- <s2 title="Glossary">
+ <s2 title="Glossary">
<gloss>
+ <label>XSLT Namespace</label>
+ <item>The <jump href="http://www.w3.org/TR/REC-xml-names/";>XML
namespace</jump> for XSLT. An XML namespace is a
+ collection of element and attribute names, identified by a Unique
Resource Identifier (URI), which often takes the form of
+ a URL, but is really just a unique string, not a pointer to a web
page. The XSLT namespace URI is
+ http://www.w3.org/1999/XSL/Transform. In each XSLT stylesheet, you
must declare this namespace in the stylesheet element
+ tag and bind it to a local prefix. Like the XSLT specification, we
always use xsl as the XSLT namespace prefix in our
+ descriptions and examples, although you are free to bind any prefix
to this namespace.<br/><br/></item>
+
<label>XSL Instruction</label>
- <item>Any tag with an XSL namespace prefix.<br/><br/></item>
+ <item>Any tag associated with the XSLT namespace.<br/><br/></item>
<label>Template</label>
<item>An element, usually with child elements, that specifies a
"rule" or set of
instructions to perform when a particular kind of node is
encountered in the source tree.<br/><br/></item>
<label>XSL Template Instruction</label>
- <item>Any tag with an XSL namespace prefix
- that occurs inside an xsl:template element.<br/><br/></item>
-
- <label>Template Child</label>
- <item>Any node that is a child of an xsl:template
element.<br/><br/></item>
-
+ <item>Any tag that occurs inside an xsl:template element and is
associated with the XSLT namespace.<br/><br/></item>
+
<label>Source Tree</label>
- <item>The tree input to the XSL process.<br/><br/></item>
+ <item>The XML tree input to the XSL process.<br/><br/></item>
<label>Result Tree</label>
<item>The tree that is output by the XSL process.<br/><br/></item>
@@ -177,6 +187,7 @@
</gloss>
<p>For more definitions of XSLT terminology, see Dave Pawson's
<jump
href="http://freespace.virgin.net/b.pawson/xsl/xslvocab.html#top";>XSLT
Terminology
- Clarification</jump>.</p>
+ Clarification</jump> and the Glossary in Michael Kay's
+ <jump
href="http://www.wrox.com/Consumer/Store/Details.asp?ISBN=1861003129";>XSLT
Programmer's Reference</jump>.</p>
</s2>
</s1>
1.10 +3 -3 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.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- readme.xml 2000/04/11 16:17:29 1.9
+++ readme.xml 2000/05/31 15:57:50 1.10
@@ -68,8 +68,8 @@
</ul>
<s2 title="Status">
<ul>
- <li><link anchor="done">Bug fixes</link></li>
- <li><link anchor="bugs">Outstanding bugs</link></li>
+ <li><link anchor="done">Changes since version 1.0.1</link></li>
+ <li><link anchor="bugs">Bug reporting</link></li>
<li><link anchor="status">Version of Xerces to use</link></li>
</ul>
<anchor name="done"/>
@@ -95,7 +95,7 @@
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>
+ <li>Place <resource-ref idref="xerces-j-used"/> xerces.jar in the
Java class path.<br/><br/></li>
<li>If you are working in Windows, set MAKE_MODE as follows:<br/><br/>
<code>set MAKE_MODE=UNIX</code><br/><br/></li>
<li>Run the make file in the &xslt4j; root directory:<br/><br/>
1.11 +5 -6 xml-xalan/xdocs/sources/xalan/resources.xml
Index: resources.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/resources.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- resources.xml 2000/04/10 18:55:23 1.10
+++ resources.xml 2000/05/31 15:57:51 1.11
@@ -14,9 +14,12 @@
<resources>
&apiResources;
- <resource id="Xalan-current" title="Xalan-Java 1.0.1 XSLT Processor"
location="http://xml.apache.org/xalan"/>
- <resource id="Xalan-dist" title="Xalan distribution"
location="http://xml.apache.org/dist/xalan-j/"/>
+ <resource id="xalan-j-current" title="Xalan-Java 1.1.0 XSLT Processor"
location="http://xml.apache.org/xalan"/>
+ <resource id="xalan-j-dist" title="Xalan-Java distribution directory"
location="http://xml.apache.org/dist/xalan-j/"/>
<resource id="LotusXSL-current" title="LotusXSL 1.0.0"
location="http://www.alphaworks.ibm.com/tech/LotusXSL"/>
+ <resource id="xml4j-used" title="the XML Parser for Java Version 3.0.0EA3"
location="http://www.alphaworks.ibm.com/tech/xml4j"/>
+ <resource id="xerces-j-used" title="Xerces-Java Version 1.1.0"
location="http://xml.apache.org/xerces-j/index.html"/>
+
<resource id="ApacheLicense" title="The Apache Software License, Version
1.1" location="http://xml.apache.org/dist/LICENSE.txt"/>
@@ -32,11 +35,7 @@
<resource id="DOM-draft-august" title="August 18 Document Object Model
(DOM) Level 1 Specification"
location="http://www.w3.org/TR/1998/PR-DOM-Level-1-19980818/"/>
<resource id="DOM-draft-october" title="October 1 Document Object Model
(DOM) Level 1 Specification"
location="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001"/>
<resource id="DOM" title="DOM" location="http://www.w3.org/DOM"/>
-
- <resource id="xml4j-used" title="Version 3.0.0EA3 of the XML Parser for
Java" location="http://www.alphaworks.ibm.com/tech/xml4j"/>
- <resource id="xerces-used" title="Version 1.0.3 of Xerces-Java"
location="http://xml.apache.org/xerces-j/index.html"/>
-
<resource id="JRE1.2" title="Sun's JRE-1.2"
location="http://java.sun.com/products/jdk/1.2/jre/index.html"/>
<resource id="JDK1.2" title="Sun's JDK-1.2"
location="http://java.sun.com/products/jdk/1.2/"/>
<resource id="JDK1.1" title="Sun's JDK-1.1"
location="http://java.sun.com/products/jdk/1.1/"/>
1.9 +4 -3 xml-xalan/xdocs/sources/xalan/usagepatterns.xml
Index: usagepatterns.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/usagepatterns.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- usagepatterns.xml 2000/04/24 17:02:59 1.8
+++ usagepatterns.xml 2000/05/31 15:57:51 1.9
@@ -75,8 +75,9 @@
</ul><anchor name="intro"/>
<s2 title="Introduction">
-<p>&xslt4j; takes as primary input an XML source document and an XSL
stylesheet, both represented by instances of the <resource-ref
idref="XSLTInputSourceDoc"/>. You can use a URL or file, a character stream, a
byte stream, a DOM tree, or a SAX input source to create an XSLTInputSource
object. The stylesheet may also take the form of a compiled stylesheet (an
instance of the <resource-ref idref="StylesheetRootDoc"/>. If the XML document
contains a stylesheet Processing Instruction (PI), a separate stylesheet is not
required.</p>
-<p>&xslt4j; uses an implementation of the <resource-ref
idref="XMLParserLiaisonDoc"/> to interact with an XML parser and sends the
output to <resource-ref idref="XSLTResultTargetDoc"/>. Unless your are reading
or creating a DOM, you probably want to use the default <link idref="dtm">DTM
(Document Table Model)</link> liaison and XML parser. When you read from a DOM
or write to a DOM, use the <resource-ref idref="XercesLiaisonDoc"/> along with
the &xml4j; XML parser.</p>
+<p>&xslt4j; takes as primary input an XML source document and an XSL
stylesheet, both represented by instances of the <resource-ref
idref="XSLTInputSourceDoc"/>. You can use a URL or file, a character stream, a
byte stream, a DOM tree, or a SAX input source to create an XSLTInputSource
object. The stylesheet may also take the form of a compiled stylesheet (an
instance of the <resource-ref idref="StylesheetRootDoc"/>.</p>
+<note>If the XML document contains a stylesheet Processing Instruction (PI),
&xslt4j; uses the stylesheet this PI points to and a separate stylesheet object
is not required.</note>
+<p>&xslt4j; uses an implementation of the <resource-ref
idref="XMLParserLiaisonDoc"/> to interact with an XML parser and sends the
output to <resource-ref idref="XSLTResultTargetDoc"/>, which may be configured
to write to a file, a character stream, a byte stream, a DOM tree, or a SAX
document handler. Unless your are reading or creating a DOM, you probably want
to use the default <link idref="dtm">DTM (Document Table Model)</link> liaison
and XML parser. When you read from a DOM or write to a DOM, use the
<resource-ref idref="XercesLiaisonDoc"/> along with the &xml4j; XML parser.</p>
<p>The XSLT and XPath engines are independent of any given XML parser
implementation. All parser-dependent
calls are funneled through the XMLParserLiaison.</p>
<p>For detailed API documentation (javadoc), see <resource-ref
idref="APIDocumentation"/>. For an overview of the
@@ -124,7 +125,7 @@
<p>To set a stylesheet parameter, use the XSLTProcessor
setStylesheetParam(String key, String expression) method, where key is the
parameter name and expression is an XPath expression. If the parameter is a
String, enclose it in single quotes to make it a String expression.</p>
<p>You can also use setStylesheetParam(String key, XObject value). This
option is useful when you are working with the XPath API. For example, you
could use the XObject returned by an Xpath function to set a parameter.</p>
<p>You can include a -param argument when you call the <link
idref="commandline">command line utility</link>.For example:</p>
-<p><code>java org.apache.xalan.xslt.Process -in foo.xml -xsl foo.xsl -param
'boo'</code></p>
+<p><code>java org.apache.xalan.xslt.Process -in foo.xml -xsl foo.xsl -param
param1 'boo'</code></p>
<p>The <link idref="samples"
anchor="usestylesheetparam">UseStylesheetParam</link> sample application also
uses a command-line parameter.</p>
<p>For information about using stylesheet parameters with a compiled
stylesheet, see the next section.</p>
</s2><anchor name="compiled"/>
