dleslie 01/12/20 05:57:15
Modified: c/xdocs DoxyfileXalan
c/xdocs/html/apiDocs footer.html header.html tail.html
c/xdocs/sources entities.ent xalan.xml
c/xdocs/sources/xalan commandline.xml faq.xml getstarted.xml
history.xml index.xml readme.xml resources.xml
samples.xml usagepatterns.xml
Log:
Updates for release 1.3
Revision Changes Path
1.11 +1 -1 xml-xalan/c/xdocs/DoxyfileXalan
Index: DoxyfileXalan
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/DoxyfileXalan,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- DoxyfileXalan 2001/08/09 20:18:30 1.10
+++ DoxyfileXalan 2001/12/20 13:57:14 1.11
@@ -204,7 +204,7 @@
# directories like "/usr/src/myproject". Separate the files or directories
# with spaces.
-INPUT = ../src/DOMSupport ../src/ICUBridge ../src/Include
../src/PlatformSupport ../src/TestXSLT ../src/XalanDOM ../src/XalanSourceTree
../src/XalanTransformer ../src/XercesParserLiaison ../src/XMLSupport
../src/XPath ../src/XSLT ../src/XalanExtensions
+INPUT = ../src/DOMSupport ../src/ICUBridge ../src/Include
../src/PlatformSupport ../src/TestXSLT ../src/XalanDOM ../src/XalanSourceTree
../src/XalanTransformer ../src/XercesParserLiaison ../src/XMLSupport
../src/XPath ../src/XSLT ../src/XalanExtensions ../src/XalanExe
../src/XpathCAPI
# If the value of the INPUT tag contains directories, you can use the
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
1.6 +1 -1 xml-xalan/c/xdocs/html/apiDocs/footer.html
Index: footer.html
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/html/apiDocs/footer.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- footer.html 2001/08/20 20:25:40 1.5
+++ footer.html 2001/12/20 13:57:14 1.6
@@ -7,7 +7,7 @@
<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="80%">
<TR>
<TD WIDTH="80%" VALIGN="TOP">
- <P ALIGN="CENTER"><B>Xalan-C++ XSL Transformer Version
1.2</B><BR>
+ <P ALIGN="CENTER"><B>Xalan-C++ XSLT Processor Version
1.3</B><BR>
Copyright © 2000, 2001 The Apache Software
Foundation. All Rights Reserved.</i></p>
</TD>
</TR>
1.5 +1 -1 xml-xalan/c/xdocs/html/apiDocs/header.html
Index: header.html
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/html/apiDocs/header.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- header.html 2001/08/20 20:25:40 1.4
+++ header.html 2001/12/20 13:57:14 1.5
@@ -1,5 +1,5 @@
<HTML><HEAD><TITLE>Xalan-C++ API Documentation</TITLE></HEAD>
<BODY>
<h2 align="center">Xalan-C++ API Documentation</h2>
-<h3 align="center">The Xalan C++ XSL Transformer Version 1.2</h3>
+<h3 align="center">The Xalan C++ XSLT Processor Version 1.3</h3>
</BODY>
1.5 +1 -1 xml-xalan/c/xdocs/html/apiDocs/tail.html
Index: tail.html
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/html/apiDocs/tail.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- tail.html 2001/08/20 20:25:40 1.4
+++ tail.html 2001/12/20 13:57:14 1.5
@@ -2,7 +2,7 @@
<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="80%">
<TR>
<TD WIDTH="100%" VALIGN="TOP">
- <P ALIGN="CENTER"><B>Xerces-C XML Parser for C++
Version 1.5.1</B><BR>
+ <P ALIGN="CENTER"><B>Xerces-C XML Parser for C++
Version 1.6.0</B><BR>
Copyright © 2000,2001 The Apache Software
Foundation. All Rights Reserved.
</TD>
</TR>
1.21 +15 -12 xml-xalan/c/xdocs/sources/entities.ent
Index: entities.ent
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/entities.ent,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- entities.ent 2001/08/10 19:16:43 1.20
+++ entities.ent 2001/12/20 13:57:15 1.21
@@ -1,21 +1,24 @@
<?xml encoding="US-ASCII"?>
<!ENTITY xslt4c "Xalan-C++">
-<!ENTITY xslt4c-dist "Xalan-C_1_2">
-<!ENTITY xslt4c-current "Xalan-C++ version 1.2">
+<!ENTITY xslt4c-dist "Xalan-C_1_3">
+<!ENTITY xslt4c-current "Xalan-C++ version 1.3">
<!ENTITY xslt4c-windlls "DOMSupport.dll, PlatformSupport.dll, XalanDOM.dll,
XalanSourceTree,dll, XercesParserLiaison.dll, XMLSupport.dll, XPath.dll,
XSLT.dll, XalanTransformer.dll, XalanExtensions.dll">
-<!ENTITY xslt4c-linuxlib "libxalan-c1_2.so">
-<!ENTITY xslt4c-aixlib "libxalan-c1_2.a">
-<!ENTITY xslt4c-hplib "libxalan-c1_2.sl">
-<!ENTITY xslt4c-solarislib "libxalan-c1_2.so">
+<!ENTITY xslt4c-linuxlib "libxalan-c1_3.so">
+<!ENTITY xslt4c-aixlib "libxalan-c1_3.a">
+<!ENTITY xslt4c-hplib "libxalan-c1_3.sl">
+<!--ENTITY xslt4c-solarislib "libxalan-c1_3.so"-->
+<!ENTITY xslt4c-solarislib "[This release does not include a Solaris build]">
<!ENTITY xml4c "Xerces-C++">
-<!ENTITY xml4c-used "Xerces-C++ version 1.5.1">
-<!ENTITY xml4c-windll "xerces-c_1_5_1.dll">
+<!ENTITY xml4c-used "Xerces-C++ version 1.6.0">
+<!ENTITY xml4c-windll "xerces-c_1_6_0.dll">
<!ENTITY xml4c-winlib "xerces-c_1.lib">
-<!ENTITY xml4c-linuxlib "libxerces-c1_5_1.so">
-<!ENTITY xml4c-aixlib "libxerces-c1_5_1.a">
-<!ENTITY xml4c-hplib "libxerces-c1_5_1.sl">
-<!ENTITY xml4c-solarislib "libxerces-c1_5_1.so">
+<!ENTITY xml4c-linuxlib "libxerces-c1_6_0.so">
+<!ENTITY xml4c-aixlib "libxerces-c1_6_0.a">
+<!ENTITY xml4c-hplib "libxerces-c1_6_0.sl">
+<!--ENTITY xml4c-solarislib "libxerces-c1_6_0.so"-->
+<!ENTITY xml4c-solarislib "[This release does not include a Solaris build]">
+<!ENTITY solarisbuild " [We do not have the resources to include a Solaris
build with this release.]">
<!ENTITY xslt4j "Xalan-Java">
<!ENTITY icu-used "International Components for Unicode(ICU) 1.8.1 source
files">
<!ENTITY icu-windlls "icui18n.dll, icuuc.dll">
1.9 +1 -1 xml-xalan/c/xdocs/sources/xalan.xml
Index: xalan.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- xalan.xml 2001/08/09 20:10:36 1.8
+++ xalan.xml 2001/12/20 13:57:15 1.9
@@ -67,7 +67,7 @@
<separator/>
<document id="index"
- label="Xalan-C++ 1.2"
+ label="Xalan-C++ 1.3"
source="xalan/index.xml"/>
<separator/>
1.21 +48 -34 xml-xalan/c/xdocs/sources/xalan/commandline.xml
Index: commandline.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/commandline.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- commandline.xml 2001/08/27 19:45:22 1.20
+++ commandline.xml 2001/12/20 13:57:15 1.21
@@ -61,32 +61,47 @@
<s1 title="&xslt4c; Command-Line Utility">
<ul>
-<li><link anchor="use">Using the Command-Line Utility</link></li>
-<li><link anchor="icu">Enabling ICU support for testXSLT</link></li>
+<li><link anchor="use">Using a command-line utility</link></li>
+<li><link anchor="xalanexe">Using the Xalan executable</link></li>
+<li><link anchor="testXSLT">Using TestXSLT</link></li>
+<li><link anchor="icu">Enabling ICU support for the Xalan executable and/or
testXSLT</link></li>
</ul><anchor name="use"/>
-
- <s2 title="Using the Command-Line Utility">
- <p>To perform a transformation, you can call &xslt4c; from the command
line (or script),
+<s2 title="Using a command-line utility">
+<p>To perform a transformation, you can call &xslt4c; from the command line
(or script),
or from within an application (see <link idref="usagepatterns">Usage
Patterns</link>).</p>
- <p>The testXSLT executable provides a command-line interface
- for performing XSL transformation. To perform a transformation from the
command line or a script,
+<p>To perform a transformation from the command line or a script, you can
use Xalan or testXSLT. The testXSLT executable has been around since the
inception of &xslt4c; and supports a variety of options. The Xalan executable
is newer, simpler to use, and supports fewer options.</p>
+<p>To perform a transformation from the command line or a script with either
executable,
do the following:</p>
<ol>
<li><link idref="getstarted" anchor="download">Download
&xslt4c;</link>.<br/><br/></li>
- <li><link idref="getstarted"
- anchor="path">Set the path</link> to include the build
directory.<br/><br/></li>
- <li>Call the testXSLT executable with the appropriate flags and
- arguments (described below). The following command line, for example,
includes the -IN, -XSL,
- and -OUT flags with their accompanying arguments -- the XML source
document, the XSL
+ <li><link idref="getstarted" anchor="path">Set the path</link> to
include the build directory.<br/><br/></li>
+ <li>Call the executable with the appropriate flags and arguments
(described below).</li>
+ </ol>
+</s2><anchor name="xalanexe"/>
+<s2 title="Using the Xalan executable">
+<p>Call the Xalan executable as follows:<br/><br/>
+<code>Xalan <ref>[options]</ref> <ref>xmlSource</ref>
<ref>xslStylesheet</ref></code><br/><br/>
+where <ref>xmlSource</ref> is the XML source document,
<ref>xslStylesheet</ref> is the stylesheet to apply, and <ref>[options]</ref>
are any (or none) of the following:</p>
+<table>
+ <tr><th>Option</th><th>Description</th></tr>
+ <tr><td>-a</td><td>Use stylesheet processing instruction, not the
stylesheet argument.</td></tr>
+ <tr><td>-o filename</td><td>Write transformation result to this file
(rather than to the console).</td></tr>
+ <tr><td>-p name expr</td><td>Set a stylesheet parameter with this
expression</td></tr>
+ <tr><td>-v</td><td>Validate the XML source document.</td></tr>
+ </table>
+ <p>To display a list of the options call the Xalan executable as
follows:</p>
+<p><code>Xalan ?</code></p>
+</s2><anchor name="testxslt"/>
+<s2 title="Using TestXSLT">
+ <p>Call the testXSLT executable with the flags and arguments described
below. The following command line, for example, includes the -IN, -XSL, and
-OUT flags with their accompanying arguments -- the XML source document, the XSL
stylesheet, and the output file:<br/><br/>
- <code>testXSLT -IN foo.xml -XSL foo.xsl -OUT foo.out</code>
- </li></ol>
- <p>The command line utility can take the following flags and arguments
(the flags are case insensitive):</p>
+ <code>testXSLT -IN foo.xml -XSL foo.xsl -OUT foo.out</code></p>
+ <p>The testXSLT executable can take the following flags and arguments
(the flags are case insensitive):</p>
<source>-IN inputXMLURL
-XSL XSLTransformationURL
-OUT outputFileName
--ESCAPE chars(Which characters to escape -- default is <>&"'\r\n)
--EER (Expand entity references --default is not to expand)
+-H (Display list of command-line options)
+-? (Display list of command-line options)
-V (Version info)
-QC (Quiet Pattern Conflicts Warnings)
-Q (Quiet Mode)
@@ -109,15 +124,13 @@
-DOM (Test for well-formed output --format to DOM then to XML for output)
-XST (Format to Xalan source tree, then to XML for output)
-XD (Use Xerces DOM instead of Xalan source tree)
--DE Disable built-in <link idref="extensionslib">extension functions</link>)
+-DE Disable built-in extension functions)
-EN (Specify the namespace URI for Xalan extension functions; the default
is 'http://xml.apache.org/xslt')
--PARAM name expression (Set a stylesheet parameter)
-
-
-</source>
+-PARAM name expression (Set a stylesheet parameter)</source>
<p>Use -IN to specify the XML source document.</p>
<p>Use -XSL to specify the XSL stylesheet file.</p>
+ <p>Use -DE not to load the standard set of <link
idref="extensionslib">extension functions</link>.</p>
<p>Use -TEXT if you want the output to include only text nodes without
any escaping.</p>
<p>Use -HTML to write 4.0 transitional HTML (some elements, such as
<br>, are
not well formed XML).</p>
@@ -125,29 +138,30 @@
<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>
- </s2><anchor name="icu"/>
- <s2 title="Enabling ICU support for testXSLT">
+ </s2><anchor name="icu"/>
+ <s2 title="Enabling ICU support for the Xalan executable and/or
testXSLT">
<p>You can set up the <resource-ref idref="icu"/> to enhance the
support that &xslt4c; provides for encoding, number
formatting, and sorting. For more information, see <link
idref="usagepatterns" anchor="icu">Using the ICU</link>.</p>
- <p>If you have built and integrated the ICU with &xml4c;, testXSLT
(like any &xslt4c; application) automatically uses ICU
+ <p>If you have built and integrated the ICU with &xml4c;, Xalan and
testXSLT (like any &xslt4c; application) automatically uses ICU
support for output encoding. See <resource-ref
idref="xerces-build-icu"/>.</p>
- <p>The testXSLT executable also conditionally includes ICU support for
number formatting and sorting. Look in process.cpp for the
- <code>#if defined(XALAN_USE_ICU)</code> blocks. In these blocks,
process.cpp #includes the ICUBridge headers, and
+ <p>The Xalan and testXSLT executables also conditionally include ICU
support for number formatting and sorting. For Xalan, look in
XalanTransformer.cpp
+ for the <code>#if defined(XALAN_USE_ICU)</code> blocks. For testXSLT,
look in process.cpp for the
+ <code>#if defined(XALAN_USE_ICU)</code> blocks. These blocks #include
the ICUBridge headers, and
substitutes ICU support for xsl:number, format-number(), and xsl:sort.
To activate this support:</p>
<ol>
<li>Download and build the ICU (see <link idref="usagepatterns"
anchor="icu">Using the ICU</link>).<br/><br/></li>
- <li>Rebuild testXSLT with the ICU enabled (see below).</li>
+ <li>Rebuild Xalan and or testXSLT with the ICU enabled (see
below).</li>
</ol>
- <s3 title="Rebuilding TestXSLT in Windows">
+ <s3 title="Rebuilding Xalan and/or TestXSLT in Windows">
<ol>
- <li>Uncomment the <code>#define XALAN_USE_ICU</code> in
process.cpp.<br/><br/></li>
- <li>Add ICUBridge to the Visual C++ list of dependencies for the
TestXSLT project.<br/><br/></li>
- <li>Build TestXSLT.exe.</li>
+ <li>Uncomment the <code>#define XALAN_USE_ICU</code> in
XalanTransformer.cpp and/or process.cpp.<br/><br/></li>
+ <li>Add ICUBridge to the Visual C++ list of dependencies for the
XalanTransformer and/or TestXSLT project.<br/><br/></li>
+ <li>Build Xalan.exe and/or TestXSLT.exe.</li>
</ol>
</s3>
<s3 title="Rebuilding testXSLT in UNIX">
- <p>In the Linux, AIX, HP-UX 11, and Solaris builds, the ICUBridge is in
the core Xalan library (&xslt4c-linuxlib; in Linux; &xslt4c-aixlib; in
- AIX; &xslt4c-hplib; in HP-UX 11; &xslt4c-solarislib; in Solaris), so
you must rebuild this library along with testXSLT.</p>
+ <p>In the Linux, AIX, HP-UX 11, and Solaris builds &solarisbuild;, the
ICUBridge is in the core Xalan library (&xslt4c-linuxlib; in Linux;
&xslt4c-aixlib; in
+ AIX; &xslt4c-hplib; in HP-UX 11; &xslt4c-solarislib; lib; in Solaris ),
so you must rebuild this library along with Xalan and/or testXSLT.</p>
<p>Before you do the build, define the XALAN_USE_ICU environment
variable. For information about defining this
environment variable and doing a build, see <link idref="readme"
anchor="unix">Steps for doing a
UNIX build</link>.</p>
1.25 +3 -3 xml-xalan/c/xdocs/sources/xalan/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/faq.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- faq.xml 2001/08/27 19:45:22 1.24
+++ faq.xml 2001/12/20 13:57:15 1.25
@@ -66,7 +66,7 @@
<td>Yes</td>
</tr>
<tr>
- <td>Solaris 2.6</td>
+ <td>Solaris 2.6 &solarisbuild;</td>
<td>Workshop 4.2</td>
<td>Yes</td>
</tr>
@@ -102,8 +102,8 @@
<p>For more details see: <link idref="usagepatterns" anchor="icu">Using the
International Components for Unicode (ICU)</link>.</p><!--icuNote--><anchor
name="gnutar"/><p/></a>
</faq>
- <faq title="A tar checksum error on Solaris.">
- <q>I am getting a tar checksum error on Solaris. What's the
problem?</q>
+ <faq title="A tar checksum error on Solaris">
+ <q>I am getting a tar checksum error on Solaris &solarisbuild;. What's
the problem?</q>
<a>
<p>The Solaris tar utility you are using does not properly handle
files with long pathnames.
You must use GNU tar (gtar), which handles arbitrarily long
pathnames
1.28 +14 -14 xml-xalan/c/xdocs/sources/xalan/getstarted.xml
Index: getstarted.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/getstarted.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- getstarted.xml 2001/08/14 17:41:48 1.27
+++ getstarted.xml 2001/12/20 13:57:15 1.28
@@ -11,7 +11,7 @@
</ul>
<anchor name="download"/>
<s2 title="Downloading what you need">
-<p>For &xslt4c-current;, we are distributing a Windows32 Visual C++ build
and four UNIX builds with a makefile: a Red Hat Linux GNU build, an AIX xlC_r
build, an HP-UX 11 aCC build, and a Solaris build.
+<p>For &xslt4c-current;, we are distributing a Windows32 Visual C++ build
and four UNIX builds with a makefile: a Red Hat Linux GNU build, an AIX xlC_r
build, an HP-UX 11 aCC build, and a Solaris &solarisbuild; build.
Please contact us at <human-resource-ref idref="xalandev"/> if you would
like to help provide builds for other platforms.</p>
<anchor name="xalandists"/>
<s3 title="&xslt4c; Windows Distribution">
@@ -24,40 +24,40 @@
<p>For the Linux build, download <resource-ref
idref="xslt4c-linux-download"/>. This Red Hat Linux 6.1 distribution was built
with egcs-2.91.66 and glibc-2.1.2-11.</p>
<p>For the AIX build, download <resource-ref idref="xslt4c-aix-download"/>.
This AIX 4.3 distribution was built with IBM C and C++ for AIX 3.6.6.</p>
<p>For the HP-UX 11 build, download <resource-ref
idref="xslt4c-hp-ux-download"/>. This HP-UX 11 distribution was built with aCC
A.03.27.</p>
-<p>For the Solaris build, download <resource-ref
idref="xslt4c-solaris-download"/>. This Solaris distribution was built with
Workshop 4.2.</p>
-<note>Use GNU tar to untar the Solaris distribution file; see <link
idref="faq" anchor="gnutar">A tar checksum error on Solaris</link>.</note>
+<p>For the Solaris build, download <resource-ref
idref="xslt4c-Solaris-download"/>. This Solaris distribution was built with
Workshop 4.2.</p>
+<note>Use GNU tar to untar the Solaris distribution file; see <link
idref="faq" anchor="gnutar">A tar checksum error on Solaris </link>.</note>
<p>Each distribution contains all you need to run the Xalan command-line
transformations utility and to build your own applications.
If you want to take advantage of the support for number formatting, sorting,
and encoding the ICU provides, you should also download and install the
<resource-ref idref="icu"/>; see <link idref="usagepatterns" anchor="icu">Using
the ICU</link>,</p>
<s3 title="What you need to run the Xalan command-line utility">
<p>To run the Xalan executable for performing transformations, you need the
following:</p>
<p><em>Windows32</em></p>
<ul>
-<li>The executable: TestXSLT.exe</li>
+<li>The executable: Xalan.exe or TestXSLT.exe</li>
<li>The Xalan-C++ dynamic link libraries: &xslt4c-windlls;</li>
<li>The Xerces-C++ dynamic link library: &xml4c-windll;</li>
</ul>
<p><em>Linux</em></p>
<ul>
- <li>The executable: testXSLT</li>
+ <li>The executable: Xalan or testXSLT</li>
<li>The Xalan-C++ shared library: &xslt4c-linuxlib;</li>
<li>The Xerces-C++ shared library: &xml4c-linuxlib;</li>
</ul>
<p><em>AIX</em></p>
<ul>
- <li>The executable: testXSLT</li>
+ <li>The executable: Xalan or testXSLT</li>
<li>The Xalan-C++ load library: &xslt4c-aixlib;</li>
<li>The Xerces-C++ load library: &xml4c-aixlib;</li>
</ul>
<p><em>HP-UX 11</em></p>
<ul>
- <li>The executable: testXSLT</li>
+ <li>The executable: Xalan or testXSLT</li>
<li>The Xalan-C++ shared library: &xslt4c-hplib;</li>
<li>The Xerces-C++ shared library: &xml4c-hplib;</li>
</ul>
-<p><em>Solaris</em></p>
+<p><em>Solaris</em> &solarisbuild;</p>
<ul>
- <li>The executable: testXSLT</li>
+ <li>The executable: Xalan or testXSLT</li>
<li>The Xalan-C++ shared library: &xslt4c-solarislib;</li>
<li>The Xerces-C++ shared library: &xml4c-solarislib;</li>
</ul>
@@ -74,7 +74,7 @@
<p>In the Linux distribution (built with a make file and the GNU C++
compiler on Red Hat Linux 6.1), the shared object libraries are in the lib
subdirectories.</p>
<p>In the AIX distribution (built with the make file and xlC_r), the load
libraries are in the lib subdirectories.</p>
<p>In the HP-UX 11 distribution (built with the make file and aCC), the
shared libraries are in the lib subdirectories.</p>
-<p>In the Solaris distribution (built with the make file and CC), the shared
libraries are in the lib subdirectories.</p>
+<p>In the Solaris distribution &solarisbuild; (built with the make file and
CC), the shared libraries are in the lib subdirectories.</p>
<note>For your convenience, both the Xalan and Xerces libraries are placed
together in the pertinent xml-xalan directory, whereas the corresponding
xml-xerces directory only contains Xerces libraries.</note>
<p>If you want to enable ICU support in your applications, you must rebuild
the Xalan-C++ shared/load library (Linux/AIX) and include the ICUBridge headers
(all platforms).</p>
<p>For the requirements for rebuilding &xslt4c;, see the <link
idref="readme" anchor="build">Build notes</link>.</p>
@@ -85,7 +85,7 @@
<p>For the Xalan-C++ Linux distribution, place xml-xalan/c/bin on the path
(PATH) and xml-xalan/c/lib on the shared library path (LD_LIBRARY_PATH for Red
Hat Linux 6.1), or copy &xslt4c-linuxlib; to /usr/lib.</p>
<p>For the Xalan-C++ AIX distribution, place xml-xalan/c/bin on the path
(PATH) and xml-xalan/c/lib on the load library path (LIBPATH), or copy
&xslt4c-aixlib; to /usr/lib.</p>
<p>For the Xalan-C++ HP-UX 11 distribution, place xml-xalan/c/bin on the
path (PATH) and xml-xalan/c/lib on the shared library path (SHLIB_PATH), or
copy &xslt4c-aixlib; to /usr/lib.</p>
-<p>For the Xalan-C++ Solaris distribution, place xml-xalan/c/bin on the path
(PATH) and xml-xalan/c/lib on the shared library path (LD_LIBRARY_PATH), or
copy &xslt4c-solarislib; to /usr/lib.</p>
+<p>For the Xalan-C++ Solaris distribution &solarisbuild;, place
xml-xalan/c/bin on the path (PATH) and xml-xalan/c/lib on the shared library
path (LD_LIBRARY_PATH), or copy &xslt4c-solarislib; to /usr/lib.</p>
<p>If you do your own Xalan, ICU, and Xerces builds, be sure to include the
directories that contain the libraries and the TextXSLT executable on your
path.</p>
</s2><anchor name="samples"/>
<s2 title="Trying out the samples">
@@ -106,10 +106,10 @@
<s2 title="Performing your own transformations from the command line">
<p>TestXSLT provides a basic utility for performing transformations from the
command line. The command line for
most standard transformations is as follows:</p>
-<p><code>testXSLT -in <ref>xmlSource</ref> -xsl <ref>stylesheet</ref> -out
<ref>outputfile</ref></code></p>
+<p><code>Xalan -o <ref>outputfile</ref> <ref>xmlSource</ref>
<ref>stylesheet</ref></code></p>
<p>where <ref>xmlSource</ref> is the XML source file name,
<ref>stylesheet</ref> is the XSL stylesheet file name, and
<ref>outputfile</ref> is the output file name.</p>
-<p>If you want the output to be displayed on the screen, simply omit the
-out flag and outputfile.</p>
-<p>You can use this utility to try out XSL stylesheets you have written, to
make sure they do what you expect with the XML source files they are designed
to transform. The utility provides useful messages if the source file or
stylesheet is not well formed. If you include a DOCTYPE statement in your XML
source files and include the -validate flag on the command line, the utility
will also let you know whether the XML document is valid (conforms to that
DOCTYPE). For more information, see <link idref="commandline">Command-Line
Utility</link>.</p>
+<p>If you want the output to be displayed on the screen, simply omit the -o
flag and <ref>outputfile</ref>.</p>
+<p>You can use this utility to try out XSL stylesheets you have written, to
make sure they do what you expect with the XML source files they are designed
to transform. The utility provides useful messages if the source file or
stylesheet is not well formed. If you include a DOCTYPE statement in your XML
source files and include the -v flag on the command line, the utility will also
let you know whether the XML document is valid (conforms to that DOCTYPE). For
more information, see <link idref="commandline">Command-Line Utility</link>.</p>
</s2><anchor name="apps"/>
<s2 title="Setting up your own XSLT applications">
<p>You can start by using your own XML source files and XSL stylesheets with
the sample applications, which illustrate a number of usage patterns. For more
information on setting up applications, see <link idref="usagepatterns">Basic
Usage Patterns</link>.</p>
1.4 +12 -0 xml-xalan/c/xdocs/sources/xalan/history.xml
Index: history.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/history.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- history.xml 2001/08/09 20:10:36 1.3
+++ history.xml 2001/12/20 13:57:15 1.4
@@ -1,3 +1,15 @@
+ <s3 title="Changes for &xslt4c; version 1.2">
+ <p>Major updates since version 1.1 include:</p>
+ <ul>
+ <li><link idref="extensionslib">Introduction of a library of extension
functions</link></li>
+ <li>Support for pre-parsed source documents and pre-compiled
stylesheets in
+ <jump
href="apidocs/class_xalantransformer.html">XalanTransformer</jump> and the C
API.</li>
+ <li>Support for stylesheet params in <jump
href="apidocs/class_xalantransformer.html">XalanTransformer</jump>
+ and the C API</li>
+ <li>Support for extension functions in <jump
href="apidocs/class_xalantransformer.html">XalanTransformer</jump></li>
+ <li>Performance enhancements</li>
+ </ul>
+ </s3>
<s3 title="Changes for &xslt4c; version 1.1">
<p>In addition to adding to the list of platforms on which &xslt4c; builds,
our focus for this release has been on bug fixes, performance enhancements,
and providing a simplified C++ and C API for performing standard
transformations. Major updates since version 1.0 include:</p>
1.25 +3 -3 xml-xalan/c/xdocs/sources/xalan/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/index.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- index.xml 2001/08/09 20:10:36 1.24
+++ index.xml 2001/12/20 13:57:15 1.25
@@ -65,8 +65,8 @@
document types.</p>
<p>&xslt4c-current; is a robust implementation of the W3C
Recommendations
for XSL Transformations (XSLT) and the XML Path Language (XPath). It
includes a compatible release of the
- &xml4c; XML parser: &xml4c-used;. The focus for this release is on bug
fixes, performance enhancements, new
- samples, and a preliminary set of extension functions. For the details,
see the <link idref="readme">Release Notes</link>.</p>
+ &xml4c; XML parser: &xml4c-used;. The focus for this release is on bug
fixes, along with a new and simpler command-line executable,
+ two new samples and additional support for using a Xerces DOM as input
for a transformation. For the details, see the <link idref="readme">Release
Notes</link>.</p>
</s2>
<s2 title="How do I get it?">
@@ -101,7 +101,7 @@
</tr>
<tr>
<td>Solaris 2.6</td>
- <td><resource-ref idref="xslt4c-solaris-download"/>*<br/>
+ <td><resource-ref idref="xslt4c-Solaris-download"/>*<br/>
*Use GNU tar to untar; see <link idref="faq"
anchor="gnutar">FAQs</link></td>
<td>Workshop 4.2</td>
</tr>
1.31 +9 -11 xml-xalan/c/xdocs/sources/xalan/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/readme.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- readme.xml 2001/08/15 19:55:50 1.30
+++ readme.xml 2001/12/20 13:57:15 1.31
@@ -77,17 +77,15 @@
<li><link anchor="to-do">To-do tasks for future &xslt4c;
releases</link></li>
</ul>
<anchor name="done"/>
- <s3 title="Changes since &xslt4c; version 1.1">
- <p>Major updates since version 1.1 include:</p>
+ <s3 title="Changes since &xslt4c; version 1.2">
+ <p>Major updates since version 1.2 include:</p>
<ul>
- <li><link idref="extensionslib">Introduction of a library of extension
functions</link></li>
- <li>Support for pre-parsed source documents and pre-compiled
stylesheets in
- <jump
href="apidocs/class_xalantransformer.html">XalanTransformer</jump> and the C
API.</li>
- <li>Support for stylesheet params in <jump
href="apidocs/class_xalantransformer.html">XalanTransformer</jump>
- and the C API</li>
- <li>Support for extension functions in <jump
href="apidocs/class_xalantransformer.html">XalanTransformer</jump></li>
- <li>Performance enhancements</li>
+ <li>A new and simplified command-line utility: <link
idref="commandline" anchor="xalanexe">the Xalan executable</link></li>
+ <li>New XPath samples exploiting the XPathEvaluator C API and
illustrating serialization of an XPath result set: <link idref="samples"
anchor="simplexpathcapi">SimpleXPathCAPI</link> and <link idref="samples"
anchor="serializenodeset">SerializeNodeSet</link></li>
+ <li>A new <link idref="usagepatterns"
anchor="xercesdomwrapperparsedsource">wrapper class</link> that lets you pass
in a Xerces DOM as input for a transformation</li>
+<li>Bug fixes.</li>
</ul>
+ <note>&solarisbuild;</note>
</s3>
<anchor name="bugs"/>
<s3 title="Bug reporting">
@@ -160,7 +158,7 @@
<li>Set the XERCESCROOT environment variable to the root of
xml-xerces.<br/><br/></li>
<li>Set the XALANCROOT environment variable to the complete path to
the root of the &xslt4c;
distribution.<br/><br/></li>
- <li>AIX and Solaris only: Download <resource-ref idref="stlport"/> and
set the STLPORTROOT environment
+ <li>AIX and Solaris only &solarisbuild; : Download <resource-ref
idref="stlport"/> and set the STLPORTROOT environment
variable to the complete path to the STLPort distribution. <br/>
(This step is not required for Linux or HP-UX 11 because The Linux
GNU compiler and HP aCC compiler include the STL (Standard Template
Library.)<br/><br/></li>
@@ -178,7 +176,7 @@
<ref>Linux:</ref> <code>runConfigure -p linux</code><br/>
<ref>AIX:</ref> <code>runConfigure -p aix -c
xlc -x xlC</code><br/><br/>
<ref>HP-UX 11:</ref> <code>runConfigure -p hp-11 -c cc -x
aCC</code><br/><br/>
- <ref>Solaris:</ref> <code>runConfigure -p solaris -c cc -x
CC</code><br/><br/>
+ <ref>Solaris &solarisbuild;:</ref> <code>runConfigure -p
Solaris -c cc -x CC</code><br/><br/>
To see the other runConfigure flags you may include, use the help
flag:<br/><br/>
<code>runConfigure
-h</code><br/><br/></li>
<li>Purge the previous build:<br/><br/>
1.15 +2 -1 xml-xalan/c/xdocs/sources/xalan/resources.xml
Index: resources.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/resources.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- resources.xml 2001/08/14 17:41:48 1.14
+++ resources.xml 2001/12/20 13:57:15 1.15
@@ -23,7 +23,8 @@
<resource id="xslt4c-linux-download" title="&xslt4c-dist;-linux.tar.gz"
location="http://xml.apache.org/dist/xalan-c/&xslt4c-dist;-linux.tar.gz"/>
<resource id="xslt4c-aix-download" title="&xslt4c-dist;-aix.tar.gz"
location="http://xml.apache.org/dist/xalan-c/&xslt4c-dist;-aix.tar.gz"/>
<resource id="xslt4c-hp-ux-download" title="&xslt4c-dist;-hp-ux.tar.gz"
location="http://xml.apache.org/dist/xalan-c/&xslt4c-dist;-hp-ux.tar.gz"/>
-<resource id="xslt4c-solaris-download" title="&xslt4c-dist;-solaris.tar.gz"
location="http://xml.apache.org/dist/xalan-c/&xslt4c-dist;-solaris.tar.gz"/>
+<!--resource id="xslt4c-Solaris-download"
title="&xslt4c-dist;-solaris.tar.gz"
location="http://xml.apache.org/dist/xalan-c/&xslt4c-dist;-solaris.tar.gz"/-->
+<resource id="xslt4c-Solaris-download" title="&solarisbuild;"
location="NONE"/>
<resource id="icu" title="International Components for Unicode (ICU)"
location="http://oss.software.ibm.com/developerworks/opensource/icu/project/index.html"/>
<resource id="icu-download" title="International Components for Unicode
(ICU) 1.8.1 source files"
location="http://oss.software.ibm.com/developerworks/opensource/icu/project/download/index.html"/>
1.33 +26 -7 xml-xalan/c/xdocs/sources/xalan/samples.xml
Index: samples.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/samples.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- samples.xml 2001/08/21 18:12:56 1.32
+++ samples.xml 2001/12/20 13:57:15 1.33
@@ -70,7 +70,9 @@
<li><link anchor="documentbuilder">DocumentBuilder</link></li>
<li><link anchor="threadsafe">ThreadSafe</link></li>
<li><link anchor="xpathwrapper">XPathWrapper</link></li>
- <li><link anchor="simplexpathapi">SimpleXPathAPI</link></li>
+ <li><link anchor="simplexpathapi">SimpleXPathAPI</link></li>
+ <li><link anchor="simplexapthcapi">SimpleXPathCAPI</link></li>
+ <li><link anchor="serializenodeset">SerializeNodeSet</link></li>
<li><link anchor="externalfunctions">ExternalFunctions</link></li>
<li><link anchor="apachemodulexslt">ApacheModuleXSLT</link></li>
</ul>
@@ -227,14 +229,15 @@
<p>Run this sample from the SimpleXPathAPI subdirectory with</p>
<p><code>SimpleXPathAPI <ref>XMLFile</ref> <ref>ContextNode</ref>
<ref>XPathExpression</ref></code></p>
<p>where <ref>XMLFile</ref> is an XML source file, <ref>ContextNode</ref>
is the location path to the context
- node, and <ref>XPathExpression</ref> is an XPath expression to apply to
that context node. The XPathWrapper
- subdirectory contains an XML file named xml.foo (part of it appears
below).</p>
+ node, and <ref>XPathExpression</ref> is an XPath expression to apply to
that context node.</p>
+<note>Keep in mind that the string value returned by an XPath expression is
the string value of the first node in the nodeset returned by the
expresssion.</note>
+<p>The XPathWrapper subdirectory contains an XML file named xml.foo (part of
it appears below).</p>
<source><?xml version="1.0"?>
<doc>
- <name first="David" last="Marston"/>
- <name first="David" last="Bertoni"/>
+ <name first="David" last="Marston">Mr. Marson</name>
+ <name first="David" last="Bertoni">Mr. Bertoni</name>
...
- <name first="Paul" last="Dick"/>
+ <name first="Paul" last="Dick">Mr. Dick</name>
</doc></source>
<p>You can try command lines like</p>
<p><code>SimpleXPathAPI foo.xml /doc name/@last</code></p>
@@ -242,7 +245,23 @@
<p><code>SimpleXPathAPI foo.xml /
'//name[position()="4"]/@first'</code></p>
<note>If a SimpleXPathAPI argument includes characters (such as *) that
the shell interprets incorrectly, enclose the argument
in double quotes.</note>
- <p>See also: <link idref="usagepatterns" anchor="xpath">Working with
XPath expressions</link>.</p>
+ <p>See also: <link idref="usagepatterns" anchor="xpath">Working with
XPath expressions</link>.</p>
+ </s2><anchor name="simplexpathcapi"/>
+ <s2 title="SimpleXPathCAPI">
+ <p>What it does: Use the XPathEvaluator C interface to evaluate an XPath
epxeression and display the string value returned by the epxression.</p>
+<note>Keep in mind that the string value returned by an XPath expression is
the string value of the first node in the nodeset returned by the
epxresssion.</note>
+<p>Run this sample from the SimpleXPathCAPI subdirectory with</p>
+<p><code>SimpleXPathCAPI <ref>XMLFile</ref>
<ref>XPathExpression</ref></code></p>
+<p>where <ref>XMLFile</ref> is an XML source file, and
<ref>XPathExpression</ref> is an XPath expression to apply to the XML source
file. The SimpleXPathCAPI subdirectory contains an XML file named xml.foo
identical to foo.xml in the preceding example.</p>
+ <p>You can try command lines like</p>
+ <p><code>SimpleXPathCAPI foo.xml /doc/name[3]</code></p>
+ </s2><anchor name="serializenodeset"/>
+ <s2 title="SerializeNodeSet">
+ <p>What it does: Serialize the node set returned by the application of an
XPath expression to an XML document.</p>
+<p>Run this sample from the SerializeNodeSet subdirectory with</p>
+<p><code>SerializeNodeSet <ref>XMLFile</ref> <ref>ContextNode</ref>
<ref>XPathExpression</ref></code></p>
+ <p>where <ref>XMLFile</ref> is an XML source file, <ref>ContextNode</ref>
is the location path to the context
+ node, and <ref>XPathExpression</ref> is an XPath expression to apply to
that context node. The SerializeNodeSet directory contains the same foo.xml
sample source file as the preceding examples.</p>
</s2><anchor name="externalfunctions"/>
<s2 title="ExternalFunctions">
<p>What it does: implement, install, and illustrate the usage of three
extension functions. The functions return a
1.31 +41 -1 xml-xalan/c/xdocs/sources/xalan/usagepatterns.xml
Index: usagepatterns.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/usagepatterns.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- usagepatterns.xml 2001/08/21 18:12:56 1.30
+++ usagepatterns.xml 2001/12/20 13:57:15 1.31
@@ -65,6 +65,7 @@
<li><link anchor="incremental">Processing output incrementally</link></li>
<li><link anchor="compiled">Performing a series of
transformations</link></li>
<li><link anchor="dom">Working with DOM input and output</link></li>
+<li><link anchor="xercesdomwrapperparsedsource">Using a Xerces DOM as the
source for a Xalan transformation</link></li>
<li><link anchor="xpath">Working with XPath expressions</link></li>
<li><link anchor="tracelistener">Using the TraceListener</link></li>
<li><link anchor="icu">Using the International Components for Unicode
(ICU)</link></li>
@@ -224,11 +225,50 @@
// the output.
// You can also convert the XalanDocument to a Xerces DOM_Document.
DOM_Document domOut = theParserLiaison.mapXercesDocument(docOut)</source>
+<p>If you want to use a Xerces DOM object as input for a transformation
without wrapping the DOM in
+a XercesParserLiaison, see <link
anchor="xercesdomwrapperparsedsource">passing in a Xerces DOM</link>.</p>
<s3 title="Limitations">
<p>Performance is much better when &xslt4c; uses native source tree handling
rather than interacting with the Xerces DOMParser.</p>
<p>By default, the Xerces DOMParser creates a DOM_XMLDecNode in the DOM tree
to represent the XML declaration. The
Xalan bridge for the Xerces DOM does not support this non-standard node
type. Accordingly, you must call DOMParser::setToCreateXMLDeclTypeNode(false)
<em>before</em> you parse the XML file. If not, the behavior is undefined, and
your application may crash.</p>
+</s3><anchor name="xercesdomwrapperparsedsource"/>
+<s3 title="Passing in a Xerces DOM to a transformation">
+<p>You may want to use a Xerces DOM that was created without using the
XalanTransformer class. As the following code snippet illustrates, you can use
XercesDOMWrapperParsedSource to pass in a Xerces DOM as the source for an XSL
transformation.</p>
+<source>#include <parsers/DOMParser.hpp>
+#include <XalanTransformer/XercesDOMWrapperParsedSource.hpp>
+
+void parseWithXerces(XalanTransformer &xalan,
+ const XSLTInputSource &xmlInput,
+ const XalanCompiledStylesheet* styleSheer,
+ const XSLTResultTarget &output,
+ XMLFileReporter &logFile)
+{
+ DOMParser the Parser;
+ theParser.setToCreateXMLDeclTypeNode(false);
+ theParser.setDoValidation(true);
+ theParser.setDoNamespaces(true);
+
+ theParser.parse(xmlInput);
+ DOM_Document theDOM = theParser.getDocument();
+ theDOM.normalize();
+ XercesDOMSupport theDOMSupport;
+ XercdesParserLiaison theParserLiaison(theDOMSupport);
+ try
+ {
+ const XercesDOMWrapperParsedSource parsedSource(
+ theDOM,
+ theParserLiaison,
+ theDOMSupport,
+ XalanDOMString(xmlInput.getSystemId()));
+ xalan.transform(parsedSource, stylesheet, output);
+ }
+ catch (....)
+ {
+ ...
+ }
+}
+ </source>
</s3>
</s2><anchor name="xpath"/>
<s2 title="Working with XPath expressions">
@@ -308,7 +348,7 @@
path (LIBPATH) or copy it to /usr/lib.</p>
<p>For HP-UX 11, rebuild &xslt4c-hplib; with XALAN_USE_ICU defined, and
place it on the shared library
path (SHLIB_PATH) or copy it to /usr/lib.</p>
- <p>For Solaris, rebuild &xslt4c-solarislib; with XALAN_USE_ICU defined,
and place it on the shared library
+ <p>For Solaris &solarisbuild;, rebuild &xslt4c-solarislib; with
XALAN_USE_ICU defined, and place it on the shared library
path (LD_LIBRARY_PATH) or copy it to /usr/lib.</p>
<p><em>Number formatting</em></p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
