dleslie 00/09/01 12:23:30
Modified: c/xdocs/sources entities.ent xalan.xml xalanLocal.xml
c/xdocs/sources/xalan commandline.xml faq.xml getstarted.xml
index.xml readme.xml resources.xml
usagepatterns.xml xalan-cdist.gif
Log:
Updates for Xalan-C 1.0
Revision Changes Path
1.6 +8 -5 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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- entities.ent 2000/07/07 16:34:25 1.5
+++ entities.ent 2000/09/01 19:23:08 1.6
@@ -1,19 +1,22 @@
<?xml encoding="US-ASCII"?>
<!ENTITY xslt4c "Xalan-C++">
-<!ENTITY xslt4c-dist "Xalan-C_0_40_0">
-<!ENTITY xslt4c-current "Xalan-C++ version 0.40.0">
+<!ENTITY xslt4c-dist "Xalan-C_1_0">
+<!ENTITY xslt4c-current "Xalan-C++ version 1.0">
<!ENTITY xslt4c-windlls "DOMSupport.dll, PlatformSupport.dll, XalanDOM.dll,
XercesParserLiaison.dll, XercesPlatformSupport.dll, XMLSupport.dll, XPath.dll,
XSLT.dll">
-<!ENTITY xslt4c-linuxlib "libxalan-c0_40.so">
+<!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-winlib "xerces-c_1.lib">
<!ENTITY xml4c-linuxlib "libxerces-c1_2.so">
+<!ENTITY xml4c-aixlib "libxerces-c1_2.a">
<!ENTITY xslt4j "Xalan-Java">
-<!ENTITY icu-used "International Components for Unicode(ICU) 1.4.1.2 source
files">
+<!ENTITY icu-used "International Components for Unicode(ICU) 1.6 source
files">
<!ENTITY icu-windlls "icui18n.dll, icuuc.dll">
-<!ENTITY icu-unixlib "libicu-1_4_1_2.so">
+<!ENTITY icu-unixlib "libicu-1_6.so">
+<!ENTITY icu-aixlib "libicu-1_6.a">
<!ENTITY done SYSTEM "sbk:/sources/xalan/DONE">
<!ENTITY status SYSTEM "sbk:/sources/xalan/STATUS">
<!ENTITY bugs SYSTEM "sbk:/sources/xalan/BUGS">
1.4 +5 -3 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.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- xalan.xml 2000/06/02 19:41:52 1.3
+++ xalan.xml 2000/09/01 19:23:10 1.4
@@ -67,7 +67,7 @@
<separator/>
<document id="index"
- label="Xalan-C++ 0.40.0"
+ label="Xalan-C++ 1.0"
source="xalan/index.xml"/>
<separator/>
@@ -106,7 +106,8 @@
<separator/>
- <external href="http://xml.apache.org/xalan/c-apidocs/index.html";
label="C++ API"/>
+ <external href="http://xml.apache.org/xalan/c-apidocs/index.html";
+ label="C++ API"/>
<separator/>
@@ -122,7 +123,8 @@
<separator/>
-<external href="http://xml.apache.org/bugs/"; label="Bug reporting"/>
+<external href="http://xml.apache.org/bugs/";
+ label="Bug reporting"/>
<separator/>
1.3 +0 -1 xml-xalan/c/xdocs/sources/xalanLocal.xml
Index: xalanLocal.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalanLocal.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- xalanLocal.xml 2000/06/02 18:40:32 1.2
+++ xalanLocal.xml 2000/09/01 19:23:12 1.3
@@ -100,7 +100,6 @@
<separator/>
-
<document id="extensions"
label="Extensions"
source="xalan/extensions.xml"/>
1.7 +33 -0 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.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- commandline.xml 2000/08/29 17:14:54 1.6
+++ commandline.xml 2000/09/01 19:23:21 1.7
@@ -60,6 +60,10 @@
<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>
+</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),
@@ -111,5 +115,34 @@
<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">
+ <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>
+ </ol>
</s2>
</s1>
1.6 +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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- faq.xml 2000/06/29 20:13:19 1.5
+++ faq.xml 2000/09/01 19:23:22 1.6
@@ -70,5 +70,5 @@
XML.</p>
<p>You can use the xsl:stylesheet doctype defined in xsl-html40s.dtd
for stylesheets that generate HTML.</p>
</a>
- </faq>
+ </faq>
</faqs>
1.9 +17 -13 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.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- getstarted.xml 2000/06/29 20:13:19 1.8
+++ getstarted.xml 2000/09/01 19:23:23 1.9
@@ -11,13 +11,14 @@
</ul>
<anchor name="download"/>
<s2 title="Downloading what you need">
-<p>For &xslt4c-current;, we are distributing a Windows32 Visual C++ build
and a Linux build. In the future, we intend to add builds for other
platforms.</p>
+<p>For &xslt4c-current;, we are distributing a Windows32 Visual C++ build, a
Linux GNU build, and an AIX xlC_r build. Please contact us at
<human-resource-ref idref="xalandev"/> if you would like to help provide builds
for other platforms.</p>
<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="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 (<em>NOT FOR THIS
RELEASE</em>)the <resource-ref idref="icu"/>.</p>
+<p>For the Linux build, download <resource-ref
idref="xslt4c-linux-download"/></p>
+<p>For the AIX build, download <resource-ref
idref="xslt4c-aix-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. 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>
@@ -25,8 +26,6 @@
<li>The executable: TestXSLT.exe</li>
<li>The Xalan-C++ dynamic link libraries: &xslt4c-windlls;</li>
<li>The Xerces-C++ dynamic link library: &xml4c-windll;</li>
-<li>(<em>NOT FOR THIS RELEASE</em>) The International Components for Unicode
(ICU) dynamic link libraries: &icu-windlls;</li>
-<li>(<em>NOT FOR THIS RELEASE</em>) The ICU locale data files</li>
</ul>
<p><em>Linux</em></p>
@@ -34,10 +33,14 @@
<li>The utility: TestXSLT</li>
<li>The Xalan-C++ shared library: &xslt4c-linuxlib;</li>
<li>The Xerces-C++ shared library: &xml4c-linuxlib;</li>
- <li>(<em>NOT FOR THIS RELEASE</em>) The International Components for
Unicode (ICU) shared library: &icu-unixlib;</li>
- <li>(<em>NOT FOR THIS RELEASE</em>) The ICU locale data files</li>
</ul>
-<p>(<em>NOT FOR THIS RELEASE</em> and we will place the locale data files
where they can be found) ICU requires you to set the ICU_DATA environment
variable to point to the directory containing the ICU locale data files. In the
Windows32 distribution, this is xml-xalan\c\Build\Win32\VC6\Release\Data. In
the Linux distribution, it is xml-xalan/c/lib/data.</p>
+<p><em>AIX</em></p>
+<ul>
+ <li>The utility: TestXSLT</li>
+ <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>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">
@@ -46,23 +49,24 @@
<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>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>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++ 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>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">
-<p>The &xslt4c; distribution includes a number of basic sample applications.
These samples are easy to compile and run,
- and you can review the source files -- all of which are brief -- to see
just how they work. In the Windows32 distribution, we have precompiled these
samples for you so they are ready to run. In the Linux distribution, you need
to build them first.</p>
+<p>The &xslt4c; distribution includes a number of basic sample applications.
We have precompiled these samples for you so they are ready to run, and you can
review the source files -- all of which are brief -- to see just how they work.
</p>
<p>To run the samples, do the following:</p>
<ol>
-<li>(Linux only) Set up make files and compile the sample sources (you may
need to make some minor changes in the header files to accommodate Linux) and
build an executable for each sample application.</li>
<li>Set up your path (see above). In the Windows32 distribution, the sample
executables are in
-xml-xalan\c\Build\Win32\VC6\Release. For Linux, we suggest you build the
executables in xml-xalan/c/bin.</li>
+xml-xalan\c\Build\Win32\VC6\Release. In the Linux and AIX distributions, the
executables are in xml-xalan/c/bin.</li>
<li>Go to the samples subdirectory containing the sample (use the DOS shell
in Windows).</li>
<li>Run the sample from the command line.</li>
<li>Examine the application source files.</li>
1.8 +29 -18 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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- index.xml 2000/07/07 16:34:26 1.7
+++ index.xml 2000/09/01 19:23:23 1.8
@@ -61,10 +61,11 @@
<s1 title="&xslt4c-current;">
<s2 title="What is it?">
- <p>Xalan is an XSLT processor for transforming XML documents into HTML,
text, or other XML document types.</p>
- <p>&xslt4c-current; represents a robust and an almost complete C++
reference implementation of the W3C Recommendations
- for XSL Transformations (XSLT) and the XML Path Language (XPath). It
uses the latest release of the &xml4c; XML parser
- (&xml4c-used;).</p>
+ <p>Xalan is an XSLT processor for transforming XML documents into HTML,
text, or other XML
+ document types.</p>
+ <p>&xslt4c-current; represents a robust C++ reference implementation of
the W3C Recommendations
+ for XSL Transformations (XSLT) and the XML Path Language (XPath). It
uses the latest release of
+ the &xml4c; XML parser (&xml4c-used;).</p>
</s2>
<s2 title="How do I get it?">
@@ -82,23 +83,33 @@
<tr>
<td>Linux</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>
+ </tr>
+ <tr>
+ <td>AIX</td>
+ <td><resource-ref idref="xslt4c-aix-download"/></td>
+ </tr>
+ </table>
+ <p>Volunteers are more than welcome to help develop builds for other
platforms!</p>
</s2>
<s2 title="Where do I get Xerces?">
- <p>Both distributions include the Xerces runtime environment for Xalan
-- &xml4c-windll; for Windows,
- and &xml4c-linuxlib; 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="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>The distributions include the Xerces runtime environment for Xalan:
&xml4c-windll; for
+ Windows, &xml4c-linuxlib; for Linux, and &xml4c-aixlib; for AIX.</p>
+ <p>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="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="How about extending support for internationalization?">
+ <p>To extend Unicode support for encoding, number formatting, and
sorting to more than 150
+ locales, you can download, build, and integrate the <resource-ref
idref="icu"/> with &xslt4c;.
+ For more information, see <link idref="usagepatterns"
anchor="icu">Using the ICU</link>.</p>
+ </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
- included in the Xalan downloads, as are a number of samples to help you
start using Xalan to transform XML
- documents.</p>
+ <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>
</s1>
1.9 +76 -13 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.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- readme.xml 2000/06/29 20:13:19 1.8
+++ readme.xml 2000/09/01 19:23:24 1.9
@@ -90,31 +90,94 @@
</ul>
<anchor name="jar"/>
<s3 title="Rebuilding &xslt4c;">
+ <ul>
+ <li><link anchor="layout">Layout of Xerces-C and ICU</link></li>
+ <li><link anchor="win32">Steps for doing a Windows build</link></li>
+ <li><link anchor="linux">Steps for doing a Linux or AIX
build</link></li>
+ </ul>
<p>If you want to rebuild &xslt4c; (to produce a debug build, for
example), you need the following:</p>
<ul>
<li>The &xslt4c; source files</li>
<li>The &xml4c; header and (for Windows) .lib files</li>
- <li>(<em>NOT FOR THIS RELEASE</em>) The ICU header and (for Windows)
.lib files</li>
+ <li>(Optional) The ICU header and (for Windows) .lib files</li>
</ul>
<p>The &xslt4c; source files are in the distribution.</p>
<p>The required &xml4c; files are in the &xml4c; binary distributions.</p>
- <p>(<em>NOT FOR THIS RELEASE</em>) To get the ICU, download and unzip the
<resource-ref idref="icu-download"/> from the IBM developerWorks open source
zone,
- and do a build -- see the Windows NT or Unix build instructions in the
readme.html that accompanies the download.</p>
- <note> If you are not rebuilding ICUBridge, you do not need the ICU
header or .lib files.</note>
- <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 &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
as indicated in the following illustration.</p>
+ <p>For information on using the <resource-ref idref="icu"/>, see
+ <link idref="usagepatterns" anchor="icu">Using the ICU</link>.</p>
+ <note>If you are not rebuilding ICUBridge, you do not need the ICU header
or .lib files.</note>
+ <p>To rebuild the Windows32 release, use the Microsoft Visual C++ 6.0
project files. To rebuild
+ the Linux or AIX release, use the make file in the root of the source
directory. The builds look
+ for &xml4c; and ICU in directories parallel to the
+ xml-xalan directory.</p>
+ </s3><anchor name="layout"/>
+ <s3 title="Layout">
+ <p><em>Important</em> We have set up the Visual C++ projects and the
Linux and AIX make files 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.</p>
+<p>If you are using a &xml4c; binary distribution, you must either modify
the &xslt4c; project files or makefile, or rearrange the build directory
structure as indicated in the following illustration.</p>
+<p>For Linux and AIX, the XERCESROOT environment variable points to the
Xerces-C root directory. For Windows, the Xerces-C root directory must be named
xml-xerces, and it must be at the same level as the &xslt4c; root directory.
For all environments, the ICU root directory must be named icu, and it must be
at the same level as the &xslt4c; root directory.</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 &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. (<em>NOT FOR THIS RELEASE</em>) 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"/>
+<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 &xslt4c; we certify that it is compabible with a given
release of &xml4c;. To be safe, stick with distributions that we certify to be
compatible. Reminder: &xslt4c-current; is compatible with
&xml4c-used;.<br/><br/>
+&xslt4c-current; has been tested with &icu-used;. You may be able to use
newer ICU releases as they appear.</note>
+ </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
+ 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>
+ <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
+ interest.<br/><br/></li>
+ </ol>
+ </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
+ <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;
+ distribution.<br/><br/></li>
+ <li>AIX only: Download <resource-ref idref="stlport"/> and set the
STLPORTROOT environment
+ 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>
+ <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>
+ <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>
+ <li>Run the make file:<br/><br/>
+ <code>make</code> (rebuild all)<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
+ defined.<br/><br/></li>
+ </ol>
+ <note>The command you use for setting environment variables depends on
the shell you are
+ using.<br/>
+ 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>
+ </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 Linux distribution does not yet include make files for the sample
applications, so you must construct your own Linux make files and build the
sample executables.</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>
</s3>
</s2><anchor name="contact"/>
<s2 title="Getting in Touch">
1.6 +6 -2 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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- resources.xml 2000/07/12 13:45:04 1.5
+++ resources.xml 2000/09/01 19:23:24 1.6
@@ -22,9 +22,13 @@
<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/xalan-c/&xslt4c-dist;-win32.zip"/>
<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="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"/>
+ <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.6 source files"
location="http://oss.software.ibm.com/developerworks/opensource/icu/project/download/index.html"/>
+<resource id="xerces-build-icu" title="Building ICU for &xml4c;"
location="http://xml.apache.org/xerces-c/build.html#BuildICU"/>
+
+ <resource id="stlport" title="STLport" location="http://www.stlport.org/"/>
<resource id="ApacheLicense" title="The Apache Software License, Version
1.1" location="http://xml.apache.org/dist/LICENSE.txt"/>
1.6 +74 -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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- usagepatterns.xml 2000/08/29 17:14:56 1.5
+++ usagepatterns.xml 2000/09/01 19:23:25 1.6
@@ -66,6 +66,7 @@
<li><link anchor="xpath">Working with XPath expressions</link></li>
<li><link anchor="extensions">Creating and using extension
functions</link></li>
<li><link anchor="tracelistener">Using the TraceListener</link></li>
+<li><link anchor="icu">Using the International Components for Unicode
(ICU)</link></li>
</ul><anchor name="intro"/>
@@ -288,5 +289,77 @@
</ul>
<p>To construct a TraceListener with TraceListenerDefault, you need a
PrintWriter and a boolean for each of these four tracing options. You can then
use the XSLTEngimeImpl setTraceSelects and addTraceListener methods to add the
TraceListener to an XSLTProcessor. See the <link idref="samples"
anchor="tracelisten">TraceListen</link> sample application.</p>
<p>The <link idref="commandline">command-line utility (TextXSLT)</link> and
TraceListen both use TraceListenerDefault to write events to the screen.</p>
-</s2>
+</s2><anchor name="icu"/>
+<s2 title="Using the ICU">
+ <p>You can use the <resource-ref idref="icu"/> to extend support for
encoding, number
+ formatting, and sorting.</p>
+ <ul>
+ <li><em>Encoding</em>
+ <br/> &xml4c; and &xslt4c; use UTF-16 encoding to work with Unicode
data.
+ If you integrate the ICU with &xml4c;, both &xml4c; and &xslt4c; use
ICU support for
+ UTF-16 encoding.<br/><br/></li>
+ <li><em>xsl:number element</em>
+ <br/>Both &xslt4c; and the ICU provide a complete implementation for
+ xsl:number.<br/><br/></li>
+ <li><em>format-number()</em>
+ <br/>This XSLT function includes two or three arguments (the third is
+ optional): number, format pattern, and decimal-format name. &xslt4c;
ignores the format
+ pattern and optional decimal-format name. If you install ICU support
for format-number(),
+ this function is fully supported with all its arguments.<br/><br/></li>
+ <li><em>xsl:sort</em>
+ <br/>If you install ICU spport for xml:sort, &xslt4c; applies the
Unicode sorting
+ algorithm.</li>
+ </ul>
+
+ <p>To get the ICU:</p>
+ <ol>
+ <li>Download and unzip the <resource-ref idref="icu-download"/> from
the IBM
+ developerWorks open source zone.<br/><br/></li>
+ <li>Do a build -- see the Windows NT or Unix build instructions in the
readme.html that
+ accompanies the download.
+ <br/><em>Important</em> For Windows, be sure to install the ICU on the
same drive and at
+ the same level as &xslt4c; and &xml4c;.<br/><br/></li>
+ <li>Set the ICU_DATA environment variable as indicated in the
readme.html.</li>
+ </ol>
+ <s3 title="Enabling ICU support for encoding">
+ <p>If you want to enable ICU support for encoding, you must integrate
ICU with
+ your &xml4c; build. &xml4c; uses ICU for input encoding. See
+ <resource-ref idref="xerces-build-icu"/>.</p>
+ <p>Once you have integreated the ICU with &xml4c;, &xslt4c;
automatically uses ICU support
+ for output encoding (the xsl:output encoding attribute).</p>
+ </s3>
+ <s3 title="Enabling ICU support for number formatting and sorting">
+ <p>If you only want to use the ICU to support number formatting and
sorting, you do not need to
+ 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>
+ </ol>
+ <p><em>ICUBridge</em></p>
+ <p>All &xslt4c; references to ICU are centralized in the ICUBridge
module, which supplies the
+ infrastructure for enabling ICU support for number formatting and
sorting.</p>
+ <source>#include <ICUBridge/ICUBridge.hpp>
+#include <ICUBridge/FunctionICUFormatNumber.hpp>
+#include <ICUBridge/ICUXalanNumberFormatFactory.hpp>
+#include <ICUBridge/ICUBridgeCollationCompareFunctor.hpp></source>
+ <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>
+<source>// Install ICU support for the format-number() function.
+FunctionICUFormatNumber::FunctionICUFormatNumberInstaller theInstaller;
+
+// Create and install a factory for using the ICU for xsl:number.
+ICUXalanNumberFormatFactory theXalanNumberFormatFactory;
+StylesheetExecutionContextDefault::installXalanNumberFormatFactory
+
(&theXalanNumberFormatFactory);</source>
+ <p><em>Sorting</em></p>
+ <p>To enable ICU support for xsl:sort, do the following:</p>
+ <source>// Set up a StylesheetExecutionContextDefault object
+// (named theExecutionContext in the following fragment),
+// and install the ICUCollationCompareFunctor.
+ICUBridgeCollationCompareFunctor theICUFunctor;
+theExecutionContext.installCollationCompareFunctor(&theICUFunctor);</source>
+ </s3>
+ </s2>
</s1>
1.4 +16 -10 xml-xalan/c/xdocs/sources/xalan/xalan-cdist.gif
<<Binary file>>
