dleslie 00/06/27 09:46:29
Modified: c/xdocs/sources/xalan STATUS commandline.xml extensions.xml
faq.xml getstarted.xml index.xml readme.xml
resources.xml samples.xml usagepatterns.xml
xalan-cdist.gif
Log:
no message
Revision Changes Path
1.5 +18 -0 xml-xalan/c/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/STATUS,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- STATUS 2000/06/02 18:40:33 1.4
+++ STATUS 2000/06/27 16:46:16 1.5
@@ -1,3 +1,14 @@
+<<<<<<< STATUS
+<s3 title="Version of Xerces-C++ to use">
+<p>&xslt4c-current; has been tested with &xml4c-used;. The &xslt4c-current;
Windows32 download includes xerces-c_1_1.dll. The &xslt4c-current; Linux
download includes libxerces-c_1_1.so.
+
+For information about including The Xerces-C++ dynamic link or shared object
library on the path, see <link idref="getstarted" anchor="path">Setting up the
system 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>
+
+</s3><anchor name="to-do"/>
+<s3 title="To-do tasks for future &xslt4c; releases">
+ <p>To complete our implementation of the <resource-ref idref="XSLT"/>, we
must add support for</p>
+=======
<s3 title="Version of Xerces to use">
<p>The &xslt4c-current; has been tested with &xml4c-used;. The
&xslt4c-current; Windows32 download includes xerces-c_1_1.dll. The
&xslt4c-current; Linux download includes libxerces-c_1_1.so.
@@ -7,13 +18,20 @@
</s3><anchor name="to-do"/>
<s3 title="To-do tasks for future &xslt4c; releases">
<p>To complete our implementation of the <resource-ref idref="XSLT"/>, we
must add support for</p>
+>>>>>>> 1.4
<ul>
<li>The fallback element<br/><br/></li>
<li>The exclude-result-prefixes attribute<br/><br/></li>
<li>The output encoding attribute<br/><br/></li>
<li>Extension elements<br/><br/></li>
</ul>
+<<<<<<< STATUS
+ <p>The XSLT specification makes no such requirement, but we plan to
implement a more efficient mechanism for storing and
+ navigating DOM trees, along the lines of the &xslt4j; Document Table
Model (DTM)</p>
+ <p>Watch the <human-resource-ref idref="xalandev"/> for more information
and for ideas about how you can get involved.</p>
+=======
<p>The XSLT specification makes no such requirement, but we plan to
implement a more efficient mechanism for storing and
navigating DOM trees, along the lines of the Xalan-J Document Table
Model (DTM)</p>
<p>Watch the <human-resource-ref idref="xalandev"/> for more information
and for ideas about how you can get involved.</p>
+>>>>>>> 1.4
</s3>
1.4 +1 -1 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.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- commandline.xml 2000/06/02 18:40:33 1.3
+++ commandline.xml 2000/06/27 16:46:16 1.4
@@ -59,7 +59,7 @@
-->
-<s1 title="Xalan-C Command-Line Utility">
+<s1 title="&xslt4c; Command-Line Utility">
<s2 title="Using the Command-Line Utility">
<p>To perform a transformation, you can call &xslt4c; from the command
line (or script),
1.3 +4 -4 xml-xalan/c/xdocs/sources/xalan/extensions.xml
Index: extensions.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/extensions.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- extensions.xml 2000/06/02 18:40:34 1.2
+++ extensions.xml 2000/06/27 16:46:17 1.3
@@ -65,7 +65,7 @@
<li><link anchor="use">Using an extension function</link></li>
</ul><anchor name="intro"/>
<s2 title="Introduction">
-<p>At times, you may want to call your own custom C++ functions from a
stylesheet. For these situations, &xslt4c; supports the creation and use of
extension functions.</p>
+<p>At times, you may want to call your own custom C functions from a
stylesheet. For these situations, &xslt4c; supports the creation and use of
extension functions.</p>
<p>You can think of extension functions as extending the core library of
functions that XPath provides. Like the
XPath functions, an extension function returns an XObject, which may contain
a value of any of the five XSLT
data types: node-set, result-tree-fragment, string, boolean, or number.</p>
@@ -163,12 +163,12 @@
<note>These XSLTProcessorEnvSupportDefault methods call
XPathEnvSupportDefault methods of the same name which provide
the actual implementation.</note>
<p>When you install an extension function, the function inhabits the
namespace you designate. For information about XML namespaces, see <jump
href="http://www.w3.org/TR/REC-xml-names/";>Namespaces in XML</jump>.</p>
-<p>The following code fragment installs the square root function defined
above as a global function, and binds it to the extension-function name
"square-root" in the namespace
"http://ExternalFunction.xalan-c++.xml.apache.org"; so it can be accessed from
stylesheets. Keep in mind that the function name does not need to be the same
as the name of the function class, and that a function name may be used more
than once provided that each function with that name is installed in a
different namespace.</p>
+<p>The following code fragment installs the square root function defined
above as a global function, and binds it to the extension-function name
"square-root" in the namespace "http://ExternalFunction.xalan-c.xml.apache.org";
so it can be accessed from stylesheets. Keep in mind that the function name
does not need to be the same as the name of the function class, and that a
function name may be used more than once provided that each function with that
name is installed in a different namespace.</p>
<source>// You have created a header file for FunctionSquareRoot.
#include <MyFunctions/FunctionSquareRoot.hpp>
// The namespace...
const XalanDOMString
- theNamespace("http://ExternalFunction.xalan-c++.xml.apache.org";);
+ theNamespace("http://ExternalFunction.xalan-c.xml.apache.org";);
// Install the function in the global space so all processor
// instances can use it.
XSLTProcessorEnvSupportDefault::installExternalFunctionGlobal(
@@ -204,7 +204,7 @@
<source><?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
version="1.0"
- xmlns:external="http://ExternalFunction.xalan-c++.xml.apache.org";
+ xmlns:external="http://ExternalFunction.xalan-c.xml.apache.org";
exclude-result-prefixes="external">
<xsl:template match="//area">
1.4 +1 -1 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.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq.xml 2000/06/02 18:40:34 1.3
+++ faq.xml 2000/06/27 16:46:17 1.4
@@ -18,7 +18,7 @@
<faq title="Which version of Xerces should I be using?">
<q>Which version of Xerces should I be using?</q>
- <a><p>The &xslt4c; release notes includes information about the Xerces-C
release with which the &xslt4c; release has been coordinated and tested. See
<link idref="readme" anchor="status">Status</link></p></a>
+ <a><p>The &xslt4c; release notes includes information about the &xml4c;
release with which the &xslt4c; release has been coordinated and tested. See
<link idref="readme" anchor="status">Status</link></p></a>
</faq>
<faq title="Are the XSLTEngineImpl (XSLT processor) and StylesheetRoot
(compiled stylesheet) objects thread-safe?">
1.6 +12 -12 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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- getstarted.xml 2000/06/02 19:41:52 1.5
+++ getstarted.xml 2000/06/27 16:46:17 1.6
@@ -15,17 +15,17 @@
<s3 title="&xslt4c; Distributions">
<p><img src="xalan-cdist.gif" alt="xalan-cdist.gif"/></p>
</s3>
-<p>For the Windows32 build, download <resource-ref
idref="xalan-c-win32-download"/>.</p>
-<p>For the Linux build, download <resource-ref
idref="xalan-c-linux-download"/></p>
-<p>Each distribution contains all you need to run the Xalan command-line
utility for performing transformations. To build your own applications, you
also need a compatible Xerces-C distribution and the <resource-ref
idref="icu"/>.</p>
+<p>For the Windows32 build, download <resource-ref
idref="xslt4c-win32-download"/>.</p>
+<p>For the Linux build, download <resource-ref
idref="xslt4c-linux-download"/></p>
+<p>Each distribution contains all you need to run the Xalan command-line
utility for performing transformations. To build your own applications, you
also need a compatible Xerces-C++ distribution and the <resource-ref
idref="icu"/>.</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 Xalan-C dynamic link libraries: DOMSupport.dll, PlatformSupport.dll,
XalanDOM.dll, XercesParserLiaison.dll,
+<li>The Xalan-C++ dynamic link libraries: DOMSupport.dll,
PlatformSupport.dll, XalanDOM.dll, XercesParserLiaison.dll,
XercesPlatformSupport.dll, XMLSupport.dll, XPath.dll, XSLT.dll</li>
-<li>The Xerces-C dynamic link library: xerces-c_1_1.dll</li>
+<li>The Xerces-C++ dynamic link library: xerces-C_1_1.dll</li>
<li>The International Components for Unicode (ICU) dynamic link libraries:
icui18n.dll, icuuc.dll</li>
<li>The ICU locale data files</li>
</ul>
@@ -33,8 +33,8 @@
<p><em>Linux</em></p>
<ul>
<li>The utility: TestXSLT</li>
- <li>The Xalan-C shared library: libxalan-C_0_40_0.so</li>
- <li>The Xerces-C shared library: libxerces-c1_0.so</li>
+ <li>The Xalan-C++ shared library: libxalan-c_0_40_0.so</li>
+ <li>The Xerces-C++ shared library: libxerces-c1_2.so</li>
<li>The International Components for Unicode (ICU) shared library:
libicu-1_4_1_2.so</li>
<li>The ICU locale data files</li>
</ul>
@@ -43,17 +43,17 @@
</s3>
<s3 title="What you need to build applications">
<p>To build your own applications with Xalan and Xerces, you also need need
the
-Xalan-C and Xerces-C header (.hpp) files and (for Windows) the Xerces-C
libraries (.lib files).</p>
-<p>The Xalan-C header files are in the src directory tree in both
distributions.</p>
+Xalan-C++ and Xerces-C++ header (.hpp) files and (for Windows) the
Xerces-C++ libraries (.lib files).</p>
+<p>The Xalan-C++ header files are in the src directory tree in both
distributions.</p>
<p>In the Windows32 distribution (built with Microsoft® Visual C++®
6.0), the dlls and libraries are in the Build - Win32 -V6 - Release
subdirectory.</p>
<p>In the Linux distribution (built with a make file and Red Hat Linux 6.1),
the shared object library is in the lib subdirectory.</p>
-<p>To get the Xerces-C header and (for Windows) .lib files, download and
expand the Xerces-C 1.1.0 Binary distribution for your platform from the
<resource-ref idref="xerces-c-dist"/>. For information about which Xerces-C
distribution has been tested with this Xalan-C release, see <link
idref="readme" anchor="status">Version of Xerces to use</link>.</p>
+<p>To get the Xerces-C++ header and (for Windows) .lib files, download and
expand the &xml4c; binary distribution for your platform from the <resource-ref
idref="xml4c-distdir"/>. For information about which &xml4c; distribution has
been tested with this &xslt4c; release, see <link idref="readme"
anchor="status">Version of &xml4c; to use</link>.</p>
<p>For information about rebuilding &xslt4c;, see the <link idref="readme"
anchor="build">Build notes</link>.</p>
</s3>
</s2><anchor name="path"/>
<s2 title="Setting up the path">
-<p>For the Xalan-C Windows32 distribution, place
xml-xalan\c\Build\Win32\VC6\Release on the path.</p>
-<p>For the Xalan-C Linux distribution, place xml-xalan/c/bin and
xml-xalan/c/lib on the shared library path (LD_LIBRARY_PATH for Red Hat Linux
6.1).</p>
+<p>For the Xalan-C++ Windows32 distribution, place
xml-xalan\c\Build\Win32\VC6\Release on the path.</p>
+<p>For the Xalan-C++ Linux distribution, place xml-xalan/c/bin and
xml-xalan/c/lib on the shared library path (LD_LIBRARY_PATH for Red Hat Linux
6.1).</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">
1.5 +9 -9 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.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- index.xml 2000/06/02 19:41:52 1.4
+++ index.xml 2000/06/27 16:46:17 1.5
@@ -77,27 +77,27 @@
</tr>
<tr>
<td>Windows32</td>
- <td><resource-ref idref="xalan-c-win32-download"/></td>
+ <td><resource-ref idref="xslt4c-win32-download"/></td>
</tr>
<tr>
<td>Linux</td>
- <td><resource-ref idref="xalan-c-linux-download"/></td>
+ <td><resource-ref idref="xslt4c-linux-download"/></td>
</tr>
</table>
<p>We plan to add builds for other platforms as soon as possible.
Volunteers are more than welcome!</p>
</s2>
<s2 title="Where do I get Xerces?">
- <p>Both distributions include the Xerces runtime environment for Xalan
-- xerces-c_1_1.dll for Windows,
- and libxerces-c_1_1.so for Linux. To build applications with Xalan and
Xerces, you also need the &xml4c;
+ <p>Both distributions include the Xerces runtime environment for Xalan
-- xerces-c_1_2.dll for Windows,
+ and libxerces-c_1_2.so for Linux. To build applications with Xalan and
Xerces, you also need the &xml4c;
binary distribution for your platform, which you can download from the
- <resource-ref idref="Xerces-c-dist"/>.</p>
- <note>Be sure you are using a compatible Xerces-C build. For
information about the build with which this release
- of Xalan-C was tested, see <link idref="readme" anchor="status">Version
of Xerces to use</link>.</note>
+ <resource-ref idref="xml4c-distdir"/>.</p>
+ <note>Be sure you are using a compatible Xerces-C++ build. For
information about the build with which this release
+ of Xalan-C++ was tested, see <link idref="readme"
anchor="status">Version of Xerces to use</link>.</note>
</s2>
<s2 title="For more information...">
- <p>For more information, go to the <link idref="overview">Xalan-C
Overview</link> and
- <link idref="getstarted">Getting Started with Xalan-C</link>. All of the
Xalan documentation on this website is
+ <p>For more information, go to the <link idref="overview">Xalan-C++
Overview</link> and
+ <link idref="getstarted">Getting Started with Xalan-C++</link>. All of
the Xalan documentation on this website is
included in the Xalan downloads, as are a number of samples to help you
start using Xalan to transform XML
documents.</p>
</s2>
1.6 +8 -8 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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- readme.xml 2000/06/02 19:41:53 1.5
+++ readme.xml 2000/06/27 16:46:17 1.6
@@ -1,8 +1,8 @@
<?xml version="1.0" standalone="no"?>
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd"[
-<!ENTITY done-c SYSTEM "DONE">
-<!ENTITY status-c SYSTEM "STATUS">
-<!ENTITY bugs-c SYSTEM "BUGS">]>
+<!ENTITY done-C++ SYSTEM "DONE">
+<!ENTITY status-C++ SYSTEM "STATUS">
+<!ENTITY bugs-C++ SYSTEM "BUGS">]>
<!--
* The Apache Software License, Version 1.1
@@ -60,7 +60,7 @@
* information on the Apache Software Foundation, please see
* <http://www.apache.org/>.
-->
-<s1 title="Xalan-C++ Release Notes">
+<s1 title="&xslt4c; Release Notes">
<p>Release notes for &xslt4c-current;</p>
<ul>
<li><link anchor="status">Status</link></li>
@@ -70,7 +70,7 @@
<s2 title="Status">
<ul>
<li><link anchor="bugs">Bug reporting</link></li>
- <li><link anchor="status">Version of Xerces-C to use</link></li>
+ <li><link anchor="status">Version of &xml4c; to use</link></li>
</ul>
<anchor name="bugs"/>
&bugs-c;
@@ -101,12 +101,12 @@
<p>To rebuild the Windows32 release, use the Microsoft Visual C++ 6.0
project files. To rebuild the Linux release, use the make
file in the root of the source directory. Both builds look for &xml4c;
and ICU in directories parallel to the xml-xalan
directory</p>
- <p><em>Important</em> We have set up the Visual C++ projects and the
Linux make file to look for Xerces in a directory structure that results from
downloading xml-xerces/c from the <jump
href="http://xml.apache.org/websrc/cvsweb.cgi/";>Apache XML CVS
repository</jump> and building with the Visual C++ project files or the Linux
make file. This structure parallels the Xalan-C source tree and build
structure.<br/><br/>
-If you are using a Xerces-C binary distribution, you must either modify the
Xalan-C project files or makefile, or rearrange the build directory structure,
and you must also get the header files from the Xerces-C source distribution,
since Xalan-C uses a header file that is not included in the Xerces-C binary
distribution.</p>
+ <p><em>Important</em> We have set up the Visual C++ projects and the
Linux make file to look for Xerces in a directory structure that results from
downloading xml-xerces/c from the <jump
href="http://xml.apache.org/websrc/cvsweb.cgi/";>Apache XML CVS
repository</jump> and building with the Visual C++ project files or the Linux
make file. This structure parallels the &xslt4c; source tree and build
structure.<br/><br/>
+If you are using a &xml4c; binary distribution, you must either modify the
&xslt4c; project files or makefile, or rearrange the build directory structure,
and you must also get the header files from the &xml4c; source distribution,
since &xslt4c; uses a header file that is not included in the &xml4c; binary
distribution.</p>
<s4 title="&xml4c; and ICU layout for &xslt4c; build">
<p><img src="xerces-icu.gif" alt="xerces-icu.gif"/></p>
</s4>
-<note>Keep in mind that at any given point in time the Xalan-C and Xerces-C
source trees in the Apache XML repository may not be consistent. When we
release a version of Xerces-C we certify that it is compabible with a given
release of Xalan-C. To be safe, stick with distributions that we certify to be
compatible. Reminder: &xslt4c-current; is compatible with
&xml4c-used;.<br/><br/>
+<note>Keep in mind that at any given point in time the &xslt4c; and &xml4c;
source trees in the Apache XML repository may not be consistent. When we
release a version of &xml4c; we certify that it is compabible with a given
release of &xslt4c;. To be safe, stick with distributions that we certify to be
compatible. Reminder: &xslt4c-current; is compatible with
&xml4c-used;.<br/><br/>
&xslt4c-current; was built with the &icu-used;. You can probably use newer
ICU releases as they appear.</note>
</s3><anchor name="samples"/>
<s3 title="Rebuilding a sample application">
1.3 +6 -6 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.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- resources.xml 2000/06/02 18:40:36 1.2
+++ resources.xml 2000/06/27 16:46:18 1.3
@@ -13,13 +13,13 @@
]>
<resources>
- <resource id="xalan-c-current" title="Xalan-C++ Version 0.40.0 XSLT
Processor" location="http://xml.apache.org/xalan"/>
- <resource id="xerces-c-used" title="Xerces-C++ Version 1.2.0"
location="http://xml.apache.org/xerces-c/index.html"/>
+ <resource id="xslt4c-current" title="&xslt4c-current"
location="http://xml.apache.org/xalan"/>
+ <resource id="xml4c-used" title="&xml4c-used;"
location="http://xml.apache.org/xerces-c/index.html"/>
- <resource id="xalan-c-dist" title="Xalan-C++ distribution directory"
location="http://xml.apache.org/dist/"/>
- <resource id="xerces-c-dist" title="Xerces-C++ distribution directory"
location="http://xml.apache.org/dist/xerces-c/"/>
- <resource id="xalan-c-win32-download" title="Xalan-C_0_40_0-win32.zip"
location="http://xml.apache.org/dist/Xalan-C_0_40_0-win32.zip"/>
- <resource id="xalan-c-linux-download" title="Xalan-C_40_0-linux.tar.gz"
location="http://xml.apache.org/dist/Xalan-C_0_40_0-linux.tar.gz"/>
+ <resource id="xslt4c-distdir" title="&xslt4c; distribution directory"
location="http://xml.apache.org/dist/xalan-c"/>
+ <resource id="xml4c-distdir" title="&xml4c; distribution directory"
location="http://xml.apache.org/dist/xerces-c/"/>
+ <resource id="xslt4c-win32-download" title="&xslt4c-dist;-win32.zip"
location="http://xml.apache.org/dist/xerces-c/&xslt4c-dist;-win32.zip"/>
+ <resource id="xslt4c-linux-download" title="&xslt4c-dist;-linux.tar.gz"
location="http://xml.apache.org/dist/xerces-c/&xslt4c-dist;-linux.tar.gz"/>
<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.4.1.2 source files"
location="http://oss.software.ibm.com/developerworks/opensource/icu/project/download/index.html"/>
1.5 +1 -1 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.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- samples.xml 2000/06/05 20:04:52 1.4
+++ samples.xml 2000/06/27 16:46:18 1.5
@@ -57,7 +57,7 @@
-->
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
-<s1 title="Xalan-C Samples">
+<s1 title="&xslt4c; Samples">
<ul>
<li><link anchor="getstarted">Samples to help you get started</link></li>
<li><link anchor="simpletransform">SimpleTransform</link></li>
1.4 +4 -4 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.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- usagepatterns.xml 2000/06/02 18:40:36 1.3
+++ usagepatterns.xml 2000/06/27 16:46:18 1.4
@@ -56,7 +56,7 @@
* information on the Apache Software Foundation, please see
* <http://www.apache.org/>.
-->
-<s1 title="Xalan-C Basic usage patterns">
+<s1 title="&xslt4c; Basic usage patterns">
<ul>
<li><link anchor="intro">Introduction</link></li>
<li><link anchor="basic">Basic procedure for performing XSL
transformations</link></li>
@@ -73,16 +73,16 @@
<p>&xslt4c; takes as primary input an XML source document and an XSL
stylesheet, both represented by instances of <jump
href="apidocs/class_XSLTInputSource.html">XSLTInputSource</jump>. These input
objects may each take the form of a file or URL, a stream, or a DOM tree. The
stylesheet may also take the form of a compiled stylesheet (an instance of
<jump href="apidocs/class_stylesheetroot.html">StylesheetRoot</jump>.</p>
<note>If the XML source document contains a stylesheet Processing
Instruction (PI), &xslt4c; uses the stylesheet this PI points to and a separate
stylesheet object is not required. </note>
<p>&xslt4c; uses &xml4c; to parse text input, performs the transformation,
and sends the output to an instance of <jump
href="apidocs/class_xsltresulttarget.html">XSLTResultTarget</jump>, which may
be configured to write to a file, a stream, or a DOM tree.</p>
-<p>For detailed API documentation, see <jump href="apidocs/index.html">Xalan
C++ API</jump>. For an overview of the
+<p>For detailed API documentation, see <jump
href="apidocs/index.html">&xslt4c; API</jump>. For an overview of the
command-line utility, see <link idref="commandline">Command-Line
Utility</link>.</p>
</s2><anchor name="basic"/>
<s2 title="Basic procedure for performing an XSL transformation">
<p>When you are setting up your application to use XSL stylesheets to
transform XML documents, you must do the following:</p>
<s3 title="1. Include the required header files">
-<p>Along with any required Xalan-C and other header files, include
utils/PlatformUtils.hpp from the Xerces-C distribution.</p>
+<p>Along with any required &xslt4c; and other header files, include
utils/PlatformUtils.hpp from the &xml4c; distribution.</p>
</s3>
<s3 title="2. Initialize Xalan and Xerces">
-<p>Use the static initializers to initialize the Xalan-C and Xerces-C
platforms. You only need to do this once per session.</p>
+<p>Use the static initializers to initialize the &xslt4c; and &xml4c;
platforms. You only need to do this once per session.</p>
<source>XMLPlatformUtils::Initialize();
XSLTEngineImpl::Initialize();</source>
</s3><anchor name="step3"/>
1.2 +13 -14 xml-xalan/c/xdocs/sources/xalan/xalan-cdist.gif
<<Binary file>>
