You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by dl...@locus.apache.org on 2000/09/12 15:35:14 UTC
cvs commit: xml-xalan/c/xdocs/sources/xalan BUGS commandline.xml extensions.xml getstarted.xml overview.xml readme.xml samples.xml usagepatterns.xml
dleslie 00/09/12 06:35:14
Modified: c/xdocs/sources entities.ent xalan.xml
c/xdocs/sources/xalan BUGS commandline.xml extensions.xml
getstarted.xml overview.xml readme.xml samples.xml
usagepatterns.xml
Log:
Updater per 1.0 review.
Revision Changes Path
1.7 +8 -6 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.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- entities.ent 2000/09/01 19:23:08 1.6
+++ entities.ent 2000/09/12 13:35:09 1.7
@@ -7,17 +7,19 @@
<!ENTITY xslt4c-linuxlib "libxalan-c1_0.so">
<!ENTITY xslt4c-aixlib "libxalan-c1_0.a">
<!ENTITY xml4c "Xerces-C++">
-<!ENTITY xml4c-used "Xerces-C++ version 1.2.0a">
-<!ENTITY xml4c-windll "xerces-c_1_2.dll">
+<!ENTITY xml4c-used "Xerces-C++ version 1.3.0">
+<!ENTITY xml4c-windll "xerces-c_1_3.dll">
<!ENTITY xml4c-winlib "xerces-c_1.lib">
-<!ENTITY xml4c-linuxlib "libxerces-c1_2.so">
-<!ENTITY xml4c-aixlib "libxerces-c1_2.a">
+<!ENTITY xml4c-linuxlib "libxerces-c1_3.so">
+<!ENTITY xml4c-aixlib "libxerces-c1_3.a">
<!ENTITY xslt4j "Xalan-Java">
<!ENTITY icu-used "International Components for Unicode(ICU) 1.6 source files">
<!ENTITY icu-windlls "icui18n.dll, icuuc.dll">
<!ENTITY icu-unixlib "libicu-1_6.so">
<!ENTITY icu-aixlib "libicu-1_6.a">
+<!ENTITY icubridge-win "ICUBridge.dll">
+<!ENTITY icubridge-linux "ICUBridge.so">
+<!ENTITY icubridge-aix "ICUBridge.a">
<!ENTITY done SYSTEM "sbk:/sources/xalan/DONE">
<!ENTITY status SYSTEM "sbk:/sources/xalan/STATUS">
-<!ENTITY bugs SYSTEM "sbk:/sources/xalan/BUGS">
-
+<!ENTITY bugs SYSTEM "sbk:/sources/xalan/BUGS">
\ No newline at end of file
1.5 +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.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- xalan.xml 2000/09/01 19:23:10 1.4
+++ xalan.xml 2000/09/12 13:35:09 1.5
@@ -106,7 +106,7 @@
<separator/>
- <external href="http://xml.apache.org/xalan/c-apidocs/index.html"
+ <external href="apidocs/index.html"
label="C++ API"/>
<separator/>
1.3 +1 -1 xml-xalan/c/xdocs/sources/xalan/BUGS
Index: BUGS
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/BUGS,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- BUGS 2000/06/02 18:40:33 1.2
+++ BUGS 2000/09/12 13:35:10 1.3
@@ -2,5 +2,5 @@
<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>
<note>If the Apache XML Bug Tracking System is not working, please report the bug to the
- <human-resource-ref idref="xalandev"/>.</note>
+ <human-resource-ref idref="xalandev"/>, and please be sure to note in the subject line that the bug applies to &xslt4c;.</note>
</s3>
1.8 +35 -26 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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- commandline.xml 2000/09/01 19:23:21 1.7
+++ commandline.xml 2000/09/12 13:35:11 1.8
@@ -117,32 +117,41 @@
make it an expression.</p>
</s2><anchor name="icu"/>
<s2 title="Enabling ICU support for 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 support for output encoding. See <resource-ref
- idref="xerces-build-icu"/>.</p>
- <p>TestXSLT 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 substitues 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>Activate <code>#define XALAN_USE_ICU</code> (commented out in the shipped version of
- process.cpp in the XSLTXalan module)<br/><br/>
- In Windows, turn <code>#define XALAN_USE_ICU</code> from a comment into an active #define
- statement. In Linux and AIX, you can do the same, or you can define a XALAN_USE_ICU
- environment variable. If you do the later, the make file passes in the #define statement when
- you do a build. If you use this option,keep in mind that the syntax for defining an
- environmente variable depends on the shell you are using. If you are using the Bourne Shell, K
- Shell, or Bash, use <br/> <code>export XALAN_USE_ICU "1"</code>
- <br/>If you are using C Shell, use<br/> <code>setenv
- XALAN_USE_ICU="1"</code><br/><br/></li>
- <li>Rebuild the TestXSLT executable.<br/><br/>
- For Windows, add ICUBridge to the list Visual C++ list of dependencies for the TestXSLT
- project, and rebuild the TestXSLT executable. For Linux or AIX, use
- <br/> <code>make TestXSLT</code></li>
+ <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
+ support for output encoding. See <resource-ref idref="xerces-build-icu"/>.</p>
+ <p>TestXSLT 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
+ substitues 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>
</ol>
+ <s3 title="Rebuilding 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>
+ </ol>
+
+ </s3>
+ <s3 title="Rebuilding TestXSLT in Linux or AIX">
+ <ol>
+ <li>Define the XALAN_USE_ICU environment variable.<br/>
+ The syntax for defining an environment variable depends on the shell you are using.
+ If you are using the Bourne Shell, K Shell, or Bash, use
+ <br/><br/> <code>export XALAN_USE_ICU "1"</code><br/><br/>
+ If you are using C Shell, use
+ <br/><br/> <code>setenv XALAN_USE_ICU="1"</code><br/><br/></li>
+ <li>Delete the existing TestXSLT.<br/><br/></li>
+ <li>Run make:<br/><br/>
+ <code> make TestXSLT</code></li>
+ </ol>
+ <note>The make file uses the XALAN_USE_ICU environment variable to do the equivalent of a #define and to add ICUBridge
+ to the list of dependencies for TestXSLT. If you uncomment the <code>#define XALAN_USE_ICU</code> statement in
+ process.cpp (which is the right thing to do in Windows), you will get a warning about duplicate settings when you run
+ the make, and TestXSLT will not link with ICUBridge.</note>
+ </s3>
</s2>
</s1>
1.6 +1 -1 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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- extensions.xml 2000/08/29 17:14:55 1.5
+++ extensions.xml 2000/09/12 13:35:11 1.6
@@ -209,7 +209,7 @@
The <ref>prefix</ref> identifies the namespace, and <ref>URI</ref> matches the namespace specified when the function
is installed.<br/><br/>
By default, namespace declarations are included in the transformation output. To exclude namespaces from the output,
-use (<em>NOT YET IMPLEMENTED</em>)<br/><br/>
+use<br/><br/>
<code>exclude-result-prefixes="<ref>prefix-1 prefix-2 ...</ref>"</code><br/><br/>
in the stylesheet element or<br/><br/>
<code>xsl:exclude-result-prefixes="<ref>prefix-1 prefix-2 ...</ref>"</code><br/><br/>
1.11 +4 -3 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.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- getstarted.xml 2000/09/05 12:48:24 1.10
+++ getstarted.xml 2000/09/12 13:35:11 1.11
@@ -40,7 +40,7 @@
<li>The Xalan-C++ load library: &xslt4c-aixlib;</li>
<li>The Xerces-C++ load library: &xml4c-aixlib;</li>
</ul>
-<p>If you want to enable ICU support for the command-line utility, you must build the ICU and rebuild TestXSLT. See <link idref="usagepatterns" anchor="icu">Using the ICU</link> and <link idref="commandline" anchor="icu">Enabling ICU support for TestXSLT</link>.</p>
+<p>If you want to enable ICU support for the command-line utility, you must build the ICU and rebuild TestXSLT with the ICUBridge. See <link idref="usagepatterns" anchor="icu">Using the ICU</link> and <link idref="commandline" anchor="icu">Enabling ICU support for TestXSLT</link>.</p>
<p>For information about using the command-line utility, see <link idref="commandline">Command-Line Utility</link>.</p>
</s3>
<s3 title="What you need to build applications">
@@ -48,16 +48,17 @@
Xalan-C++ and Xerces-C++ header (.hpp) files and (for Windows) the &xslt4c; and &xml4c; 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 on Red Hat Linux 6.1 with a make file and the CNU C++ compiler), the shared object library is in the lib subdirectory.</p>
+<p>In the Linux distribution (built on Red Hat Linux 6.1 with a make file and the GNU C++ compiler), the shared object library is in the lib subdirectory.</p>
<p>In the AIX distribution (built with the make file and xlC_r), the load library is in the lib subdirectory.</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>If you want to enable ICU support in your applications, you must include the ICUBridge headers</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), or copy &xslt4c-linuxlib; to /usr/lib.</p>
-<p>For the Xalan-C++ AIX distribution, place xml-xalan/c/bin and xml-xalan/c/lib on the load library path (LIB for xlC_r), or copy &xslt4c-aixlib; to /usr/lib.</p>
+<p>For the Xalan-C++ AIX distribution, place xml-xalan/c/bin and xml-xalan/c/lib on the load library path (LIB_PATH for AIX), or copy &xslt4c-aixlib; 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"/>
1.6 +3 -1 xml-xalan/c/xdocs/sources/xalan/overview.xml
Index: overview.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/overview.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- overview.xml 2000/09/05 12:48:24 1.5
+++ overview.xml 2000/09/12 13:35:11 1.6
@@ -138,7 +138,9 @@
<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>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>
+ Reference</jump>, Wrox Press, 2000<br/><br/></li>
+ <li>Neil Bradley's <jump href="http://cseng.aw.com/bookpage.taf?ISBN=0-201-67487-4">XSL Companion</jump>,
+ Addison-Wesley, 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>
1.10 +22 -19 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.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- readme.xml 2000/09/01 19:23:24 1.9
+++ readme.xml 2000/09/12 13:35:12 1.10
@@ -123,15 +123,16 @@
</s3><anchor name="win32"/>
<s3 title="Steps for doing a Windows build">
<ol>
- <li>Rearrange the &xslt4c; binary distribution as indicated above so the headers are in
+ <li>Rearrange the &xml4c; binary distribution as indicated above so the headers are in
the xml-xerces/c/src tree and xml-xerces is at the same level as the xml-xerces root
directory.<br/><br/></li>
<li>(Optional) If you are rebuilding the ICUBridge, install the ICU so the icu root directory
is at the same level as the xml-xerces root directory (see <link
- idref="usagepatterns" anchor="icu">Using the ICU</link> <br/><br/></li>
- <li>If you want TestXSLT to use ICU support for number formatting and sorting, complete the
- preceding step, #define XALAN_USE_ICU in process.cpp, and add ICUBridge to the list of
- dependencies for TestXSLT.<br/><br/></li>
+ idref="usagepatterns" anchor="icu">Using the ICU</link> <br/><br/>
+ If you want TestXSLT to use ICU support for number formatting and sorting, install the ICU,
+ uncomment the <code>#define XALAN_USE_ICU</code> statement in process.cpp, and add ICUBridge to the Visual
+ C++ list of TestXSLT dependencies (see <link idref="commandline" anchor="icu">Enabling ICU support for
+ TestXSLT</link>).<br/><br/></li>
<li>Use Visual C++ to open the Xalan workspace from the xml-xalan\c\Projects\Win32\VC6.
<br/><br/></li>
<li>Use Visual C++ to rebuild everything or specific dynamic link libraries and executables of
@@ -140,7 +141,7 @@
</s3><anchor name="unix"/>
<s3 title="Steps for doing a Linux or AIX build">
<ol>
- <li>Rearrange the &xslt4c; binary distribution as indicated above so the headers are in the
+ <li>Rearrange the &xml4c; binary distribution as indicated above so the headers are in the
<ref>xerces-c_x_y_z-platform</ref>/c/src tree, and set the XERCESCROOT environment variable
to the complete path to <ref>xerces-c_x_y_z-platform</ref>.<br/><br/></li>
<li>Set the XALANCROOT environment variable to the complete path to the root of the &xslt4c;
@@ -149,21 +150,23 @@
variable to the complete path to the STLPort distribution. The Linux GNU compiler includes
the STL (Standard Template Library).<br/><br/></li>
<li>(Optional) If you are rebuilding the ICUBridge, install the ICU and define XALAN_USE_ICU
- (see <link idref="usagepatterns" anchor="icu">Using the ICU</link> <br/><br/></li>
+ (see <link idref="usagepatterns" anchor="icu">Using the ICU</link>) <br/><br/></li>
<li>Change directory to xml-xalan/c/src in the &xslt4c; distribution.<br/><br/></li>
<li>Use the chmod +x command to set the executable flags for conf* and
- runConfigure.<br/><br/></li>
+ runConfigure.<br/><br/>
+ <code>chmod +x runConfigure</code><br/>
+ <code>chmod +x conf*</code><br/><br/></li>
<li>Run the runConfigure utility with at least the platform flag (Linux) or the platform, C compilier, and C++ compiler flags (AIX) as indicated below.<br/><br/>
<ref>Linux:</ref> <code>runConfigure -p linux</code><br/>
- <ref>AIX:</ref> runConfigure -p aix -c xlc_r -x xlC-r<br/><br/>
- To see the other runConfigure flags you may include, use the help flag:<br/>
- <code>runConfigure -h</code><br/><br/></li>
+ <ref>AIX:</ref> <code>runConfigure -p aix -c xlc_r -x xlC-r</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>Run the make file:<br/><br/>
- <code>make</code> (rebuild all)<br/>
+ <code>make</code><br/>
or<br/>
- <code>make <ref>targ</ref></code><br/><br/>
- where <ref>targ</ref> is all (rebuild all), lib (the XSLT libary), or TestXSLT (the
- TestSXSLT executable). ICUBridge is included in the build if XALAN_USE_ICU is
+ <code>make <ref>targ</ref></code><br/><br/>
+ where <ref>targ</ref> is ommitted or is <code>all</code> (rebuild all), <code>lib</code> (the XSLT libary), or
+ <code>TestXSLT</code> (the TestSXSLT executable). ICUBridge is included in the build of TestXSLT if XALAN_USE_ICU is
defined.<br/><br/></li>
</ol>
<note>The command you use for setting environment variables depends on the shell you are
@@ -171,13 +174,13 @@
For Bourne Shell, K Shell, or Bash use <em>export</em> ENVAR "val"<br/>
For C Shell, use <em>setenv</em> ENVAR="val"<br/>
where ENVAR is the environment variable name and val is the environment variable
- setting.</note>
+ setting. You can check the setting of an environment variable with <em>echo</em> $ENVAR</note>
</s3><anchor name="samples"/>
<s3 title="Rebuilding a sample application">
<p>The Windows32 distribution includes Visual C++ project files for each of the sample applications. The project files are in the samples subdirectories along with the source files. If you modify a sample and want to recompile it, you can recompile the .cpp file(s) and rebuild the executable.</p>
-<p>The make files that come with the Linux and AIX distributions include targets for rebuilding one or all of the sample applications (with the exception of the ThreadSafe sample, which in its current form only runs under Windows). To rebuild one or more sample applications, go to the xml-xerces/c/src directory and run<br/><br/>
- <code>make <ref>Targ</ref></code><br/><br/>
-where <ref>Targ</ref> is Samples (all the samples), CompileStylesheet, ExternalFunction, SimpleTransform, TraceListen, UseStylesheetParam, or XPathWrapper.</p>
+<p>The make files that come with the Linux and AIX distributions include targets for rebuilding one or all of the sample applications (with the exception of the ThreadSafe sample, which in its current form only runs under Windows). To rebuild one or more sample applications, go to the xml-xalan/c/src directory and run<br/><br/>
+ <code>make <ref>targ</ref></code><br/><br/>
+where <ref>targ</ref> is <code>Samples</code> (all the samples), <code>CompileStylesheet</code>, <code>ExternalFunction</code>, <code>SimpleTransform</code>, <code>TraceListen</code>, <code>UseStylesheetParam</code>, or <code>XPathWrapper</code>.</p>
</s3>
</s2><anchor name="contact"/>
<s2 title="Getting in Touch">
1.8 +4 -5 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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- samples.xml 2000/09/05 12:48:24 1.7
+++ samples.xml 2000/09/12 13:35:12 1.8
@@ -72,10 +72,7 @@
<anchor name="getstarted"/>
<s2 title="Samples to help you get started">
<p>Each of the subdirectories in the &xslt4c; samples directory contains the source files for a
- sample application. In the Windows32 distribution, the executables for all the samples are in the build
- subdirectory, which should be on the system path. If you are using the Linux distribution, you must build the
- sample application executables yourself. Of course you can also consult the sample application source files for
- useful information about how to perform basic operations.</p>
+ sample application. The executables for the samples are in the build subdirectory, which should be on the system path.</p>
<p>With most of the samples, you can use the following procedure:</p>
<ol>
<li>Go to the samples subdirectory containing the sample (use the DOS shell if you are running Windows)
@@ -170,6 +167,8 @@
<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>
+ <note>If an XPathWrapper argument includes characters (such as *) that the shell intercepts, enclose the argument
+ in double quotes.</note>
<source><?xml version="1.0"?>
<doc>
<name first="David" last="Marston"/>
@@ -181,7 +180,7 @@
<p><code>TestDriver foo.xml /doc name/@last</code></p>
<p>and</p>
<p><code>TestDriver foo.xml //name[position()="4"]./@first</code></p>
- <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="externalfunctions"/>
<s2 title="ExternalFunctions">
<p>What it does: implement, install, and illustrate the usage of three extension functions. The functions return a
1.7 +9 -5 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.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- usagepatterns.xml 2000/09/01 19:23:25 1.6
+++ usagepatterns.xml 2000/09/12 13:35:12 1.7
@@ -71,7 +71,7 @@
</ul><anchor name="intro"/>
<s2 title="Introduction">
-<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>
+<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">&xslt4c; API</jump>. For an overview of the
@@ -195,12 +195,12 @@
<note>If the expression is a string and you are using XalanDOMString for the input parameter, enclose it in single quotes to make it a string expression.</note>
<p>You can include the -param flag with two arguments when you call the <link idref="commandline">command line utility</link>. The first argument is the parameter name or key, and the second argument is the string expression (in single quotes). For example:</p>
<p><code>TestXSLT -in foo.xml -xsl foo.xsl -param param1 'boo'</code></p>
-<p>If the string expression includes spaces, first enclose the string in single quotes so it is interpreted as a string expression, and then enclose the resulting string in double quotes so it is interpreted as a single argument. For example:</p>
+<p>If the string expression includes spaces or other characters that the shell intercepts, first enclose the string in single quotes so &xslt4c; interprets it as a string expression, and then enclose the resulting string in double quotes so the shell interprets it as a single argument. For example:</p>
<p><code>TestXSLT -in foo.xml -xsl foo.xsl -param param1 "'hello there'"</code></p>
<p>The <link idref="samples" anchor="usestylesheetparam">UseStylesheetParam</link> sample application also uses a command-line parameter.</p>
</s2><anchor name="compiled"/>
<s2 title="Compiling stylesheets">
-<p>When &xslt4c; performs a transformation with the <link anchor="process">XSLTEngineImpl process() method used above</link>, it starts by compiling the stylesheet into a binary representation. If you intend to use the same stylesheet to perform multiple transformations, you can enhance efficiency by explicitly compiling the stylesheet and using another XSLTEngimeImpl process() method for each transformation. A compiled stylesheet (a <jump href="apidocs/class_stylesheetroot.html">StylesheetRoot</jump> object) thread safe, so it even supports concurrent access by multiple clients. If, for example, you are setting up a server application to perform transformations, you can improve performance by compiling any stylesheets the application repeatedly uses.</p>
+<p>When &xslt4c; performs a transformation with the <link anchor="process">XSLTEngineImpl process() method used above</link>, it starts by compiling the stylesheet into a binary representation. If you intend to use the same stylesheet to perform multiple transformations, you can enhance efficiency by explicitly compiling the stylesheet and using another XSLTEngimeImpl process() method for each transformation. A compiled stylesheet (a <jump href="apidocs/class_stylesheetroot.html">StylesheetRoot</jump> object) is thread safe, so it even supports concurrent access by multiple clients. If, for example, you are setting up a server application to perform transformations, you can improve performance by compiling any stylesheets the application repeatedly uses.</p>
<p>A compiled stylesheet requires its own XPath and XObject factory support objects, independent of the support objects for an XSLT processor. So after you have set up the XSLT processor with its support objects, set up other
factory support objects and use them to create a construction context for the stylesheet:</p>
<source>// Set up the XSLT processor with its support objects
@@ -333,8 +333,9 @@
integrate the ICU with &xslt4c;, but you must do the following in the application where you
want to enable ICU support:</p>
<ol>
- <li>Include the ICUBridge headers</li>
- <li>Substitue ICU support for format-number(), xsl:number, and xsl:sort</li>
+ <li>Include the ICUBridge headers.</li>
+ <li>Substitue ICU support for format-number(), xsl:number, and/or xsl:sort.</li>
+ <li>Provide your application access to the ICUBridge library.</li>
</ol>
<p><em>ICUBridge</em></p>
<p>All &xslt4c; references to ICU are centralized in the ICUBridge module, which supplies the
@@ -343,6 +344,9 @@
#include <ICUBridge/FunctionICUFormatNumber.hpp>
#include <ICUBridge/ICUXalanNumberFormatFactory.hpp>
#include <ICUBridge/ICUBridgeCollationCompareFunctor.hpp></source>
+ <p>Put the ICUBridge library on the library path. For Windows, put &icubridge-win; on the path. For Linux, put
+ &icubridge-linux; on the shared library path (LD_LIBRARY_PATH for Red Hat Linux 6.1) or copy it to /usr/lib.
+ For AIX, put &icubridge-aix; on the load library path (LIB_PATH) or copy it to /usr/lib.</p>
<p><em>Number formatting</em></p>
<p>To enable ICU support for the xsl:number element and the XSLT format-number() function, do
the following:</p>