dmitryh 2004/04/26 12:24:57
Modified: c/xdocs/html/apiDocs footer.html header.html tail.html
c/xdocs/sources entities.ent xalan.xml
c/xdocs/sources/xalan STATUS commandline.xml extensions.xml
extensionslib.xml faq.xml getstarted.xml
history.xml index.xml readme.xml samples.xml
usagepatterns.xml
Log:
Patch for documentation for release Xalan-C 1.8
Revision Changes Path
1.12 +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.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- footer.html 8 Jan 2004 21:58:19 -0000 1.11
+++ footer.html 26 Apr 2004 19:24:56 -0000 1.12
@@ -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++ XSLT Processor Version
1.7</B><BR>
+ <P ALIGN="CENTER"><B>Xalan-C++ XSLT Processor Version
1.8</B><BR>
Copyright © 1999-2004 The Apache Software
Foundation. All Rights Reserved.</i></p>
</TD>
</TR>
1.10 +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.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- header.html 8 Jan 2004 21:58:19 -0000 1.9
+++ header.html 26 Apr 2004 19:24:56 -0000 1.10
@@ -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++ XSLT Processor Version 1.7</h3>
+<h3 align="center">The Xalan C++ XSLT Processor Version 1.8</h3>
</BODY>
1.9 +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.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- tail.html 8 Jan 2004 21:58:19 -0000 1.8
+++ tail.html 26 Apr 2004 19:24:56 -0000 1.9
@@ -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 2.4.0</B><BR>
+ <P ALIGN="CENTER"><B>Xerces-C XML Parser for C++
Version 2.5.0</B><BR>
Copyright © 1999-2004 The Apache Software
Foundation. All Rights Reserved.
</TD>
</TR>
1.37 +20 -19 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.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- entities.ent 4 Apr 2004 18:30:03 -0000 1.36
+++ entities.ent 26 Apr 2004 19:24:56 -0000 1.37
@@ -58,20 +58,20 @@
<!ENTITY xslt4c "Xalan-C++">
<!ENTITY xslt4c-dist "Xalan-C_1_8_0">
+<!ENTITY xslt4c-current "Xalan-C++ version 1.8">
+<!ENTITY xslt4c-windll "Xalan-C_1_8_0.dll">
+<!ENTITY xslt4c-linuxlib "libxalan-c1_8.so">
+<!ENTITY xslt4c-aixlib "libxalan-c1_8.so">
+<!ENTITY xslt4c-hplib "libxalan-c1_8.sl">
+<!ENTITY xslt4c-solarislib "libxalan-c1_8.so">
<!ENTITY xslt4c-win_root "xml-xalan\c">
<!ENTITY xslt4c-unix_root "xml-xalan/c">
-<!ENTITY xslt4c-current "Xalan-C++ version 1.7">
-<!ENTITY xslt4c-windll "Xalan-C_1_8_0.dll">
-<!ENTITY xslt4c-linuxlib "libxalan-c1_7.so">
-<!ENTITY xslt4c-aixlib "libxalan-c1_7.so">
-<!ENTITY xslt4c-hplib "libxalan-c1_7.sl">
-<!ENTITY xslt4c-solarislib "libxalan-c1_7.so">
<!ENTITY aix43v5-dist "-aix_433-xlc_50">
<!ENTITY aix51v5-dist "-aix_510-xlc_50">
<!ENTITY aix51v5_64-dist "-aix_510_64-xlc_50">
-<!ENTITY aix51v6-dist "-aix_510-xlc_60">
-<!ENTITY aix51v6_64-dist "-aix_510_64-xlc_60">
+<!ENTITY aix51v6-dist "-aix_510-xlc_60_040127">
+<!ENTITY aix51v6_64-dist "-aix_510_64-xlc_60_040127">
<!ENTITY redhat_72_icc-dist "-redhat_72-icc_71">
<!ENTITY redhat_72_ecc-dist "-redhat_72_64-ecc_71">
<!ENTITY hpux11a-dist "-hpux_11-acc_a03">
@@ -85,8 +85,8 @@
<!ENTITY suse_72_zOS-dist "-suse_72_zOS-gcc_29">
<!ENTITY suse_81_IA-dist "-suse_81-gcc_32">
<!ENTITY win32-dist "-win32-msvc_60">
-<!ENTITY win64-dist "-winxp_64-ecc_70">
-<!ENTITY winxp_64-dist "-windows_xp_64-ecl_71">
+<!ENTITY win2003c_64-dist "-windows_2003_64-ecc_71">
+<!ENTITY win2003l_64-dist "-windows_2003_64-ecl_71">
<!ENTITY winnt-dist "-windows_nt-msvc_60">
<!ENTITY win2k-dist "-windows_2000-msvc_60">
<!ENTITY winxp-dist "-windows_xp-msvc_60">
@@ -109,21 +109,21 @@
<!ENTITY xslt4c-winnt-dist "&xslt4c-dist;&winnt-dist;&win_ext;">
<!ENTITY xslt4c-win2k-dist "&xslt4c-dist;&win2k-dist;&win_ext;">
<!ENTITY xslt4c-winxp-dist "&xslt4c-dist;&winxp-dist;&win_ext;">
-<!ENTITY xslt4c-winxp_64-dist "&xslt4c-dist;&winxp_64-dist;&win_ext;">
+<!ENTITY xslt4c-win2003l_64-dist "&xslt4c-dist;&win2003l_64-dist;&win_ext;">
<!ENTITY xslt4c-src_dist_zip "&xslt4c-dist;-src&win_ext;">
<!ENTITY xslt4c-src_dist_targz "&xslt4c-dist;-src&unix_ext;">
<!ENTITY xslt4c-docs_dist_zip "&xslt4c-dist;-docs&win_ext;">
<!ENTITY xslt4c-docs_dist_targz "&xslt4c-dist;-docs&unix_ext;">
<!ENTITY xml4c "Xerces-C++">
-<!ENTITY xml4c-used "Xerces-C++ version 2.4.0">
-<!ENTITY xml4c-dist "xerces-c2_4_0">
-<!ENTITY xml4c-windll "xerces-c_2_4_0.dll">
+<!ENTITY xml4c-used "Xerces-C++ version 2.5.0">
+<!ENTITY xml4c-dist "xerces-c2_5_0">
+<!ENTITY xml4c-windll "xerces-c_2_5_0.dll">
<!ENTITY xml4c-winlib "xerces-c_2.lib">
-<!ENTITY xml4c-linuxlib "libxerces-c2_4_0.so">
-<!ENTITY xml4c-aixlib "libxerces-c2_4_0.a">
-<!ENTITY xml4c-hplib "libxerces-c2_4_0.sl">
-<!ENTITY xml4c-solarislib "libxerces-c2_4_0.so">
+<!ENTITY xml4c-linuxlib "libxerces-c2_5_0.so">
+<!ENTITY xml4c-aixlib "libxerces-c2_5_0.a">
+<!ENTITY xml4c-hplib "libxerces-c2_5_0.sl">
+<!ENTITY xml4c-solarislib "libxerces-c2_5_0.so">
<!ENTITY xml4c-aix43v5-dist "&xml4c-dist;&aix43v5-dist;&unix_ext;">
<!ENTITY xml4c-aix51v5-dist "&xml4c-dist;&aix51v5-dist;&unix_ext;">
@@ -142,10 +142,11 @@
<!ENTITY xml4c-winnt-dist "&xml4c-dist;&winnt-dist;&win_ext;">
<!ENTITY xml4c-win2k-dist "&xml4c-dist;&win2k-dist;&win_ext;">
<!ENTITY xml4c-winxp-dist "&xml4c-dist;&winxp-dist;&win_ext;">
-<!ENTITY xml4c-winxp_64-dist "&xml4c-dist;&winxp_64-dist;&win_ext;">
+<!ENTITY xml4c-win2003c_64-dist "&xml4c-dist;&win2003c_64-dist;&win_ext;">
<!ENTITY xslt4j "Xalan-Java">
<!ENTITY icu-used "International Components for Unicode(ICU) 2.6.1 source
files">
+<!ENTITY icu-current "International Components for Unicode(ICU) version
2.6.1">
<!ENTITY icu-windlls "icui18n.dll, icuuc.dll">
<!ENTITY icubridge-win "ICUBridge.dll">
<!ENTITY done SYSTEM "xalan/DONE">
1.18 +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.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- xalan.xml 26 Feb 2004 22:24:07 -0000 1.17
+++ xalan.xml 26 Apr 2004 19:24:56 -0000 1.18
@@ -26,7 +26,7 @@
<separator/>
<document id="index"
- label="Xalan-C++ 1.7"
+ label="Xalan-C++ 1.8"
source="xalan/index.xml"/>
<separator/>
1.17 +0 -1 xml-xalan/c/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/STATUS,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- STATUS 7 Jan 2004 05:28:38 -0000 1.16
+++ STATUS 26 Apr 2004 19:24:56 -0000 1.17
@@ -1,6 +1,5 @@
<s3 title="Version of &xml4c; to use">
<p>&xslt4c-current; has been tested with &xml4c-used;.</p>
-<note>The &xslt4c-current; download no longer includes the Xerces-C++
distribution for the specified platform. You should either download the
matching &xml4c; distribution for your platform, or rebuild both &xml4c; and
&xslt4c; on your system.</note>
<p>For information about including the Xerces-C++ libraries 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"/>
1.30 +45 -2 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.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- commandline.xml 26 Feb 2004 22:24:07 -0000 1.29
+++ commandline.xml 26 Apr 2004 19:24:56 -0000 1.30
@@ -18,10 +18,13 @@
-->
-<s1 title="&xslt4c; Command-Line Utility">
+<s1 title="&xslt4c; Command-Line Utilities">
<ul>
<li><link anchor="use">Using a command-line utility</link></li>
<li><link anchor="xalanexe">Using the Xalan executable</link></li>
+<!--
+<li><link anchor="confexe">Using the conf utility</link></li>
+-->
</ul><anchor name="use"/>
<s2 title="Using a command-line utility">
<p>To perform a transformation, you can call &xslt4c; from the command line
(or script),
@@ -45,7 +48,7 @@
<tr><td>-m</td><td>Omit the META tag in HTML output.</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>-t name expr</td><td>Diplay timing information.</td></tr>
+ <tr><td>-t name expr</td><td>Display timing information.</td></tr>
<tr><td>-u name expr</td><td>Disable escaping of URLs in HTML
output.</td></tr>
<tr><td>-v</td><td>Validate the XML source document.</td></tr>
<tr><td>-</td><td>A dash as the 'source' argument reads from stdin.<br/>A
dash as the 'stylesheet' argument reads from stdin.<br/>('-' cannot be used for
both arguments.)</td></tr>
@@ -53,4 +56,44 @@
<p>To display a list of the options call the Xalan executable as
follows:</p>
<p><code>Xalan -?</code></p>
</s2>
+<!-- Next Release
+<anchor name="confexe"/>
+<s2 title="Using the conf utility">
+<p>The conf utility is a test harness used to run conformance tests found
under the xml-xalan/test/tests/conf branch. The conf utility is provided in
the bin directory of &xslt4c; UNIX binary distributions and the Build directory
of the &xslt4c; Windows binary distribution. If you downloaded the source
distribution package, you will need to do the following in order to build the
conf utility:</p>
+<p>With the Windows source package,</p>
+<ol>
+<li>Follow the same build instructions as listed under <link idref="readme"
anchor="win32">"Steps to Build on Windows"</link> to build the Xalan
executable.</li>
+<li>From Visual C++, go to "Projects" and select "Set Active Project" and
highlight the "conf" project.</li>
+<li>Go to "Build" and select "Rebuild All" to build the conf utility.</li>
+</ol>
+<p>With the UNIX source package,</p>
+<ol>
+<li>Follow the same build instructions as listed under <link idref="readme"
anchor="unix">"Steps to Build on UNIX"</link></li>
+<li>Run the build with the make target as "Tests".</li>
+</ol>
+<p>If you downloaded the binary distribution, the conf utility is located in
the bin directory. </p>
+<p>Call the conf utility as follows:<br/><br/>
+<code>Conf <ref>test_dir</ref> [-sub <ref><dir></ref> -out
<ref><dir></ref> -gold <ref><dir></ref> -source (XST | XPL |
DOM)]</code><br/><br/>
+
+<table>
+ <tr><th>Option</th><th>Description</th></tr>
+ <tr><td><ref>test_dir</ref></td><td>Specifies the base directory for the
test cases.</td></tr>
+ <tr><td>-sub <ref>dir</ref></td><td>Specifies the specific sub-directory
for the test cases. By default, the sub-directory assumes the same value
specified for the test_dir option.</td></tr>
+ <tr><td>-out <ref>dir</ref></td><td>Specifies the directory to store the
test results output. By default, the output directory is set to
CONF-RESULTS.</td></tr>
+ <tr><td>-gold <ref>dir</ref></td><td>Specifies the directory for the gold
files. By default, the gold file directory is set to
<test_dir>-gold.</td></tr>
+ <tr><td>-source <ref>type</ref></td><td>Specifies the type of parsed
source. Valid values include: XST (XalanSourceTree), XPL
(XercesParserLiaison), or DOM (Document Object Model). By default, this value
is set to XST.</td></tr>
+</table></p>
+<p>To display a list of the options call the conf utility as follows:</p>
+<p><code>conf ‐‐help</code></p>
+<p>After conformance tests have been run, a results report is generated in
HTML format. The results report file name use the following naming
convention:<br/><br/>
+ <code>conf<ref>xxyyzzzz</ref>.html</code>.
+<br/><br/>Where<br/><br/>
+<table>
+ <tr><th>Placeholder</th><th>Description</th></tr>
+ <tr><td>xx</td><td>two digit representation of the current month</td></tr>
+ <tr><td>yy</td><td>two digit representation of the current day</td></tr>
+ <tr><td>zzzz</td><td>four digit representation of the current time stamp in
military format</td></tr>
+</table></p>
+</s2>
+-->
</s1>
1.24 +2 -2 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.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- extensions.xml 12 Apr 2004 15:24:17 -0000 1.23
+++ extensions.xml 26 Apr 2004 19:24:56 -0000 1.24
@@ -119,10 +119,10 @@
}</source>
</s2><anchor name="install"/>
<s2 title="Installing an extension function">
-<p><jump href="apiDocs/class_xalantransformer.html">XalanTransformer</jump>
provides methods for installing and unistalling external functions:</p>
+<p><jump href="apiDocs/class_xalantransformer.html">XalanTransformer</jump>
provides methods for installing and uninstalling external functions:</p>
<ul>
<li>installExternalFunction() makes the function available in the current
instance of XalanTransformer. Use uninstallExternalFunction() to remove the
function.<br/><br/></li>
-<li>installExternalFunctionGlobal() makes the function available globally.
Use uninstallExternalFunctionGlobal() to remove the function. The global
install and unistall operations are not thread-safe. However, all global
functions should be thread-safe, because multiple threads could call a
particular function instance at the same time.</li>
+<li>installExternalFunctionGlobal() makes the function available globally.
Use uninstallExternalFunctionGlobal() to remove the function. The global
install and uninstall operations are not thread-safe. However, all global
functions should be thread-safe, because multiple threads could call a
particular function instance at the same time.</li>
</ul>
<p>These methods include arguments for the namespace, the function name, and
the function implementation.</p>
<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>
1.11 +1 -1 xml-xalan/c/xdocs/sources/xalan/extensionslib.xml
Index: extensionslib.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/extensionslib.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- extensionslib.xml 12 Apr 2004 15:24:17 -0000 1.10
+++ extensionslib.xml 26 Apr 2004 19:24:56 -0000 1.11
@@ -57,7 +57,7 @@
<li><jump href="http://www.exslt.org/dyn/dyn.html";>EXSLT dynamic
functions</jump></li>
<li><jump href="http://www.exslt.org/date/date.html";>EXSLT date-time
functions</jump></li>
</ul>
-<p>Anyone who would like to participate in the &xslt4c; initiative to
support EXSLT by testing these implementations or implementating other EXSLT
functions is more than welcome. Please email us
+<p>Anyone who would like to participate in the &xslt4c; initiative to
support EXSLT by testing these implementations or implementing other EXSLT
functions is more than welcome. Please email us
at the <human-resource-ref idref="xalandev"/>.</p>
</s2>
<anchor name="xalanns"/>
1.47 +12 -4 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.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- faq.xml 12 Apr 2004 15:24:17 -0000 1.46
+++ faq.xml 26 Apr 2004 19:24:56 -0000 1.47
@@ -41,7 +41,7 @@
<faq title="What is &xml4c;?">
<q>What is &xml4c; and why do I need it?</q>
-<a><p>&xml4c; is a validating XML parser written in a portable subset of
C++. &xml4c; makes it easy to give your application the ability to read and
write XML data. Like &xslt4c;, &xml4c; is available from the Apache XML site:
http://xml.apache.org/xerces-c/index.html</p><!--xml4cNote--></a>
+<a><p>&xml4c; is a validating XML parser written in a portable subset of
C++. &xml4c; makes it easy to give your application the ability to read and
write XML data. Like &xslt4c;, &xml4c; is available from the Apache XML site:
<jump
href="http://xml.apache.org/xerces-c/index.html";>http://xml.apache.org/xerces-c/index.html</jump></p><!--xml4cNote--></a>
</faq>
@@ -96,7 +96,7 @@
<faq title="Building on Windows">
<q>What do I need to rebuild &xslt4c; on Windows?</q>
-<a><p>To build &xslt4c; on Windows, you need &xml4c; and MS Visual C++ 6.0
installed with Service Pack 3 for Visual C++ and Visual Studio. You should also
apply the bug fixes for the C++ standard library that shipped with Visual C++
6.0. These fixes are available from the Dinkumware site: <jump
href="http://www.dinkumware.com/vc_fixes.html";>http://www.dinkumware.com/vc_fixes.html</jump>.</p>
+<a><p>In order to build &xslt4c; on Windows, you will need the supported
version of &xml4c; and MS Visual C++ 6.0 installed with Service Pack 5 for
Visual C++ and Visual Studio. In previous versions of &xslt4c;, the requirement
on MS Visual C++ 6.0 was to have Service Pack 3 installed. In this case, you
should also apply the bug fixes for the C++ standard library that shipped with
Visual C++ 6.0. These fixes are available from the Dinkumware site: <jump
href="http://www.dinkumware.com/vc_fixes.html";>http://www.dinkumware.com/vc_fixes.html</jump>.</p>
<p>If you do not want to apply the Dinkumware patches, or you are using a
different Service Pack, you must rebuild all of the Xerces and Xalan
binaries.</p>
<p>For more details, see <link idref="readme" anchor="win32">Steps for doing
a Windows build</link>.</p></a>
</faq>
@@ -237,7 +237,7 @@
<ul>
<li>Use an instance of std::ostrstream or
std::ostringstream to create an XSLTResultTarget. See the StreamTransform
sample for more information.</li>
</ul>
- <p>Input to another tranformation:</p>
+ <p>Input to another transformation:</p>
<ul>
<li>Any of the previous output targets could be used as
the input to another transformation, but the FormatterToSourceTree is probably
the best for efficiency reasons. See the source code for the TestXSLT command
line program for more information.</li>
</ul>
@@ -325,5 +325,13 @@
<a><p>There is no Apache Perl wrapper, however Edwin Pratomo has
written a
wrapper for &xslt4c; version 1.4 that can be found on CPAN</p></a>
</faq>
-
+
+<faq title="Missing LocalMsgIndex.hpp file">
+ <q>Why can't I find the LocalMsgIndex.hpp file?</q>
+ <a>
+ <p>The LocalMsgIndex.hpp file is not shipped with the distributions
because this file is generated during compile time. This file is created at
the start of the build process and customized for the locale and message set
you are using.</p>
+ <p>On Windows, the LocalMsgIndex.hpp header is generated by the
Localization project. By building any project that has a dependency on the
Localization project, will trigger the Message Localization component to built
and the LocalMsgIndex.hpp to be generated.</p>
+ <p>To understand more on how to build with message localization
support, see <link idref="readme" anchor="locale">Steps for Building with
Message Localization Support</link>.</p>
+ </a>
+</faq>
</faqs>
1.50 +33 -33 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.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- getstarted.xml 12 Apr 2004 15:24:17 -0000 1.49
+++ getstarted.xml 26 Apr 2004 19:24:56 -0000 1.50
@@ -29,22 +29,24 @@
<s2 title="Downloading what you need">
<p>For &xslt4c-current;, we are distributing the following:
<ul>
-<li>Windows 32-bit and 64-bit Visual C++ builds</li>
-<li>Red Hat Linux 7.2 32-bit and 64-bit Intel C++ builds</li>
-<li>AIX 5.1 32-bit and 64-bit xlC builds</li>
+<li>AIX 5.1 32-bit and 64-bit xlC_r builds</li>
<li>HP-UX 11 32-bit and 64-bit aCC builds</li>
+<li>Red Hat Linux 7.2 32-bit and 64-bit Intel C++ builds</li>
<li>Solaris 2.7 32-bit and 64-bit Forte C++ builds</li>
+<li>SuSE Linux 8.1 for IA-32 gcc 3.2.2 build </li>
+<li>Windows 32-bit and 64-bit Visual C++ builds</li>
</ul>
</p>
+<!-- Leave this section in for future releases
<p>New to the &xslt4c-current; binary distribution list, we are also
providing the following:
<ul>
-<li>SuSE Linux 8.1 for IA-32 gcc 3.2.2 build </li>
</ul>
</p>
+-->
<p>As with previous releases, the documentation build containing this User's
Guide and API documentation
will be provided in a separate distribution.</p>
<p>Please contact us at <human-resource-ref idref="xalandev"/> if you would
like to help provide builds for other platforms.</p>
-<p>If you do not already have it, you must also download the &xml4c; 2.4.0
build as indicated below.</p>
+<p>If you do not already have it, you must also download the &xml4c-used;
build as indicated below.</p>
<note>The Xalan distribution files are in <resource-ref
idref="xslt4c-distdir"/>. The Xerces distribution files are in <resource-ref
idref="xml4c-distdir"/>. Xalan documentation is provided in a separate package
from the binary distribution files. For Windows, documentation is packaged
with the file name &xslt4c-docs_dist_zip;. For UNIX, documentation is packaged
with the file name of &xslt4c-docs_dist_targz;.</note>
<table>
<tr>
@@ -98,15 +100,14 @@
<td>SuSE Linux 8.1 (32-bit)</td>
</tr>
<tr>
- <td>
- &xslt4c-winnt-dist;<br/>
- </td>
- <td>
- &xml4c-winnt-dist;<br/>
- </td>
- <td>
- Windows NT<br/>
- </td>
+ <td>&xslt4c-win2k-dist;<br/></td>
+ <td>&xml4c-winnt-dist;<br/></td>
+ <td>Windows 2000<br/></td>
+ </tr>
+ <tr>
+ <td>&xslt4c-win2003l_64-dist;<br/></td>
+ <td>&xml4c-win2003c_64-dist;<br/></td>
+ <td>Windows 2003 Server (64-bit)<br/></td>
</tr>
</table>
<p>The compiler version used for each platform is listed in the table below.
@@ -120,25 +121,24 @@
<td>IBM C and C++ for AIX 6.00</td>
</tr>
<tr>
- <td>Solaris 2.7</td>
- <td>Sun Workshop 6 update 2</td>
- </tr>
- <tr>
<td>HP/UX 11.0</td>
- <td>aCC A.03.37</td>
+ <td>aCC A.03.52</td>
</tr>
<tr>
<td>Red Hat Linux 7.2</td>
<td>Intel C++ Compiler, version 7.1</td>
</tr>
<tr>
+ <td>Solaris 2.7</td>
+ <td>Sun Workshop 6 update 2</td>
+ </tr>
+ <tr>
<td>SuSE Linux 8.1</td>
<td>gcc Compiler, version 3.2.2</td>
</tr>
<tr>
<td>Windows NT, 2000, and XP</td>
- <td>Microsoft Visual C++ with SP3 and <jump
href="http://www.dinkumware.com/vc_fixes.html";>
- Dinkumware fixes</jump> (for 32-bit)<br/>
+ <td>Microsoft Visual C++ with SP5 (for 32-bit)<br/>
Intel C++ Compiler, version 7.1 (for 64-bit)</td>
</tr>
</table>
@@ -155,9 +155,9 @@
<li><link anchor="unixpath">For UNIX</link></li>
</ul><anchor name="windowspath"/>
<s3 title="For Windows">
-<p>To use the Windows distribution, you must place the Xalan executables and
the Xalan and Xerces libraries on the path:</p>
+<p>To use the Windows binary distribution, you must place the Xalan
executables and the Xalan and Xerces libraries on the path:</p>
<ul>
-<li>Put &xslt4c-win_root;\Build\Win32\VC6\Release and
&xml4c-dist;-<my_Windows_distribution>\bin on the path.</li>
+<li>Put &xslt4c-dist;-<my_Windows_distribution>\bin and
&xml4c-dist;-<my_Windows_distribution>\bin on the path.</li>
</ul>
<p>The Visual C++ Xalan project included with the Windows release knows the
relative paths to the Xalan headers and libraries, but it does not know where
you have unzipped the Xerces distribution. If you plan to use Visual C++ to
build Xalan applications or <link idref="readme" anchor="jar">rebuild
Xalan</link>, you must also provide Visual C++ with access to the Xerces
headers and libraries.</p>
<p>Use the Visual C++ Tools menu to open the Options dialog box, go to the
Directories tab, and do the following:</p>
@@ -168,30 +168,30 @@
</s3><anchor name="unixpath"/>
<s3 title="For UNIX">
-<p>To use one of the UNIX distributions, you must place the &xslt4c;
executable on the path, and
+<p>To use one of the UNIX binary distributions, you must place the &xslt4c;
executable on the path, and
the &xslt4c; and &xml4c; libraries on the library path.</p>
<p>For the &xslt4c; AIX distributions:</p>
<ul>
-<li>Put &xslt4c-unix_root;/bin on the path (PATH).</li>
-<li>Put &xslt4c-unix_root;/lib and
&xml4c-dist;-<my_AIX_distribution>/lib
+<li>Put &xslt4c-dist;-<my_AIX_distribution>/bin on the path
(PATH).</li>
+<li>Put &xslt4c-dist;-<my_AIX_distribution>/lib and
&xml4c-dist;-<my_AIX_distribution>/lib
on the library path (LIBPATH), or copy the shared libraries to /usr/lib.</li>
</ul>
<p>For the &xslt4c; HP-UX 11 distributions:</p>
<ul>
-<li>Put &xslt4c-unix_root;/bin on the path (PATH).<br/><br/></li>
-<li>Put &xslt4c-unix_root;/lib and
&xml4c-dist;-<my_HPUX_distribution>/lib on the library path (SHLIB_PATH),
or copy
+<li>Put &xslt4c-dist;-<my_HPUX_distribution>/bin on the path
(PATH).<br/><br/></li>
+<li>Put &xslt4c-dist;-<my_HPUX_distribution>/lib and
&xml4c-dist;-<my_HPUX_distribution>/lib on the library path (SHLIB_PATH),
or copy
the shared libraries to /usr/lib.</li>
</ul>
<p>For the &xslt4c; Solaris distributions:</p>
<ul>
-<li>Put &xslt4c-unix_root;/bin on the path (PATH).<br/><br/></li>
-<li>Put &xslt4c-unix_root;/lib and
&xml4c-dist;-<my_solaris_distribution>/lib on the library path
+<li>Put &xslt4c-dist;-<my_Solaris_distribution>/bin on the path
(PATH).<br/><br/></li>
+<li>Put &xslt4c-dist;-<my_Solaris_distribution>/lib and
&xml4c-dist;-<my_Solaris_distribution>/lib on the library path
(LD_LIBRARY_PATH), or copy the shared libraries to /usr/lib.</li>
</ul>
<p>For the &xslt4c; RedHat and SuSE Linux distributions:</p>
<ul>
-<li>Put &xslt4c-unix_root;/bin on the path (PATH).</li>
-<li>Put &xslt4c-unix_root;/lib and
&xml4c-dist;-<my_linux_distribution>/lib on the library path
(LD_LIBRARY_PATH),
+<li>Put &xslt4c-dist;-<my_Linux_distribution>/bin on the path
(PATH).</li>
+<li>Put &xslt4c-dist;-<my_Linux_distribution>/lib and
&xml4c-dist;-<my_Linux_distribution>/lib on the library path
(LD_LIBRARY_PATH),
or copy the shared libraries to /usr/lib.</li>
</ul>
</s3>
@@ -201,7 +201,7 @@
<p>To run the samples, do the following:</p>
<ol>
<li>Set up your path (see above). In the Windows32 distribution, the sample
executables are in
-&xslt4c-win_root;\Build\Win32\VC6\Release. In the UNIX distributions, the
executables are in &xslt4c-unix_root;/bin.</li>
+&xslt4c-dist;-<my_Windows_distribution>\bin. In the UNIX
distributions, the executables are in
&xslt4c-dist;-<my_UNIX_distribution>/bin.</li>
<li>Go to the samples subdirectory containing the sample.</li>
<li>Run the sample from the command line (in Windows, use the DOS
shell).</li>
<li>Examine the application source files.</li>
1.12 +31 -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.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- history.xml 12 Apr 2004 15:24:17 -0000 1.11
+++ history.xml 26 Apr 2004 19:24:56 -0000 1.12
@@ -14,6 +14,37 @@
* limitations under the License.
-->
+ <s3 title="Changes for &xslt4c; version 1.7">
+ <p>Major updates since version 1.7 include:</p>
+ <ul>
+ <li><resource-ref idref="bugsfixedforthisrelease"/>.</li>
+ <li>Message Localization Support. This feature enables &xslt4c; to
issue diagnostic messages
+ in languages other than the default language (English). In order to
utilize this feature,
+ the user must provide a version of the &xslt4c; message catalog that
has been translated in
+ their language of choice. For more information on how to exploit this
feature, please see
+ <link anchor="locale">Steps for doing a Build with Message
Localization Support</link>.</li>
+ <li>Build, packaging, and installation improvements. Changes to the
&xslt4c; makefiles now
+ allow for a more flexible build, packaging, and install process. Each
step in a typical
+ build process can be invoked by specifying the appropriate target, for
example to build the
+ executable, and/or samples, or install the build at user-specified
location. For more
+ information on building &xslt4c;, please see <link anchor="unix">Steps
for doing a Unix build
+ </link>.</li>
+ <li>Deprecated DOM Support. The XercesBridge classes have been marked
deprecated and moved
+ into an exclusive directory within the xalanc/XercesParserLiaison
directory called
+ 'Deprecated'. If your application is dependent on these classes to
interface with the
+ deprecated Xerces DOM you must alter your include directive with the
'Deprecated' directory.
+ For example:<br/><br/>
+ <code>#include
"xalanc/XercesParserLiaison/XercesDocumentBridge.hpp"</code><br/><br/>
+ should be changed to:<br/><br/>
+ <code>#include
"xalanc/XercesParserLiaison/Deprecated/XercesDocumentBridge.hpp"</code><br/><br/></li>
+ <li>Upgrade from Xerces-C 2.3 to Xerces-C 2.4. </li>
+ <li>Porting of ThreadSafe example to UNIX platform.</li>
+ <li>Implementation of EXSLT string extension functions encode-uri()
and decode-uri(). </li>
+ <li>Implementation of EXSLT dynamic extension function evaluate().
</li>
+ <li>Implementation of EXSLT date-time extension function
date-time().</li>
+ </ul>
+ </s3>
+
<s3 title="Changes for &xslt4c; version 1.6">
<p>Major updates since version 1.5 include:</p>
<ul>
1.38 +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.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- index.xml 26 Feb 2004 22:24:07 -0000 1.37
+++ index.xml 26 Apr 2004 19:24:56 -0000 1.38
@@ -24,12 +24,12 @@
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
works with a compatible release of the
- &xml4c; XML parser: &xml4c-used;. The focus for this release is on bug
fixes, build and packaging improvements, and a number of new features such as
Message Localization Support and additional EXSLT 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, build support for a number of new platforms, and changes to the Xerces
Deprecated DOM support. For the details, see the <link idref="readme">Release
Notes</link>.</p>
</s2>
<s2 title="How do I get it?">
- <p>Download and unzip the &xslt4c; distribution file and the
corresponding &xml4c; distributions file for your platform. For the details,
see <link idref="getstarted" anchor="download">Downloading what you
need</link>. The &xslt4c; distribution includes platform-specific binaries,
documentation, sample applications, the complete &xslt4c; source tree.</p>
- <p>A source-only distribution is also available, if you want to build
your own binaries.</p>
+ <p>Download and unzip the &xslt4c; distribution file and the
corresponding &xml4c; distributions file for your platform. For the details,
see <link idref="getstarted" anchor="download">Downloading what you
need</link>. The &xslt4c; distribution includes source-only distribution,
documentation, sample applications, the complete &xslt4c; source tree.</p>
+ <p>Binary distributions are also available for a limited set of
platforms.</p>
</s2>
<s2 title="How about support for internationalization?">
<p>To extend Unicode support for encoding, number formatting, and
sorting, you can download,
1.55 +90 -65 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.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- readme.xml 12 Apr 2004 15:24:17 -0000 1.54
+++ readme.xml 26 Apr 2004 19:24:56 -0000 1.55
@@ -30,40 +30,28 @@
<anchor name="status"/>
<s2 title="Status">
<ul>
- <li><link anchor="done">Changes for &xslt4c; version 1.7</link></li>
+ <li><link anchor="done">Changes for &xslt4c; version 1.8</link></li>
<li><link anchor="bugs">Bug reporting</link></li>
<li><link anchor="xml4c">Version of &xml4c; to use</link></li>
<li><link anchor="to-do">To-do tasks for future &xslt4c;
releases</link></li>
</ul>
<anchor name="done"/>
- <s3 title="Changes for &xslt4c; version 1.7">
- <p>Major updates since version 1.6 include:</p>
+ <s3 title="Changes for &xslt4c; version 1.8">
+ <p>Major updates since version 1.7 include:</p>
<ul>
<li><resource-ref idref="bugsfixedforthisrelease"/>.</li>
- <li>Message Localization Support. This feature enables &xslt4c; to
issue diagnostic messages
- in languages other than the default language (English). In order to
utilize this feature,
- the user must provide a version of the &xslt4c; message catalog that
has been translated in
- their language of choice. For more information on how to exploit this
feature, please see
- <link anchor="locale">Steps for doing a Build with Message
Localization Support</link>.</li>
- <li>Build, packaging, and installation improvements. Changes to the
&xslt4c; makefiles now
- allow for a more flexible build, packaging, and install process. Each
step in a typical
- build process can be invoked by specifying the appropriate target, for
example to build the
- executable, and/or samples, or install the build at user-specified
location. For more
- information on building &xslt4c;, please see <link anchor="unix">Steps
for doing a Unix build
- </link>.</li>
- <li>Deprecated DOM Support. The XercesBridge classes have been marked
deprecated and moved
- into an exclusive directory within the xalanc/XercesParserLiaison
directory called
- 'Deprecated'. If your application is dependent on these classes to
interface with the
- deprecated Xerces DOM you must alter your include directive with the
'Deprecated' directory.
- For example:<br/><br/>
- <code>#include
"xalanc/XercesParserLiaison/XercesDocumentBridge.hpp"</code><br/><br/>
- should be changed to:<br/><br/>
- <code>#include
"xalanc/XercesParserLiaison/Deprecated/XercesDocumentBridge.hpp"</code><br/><br/></li>
- <li>Upgrade from Xerces-C 2.3 to Xerces-C 2.4. </li>
- <li>Porting of ThreadSafe example to UNIX platform.</li>
- <li>Implementation of EXSLT string extension functions encode-uri()
and decode-uri(). </li>
- <li>Implementation of EXSLT dynamic extension function evaluate().
</li>
- <li>Implementation of EXSLT date-time extension function
date-time().</li>
+ <li>Upgrade from Xerces-C 2.4 to Xerces-C 2.5. </li>
+ <li>Provide build support for Cygwin and HP-UX 11.00 on Itanium.
Although binary distributions are not provided for the Cygwin environment and
+ HP-UX 11.00 on Itanium platform, the build configuration files
provided in the source distribution can be used to build on these platforms.
</li>
+ <li>Project files for supporting Microsoft Visual Studio .NET.
Although a binary distribution for the Microsoft Visual Studio .NET
+ is not provided in this release, Visual Studio solution files are
provided in the Windows source distribution for those who choose to build
+ on this platform. Please see <link anchor="dotNet">"Step for
doing a Windows Build with Visual Studio .NET"</link> for details.</li>
+ <li>Additional changes to Xerces Deprecated DOM support. This is
another step towards phasing out the support for Xerces Deprecated DOM. Users
are encouraged to modify their applications to interface with the new Xerces
DOM support. For more information on the effects of these changes to your
build environment, please see <link anchor="xercesdepdom">"Steps for doing a
Build with Xerces Deprecated DOM Support"</link></li>
+ <!--
+ <li>Porting of conf utility to the UNIX platform. The conf utility is
a test harness designed to run the conformance tests located under the
xml-xalan/test/tests directory. After the tests have been run, a results
report is generated in HTML format for easy viewing. For more information on
how to use this tool, please see <link idref="commandline"
anchor="confexe">"Using the command line utility"</link>.</li>
+ -->
+ <li>Implemented optimizations to significantly improve the throughput
of the ICU-enabled "format-number" function.</li>
+ <li>Changes in the XML Serializer. The serializer will no longer put a
newline after the xml header tag unless indent="yes". See bugzilla <jump
href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24304";>24304</jump> and
<jump
href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28386";>28386</jump>.</li>
</ul>
</s3>
@@ -89,50 +77,71 @@
<s3 title="Rebuilding &xslt4c;">
<ul>
<li><link anchor="needed">What you need from the
distributions</link></li>
- <li><link anchor="win32">Steps for doing a Windows build</link></li>
+ <li><link anchor="win32">Steps for doing a Windows Build</link></li>
+ <li><link anchor="dotNet">Steps for doing a Windows Build with Visual
Studio .NET</link></li>
<li><link anchor="unix">Steps for doing a UNIX build</link></li>
<li><link anchor="locale">Steps for doing a Build with Message
Localization Support</link></li>
+ <li><link anchor="xercesdepdom">Steps for doing a Build with Xerces
Deprecated DOM Support</link></li>
</ul></s3><anchor name="needed"/>
<s3 title="What you need from the distributions">
<p>To rebuild &xslt4c;, you need the &xslt4c; source files, the &xml4c;
header files, and
for Windows the &xml4c; .lib file. If you want to rebuild with the ICU,
you will need to download the ICU source package to build the ICU libraries.
</p>
- <p>The &xslt4c; source tree is in the src subdirectory of the &xslt4c;
<link idref="getstarted" anchor="download">binary distributions</link>. The
&xml4c; header files are in the include/xercesc tree of the corresponding
&xml4c; binary distributions. The Windows Xerces .lib file is in the lib
directory of the &xml4c; Windows binary distribution.</p>
<note>You can also download &xslt4c; source distributions from <resource-ref
idref="xslt4c-distdir"/>: &xslt4c-dist;-src.zip and &xslt4c-dist;-src.tar.gz.
&xml4c; source distributions are available from <resource-ref
idref="xml4c-distdir"/>:
&xml4c-dist;-src.zip and &xml4c-dist;-src.tar.gz.</note>
<p>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 compatible with a given
version of &xml4c;. To be safe, use the Xerces distributions that we certify as
compatible. Reminder: &xslt4c-current; is compatible with &xml4c-used;.</p>
<p>For information on using the <resource-ref idref="icu"/>, see
<link idref="usagepatterns" anchor="icu">Using the ICU</link>.
- &xslt4c-current; has been tested with &icu-used;. You may be able to use
newer ICU releases as they appear.</p>
+ The recommended version of ICU for &xslt4c-current; is &icu-current;. You
may be able to use newer ICU releases as they appear.</p>
</s3><anchor name="win32"/>
<s3 title="Steps for doing a Windows build">
- <p>To build &xslt4c; on Windows, you need &xml4c; and MS Visual C++ 6.0
installed with Service Pack 3 for Visual C++ and Visual Studio. You should also
apply the bug fixes for the C++ standard library that shipped with Visual C++
6.0. These fixes are available from the Dinkumware site: <jump
href="http://www.dinkumware.com/vc_fixes.html";>http://www.dinkumware.com/vc_fixes.html</jump>.</p>
- <p>If you do not want to apply the Dinkumware patches, or you are using a
different Service Pack, you must rebuild all of the Xerces and Xalan
binaries.</p>
+ <p>To build &xslt4c; on Windows, you need &xml4c; and MS Visual C++ 6.0
installed with Service Pack 5 for Visual C++ and Visual Studio .NET.</p>
+ <p>If you are using a different Service Pack, you must rebuild all of the
Xerces and Xalan binaries.</p>
<p>Before you do the following, be sure you have <link idref="getstarted"
anchor="windowspath">provided Visual C++ the paths to the Xerces headers and
libraries</link>.</p>
<ol>
- <li>If you want to enable ICU support, install the ICU so the ICU root
directory is at the same level as the xml-xerces directory (see <link
- idref="usagepatterns" anchor="icu">Using the ICU</link>). If you
choose to build Xalan with ICU, you will need to rebuild the Xerces binary with
ICU as well.<br/><br/></li>
- <li>Use Visual C++ to open the Xalan workspace from the
&xslt4c-win_root;\Projects\Win32\VC6. If you are building with ICU, then use
XalanICU.dsw. Otherwise, open the Xalan.dsw workspace.
- <br/><br/></li>
- <li>From Visual C++, go to "Tools" and select "Options". From the
"Options" window, click on the "Directories" tab and do the following:
+ <li>Create the ICUROOT environment variable and set it the the path of
the ICU root.</li>
+ <li>Create the XERCESCROOT environment variable and set it to the path
of the root of &xml4c;.</li>
+ <li>Use Visual C++ to open the Xalan workspace (.dsw) from the
&xslt4c-win_root;\Projects\Win32\VC6. If you are building with ICU, then use
XalanICU.dsw. Otherwise, open the Xalan.dsw workspace.<br/><br/>
+ <note>You may need to restart Visual Studio .NET in order for ICUROOT
and XERCESCROOT to take effect.</note>
+ <br/>
+ As an alternative method to the steps described above, would be to go to
"Tools" and select "Options" from Visual C++. From the "Options" window, click
on the "Directories" tab and do the following:
<ol>
<li>Show Directories for: Executable files. Add the Xerces bin
directory to the list.</li>
<li>Show Directories for: Include files. Add the Xerces include
directory to the list. If you are building with ICU, add the ICU include
directory to the list as well.</li>
<li>Show Directories for: Library files. Add the Xerces lib directory to
the list. If you are building with ICU, add the ICU lib directory to the list
as well.</li>
</ol></li>
- <li>Use Visual C++ to build the Xalan library and executables of
interest.</li>
</ol>
<note>To recompile existing applications without changing your source
code, be sure to modify your Project settings to pick up the Xalan headers in
its new location. (see image below)</note>
<p><img src="options-sane.gif" alt="Visual C++ 6.0 Include Directories
change"/></p>
+</s3>
+<anchor name="dotNet"/>
+<s3 title="Steps for doing a Windows Build with Microsoft Visual Studio
.NET">
+ <p>For users who want to build with Visual Studio .NET,</p>
+ <ol>
+ <li>Create the ICUROOT environment variable and set it the the path of
the ICU root.</li>
+ <li>Create the XERCESCROOT environment variable and set it to the path
of the root of &xml4c;.</li>
+ <li>Use Visual Studio .NET to open the Xalan solution (.sln) from the
&xslt4c-win_root;\Projects\Win32\VC7. If you are building with ICU, then use
XalanICU.sln. Otherwise, open the Xalan.sln solution file.<br/><br/>
+ <note>You may need to restart Visual Studio .NET in order for ICUROOT
and XERCESCROOT to take effect.</note>
+ <br/>
+ An alternative method to the steps described above, would be to go to
"Tools" and select "Options" from Visual Studio .NET. From the "Options"
window, click on the "Projects" folder to expand the list. Select "VC++
Directories" from the list and do the following:
+ <ol>
+ <li>Show Directories for: Executable files. Add the Xerces bin
directory to the list.</li>
+ <li>Show Directories for: Include files. Add the Xerces include
directory to the list. If you are building with ICU, add the ICU include
directory to the list as well.</li>
+ <li>Show Directories for: Library files. Add the Xerces lib directory to
the list. If you are building with ICU, add the ICU lib directory to the list
as well.</li>
+ </ol></li>
+ </ol>
+ <note>To recompile existing applications without changing your source
code, be sure to modify your Project settings to pick up the Xalan headers in
its new location. (see image below)</note>
+ <p><img src="NET_options.jpg" alt="Visual Studio .NET Include Directories
change"/></p>
</s3><anchor name="unix"/>
<s3 title="Steps for doing a UNIX build">
+ <p>For users who want to build in the UNIX environment,</p>
<ol>
<li>The Xalan build files are written for GNU make, and will not work
with other make utilities.<br/><br/></li>
<li>Set the XERCESCROOT environment variable to the path to the root
of &xml4c;.<br/><br/></li>
<li>Set the XALANCROOT environment variable to the path to the c
directory in the root of the &xslt4c;
distribution. For example, if the distribution is located in
"/home/mydir", you would set the XALANCROOT to
"/home/mydir/&xslt4c-unix_root;". <br/><br/></li>
<li>(Optional) If you are including the ICUBridge, install the ICU,
use the shell to define XALAN_USE_ICU and to set the ICUROOT environment
variable to the path to the ICU root. For more information, see (see <link
idref="usagepatterns" anchor="icu">Using the ICU</link>). Note that building
Xalan with ICU requires that Xerces must also be built with ICU.<br/><br/></li>
- <li>Change directory to &xslt4c-unix_root; in the &xslt4c;
distribution. You can also
+ <li>Change directory to XALANCROOT. You can also
build Xalan-C outside of the source tree, but you will need to
adjust the path to the
runConfigure script in the next step.<br/><br/></li>
<li>Run the runConfigure utility and provide the platform, C compiler,
and C++ compiler flags as
@@ -143,9 +152,9 @@
<table>
<tr><th>flag</th><th>Description</th></tr>
<tr><td>p</td><td>Build platform. Option must be provided by user.
Valid values <br/>include:
- aix, linux, freebsd, netbsd, solaris, hp-10, hp-11, irix, tru64,
<br/>macosx. </td></tr>
- <tr><td>c</td><td>C compiler name. Example: gcc, cc, c89, xlc,
etc.</td></tr>
- <tr><td>x</td><td>C++ compiler name. Example: g++, xlC, CC,
etc.</td></tr>
+ aix, linux, freebsd, netbsd, solaris, hp-10, hp-11, hp-11-ia64,
irix,<br/> tru64, macosx, cygwin. </td></tr>
+ <tr><td>c</td><td>C compiler name. Example: gcc, cc, c89, xlc_r,
etc.</td></tr>
+ <tr><td>x</td><td>C++ compiler name. Example: g++, xlC_r, CC,
etc.</td></tr>
<tr><td>d</td><td>Indicates build is a debug build. Takes no
values. Default is no <br/>debug.</td></tr>
<tr><td>t</td><td>Transcoder to use. Valid value is 'icu'. Default
is null.</td></tr>
<tr><td>m</td><td>Type of localization support method. Valid
values include: inmem, <br/>icu, and nls.
@@ -163,17 +172,20 @@
</table><br/>
<ref>Linux using GCC:</ref> <code>./runConfigure -p
linux -c gcc -x c++</code><br/>
<ref>Linux using the Intel
compiler:</ref> <code>./runConfigure -p linux -c icc -x
icpc</code><br/>
- <ref>AIX
(32-bit):</ref> <code>./runConfigure -p aix -c xlc -x
xlC</code><br/><br/>
- <ref>AIX
(64-bit):</ref> <code>./runConfigure -p aix -c xlc -x
xlC -b 64</code><br/><br/>
+ <ref>AIX
(32-bit):</ref> <code>./runConfigure -p aix -c xlc_r -x
xlC_r</code><br/><br/>
+ <ref>AIX
(64-bit):</ref> <code>./runConfigure -p aix -c xlc_r -x
xlC_r -b 64</code><br/><br/>
+ <ref>Cygwin (32-bit):</ref> <code>./runConfigure -p
cygwin -c gcc -x g++</code><br/><br/>
<ref>HP-UX 11 (32-bit):</ref> <code>./runConfigure -p
hp-11 -c cc -x aCC</code><br/><br/>
<ref>HP-UX 11 (64-bit):</ref> <code>./runConfigure -p
hp-11 -c cc -x aCC -b 64</code><br/><br/>
- <ref>Solaris (32-bit):</ref> <code>./runConfigure -p
Solaris -c cc -x CC</code><br/><br/>
- <ref>Solaris (64-bit):</ref> <code>./runConfigure -p
Solaris -c cc -x CC -b 64</code><br/><br/>
+ <ref>HP-UX 11 for Itanium
(32-bit):</ref> <code>./runConfigure -p hp-11-ia64 -c cc -x
aCC</code><br/><br/>
+ <ref>HP-UX 11 for Itanium
(64-bit):</ref> <code>./runConfigure -p hp-11-ia64 -c cc -x aCC -b
64</code><br/><br/>
+ <ref>Solaris (32-bit):</ref> <code>./runConfigure -p
solaris -c cc -x CC</code><br/><br/>
+ <ref>Solaris (64-bit):</ref> <code>./runConfigure -p
solaris -c cc -x CC -b 64</code><br/><br/>
If you choose to install the distribution after building the
libraries and executables,
then you will need to indicate where you would like the
distribution to be installed.
To specify the install directory for your distribution, specify
the flag -P <install directory>.
For example, building and installing on the AIX platform:<br/><br/>
- <code>./runConfigure -p aix -c xlc -x xlC -P
$HOME/my_xalan</code><br/><br/>
+ <code>./runConfigure -p aix -c xlc_r -x xlC_r -P
$HOME/my_xalan</code><br/><br/>
<note>The standard binary directories bin, lib, and include are
created in the specified directory only if the install or install-package
option is
specified in the build process.<br/><br/></note>
To see the other runConfigure flags you may include, use the help
flag:<br/><br/>
@@ -193,8 +205,8 @@
<tr><td>install</td><td>Build the library, executables and copy
them (along with <br/>the header files)
the specified install location.</td></tr>
<tr><td>install-package</td><td>Installs the library, executables,
samples to the <br/>specified location.</td></tr>
- <tr><td>samples</td><td>Builds the samples.</td></tr>
- <tr><td>tests</td><td>Builds the tests.</td></tr>
+ <tr><td>Samples</td><td>Builds the samples.</td></tr>
+ <tr><td>Tests</td><td>Builds the tests.</td></tr>
</table>
</li>
</ol>
@@ -218,7 +230,7 @@
</ul>
<p>Regardless of which method you choose, a message file containing
translated messages in the
language of your choice must be provided. The standard message file
provided in the &xslt4c;
- version 1.7 source package is in XML Localization Interchange File Format
(XLIFF) format
+ version 1.8 source package is in XML Localization Interchange File Format
(XLIFF) format
and conforms to the XLIFF 1.1 standard (please see
<jump
href="http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm";>
http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm</jump>
for more
@@ -229,26 +241,24 @@
as shown above for building in Unix or Windows but with a small
change.</p>
<p>For building on Windows platform with "In Memory" method:</p>
<ol>
+ <li>Create the environment variable XERCESCROOT and set it to the path to
the root of &xml4c;.</li>
+ <li>Create the environment variable ICUROOT and set it to the path to the
ICU root.</li>
<li>Open the Xalan.dsw workspace using Microsoft Visual C++. The "inmem"
localization method should be configured by default.</li>
<li>Select the Localization project, and go to Settings and click on the
"General" tab.Verify
the build command line to use "nmake /f BuildMessages.mak TYPE=inmem
LOCAL=en_US"</li>
- <li>Add the Xerces-C bin directory to the PATH </li>
- <li>Add the Xerces-C lib directory to the library directory list </li>
- <li>Add the Xerces-C include directory to the include directory list.
</li>
<li>Run "Build all" with the configuration of your choice. </li>
</ol>
<p>For building on the Windows platform with ICU method:</p>
<ol>
+ <li>Create the environment variable XERCESCROOT and set it to the path to
the root of &xml4c;.</li>
+ <li>Create the environment variable ICUROOT and set it to the path to the
ICU root.</li>
<li>Open the XalanICU.dsw workspace using Microsoft Visual C++. </li>
<li>Select the AllInOneWithICU project, and ensure that the project
depends on the LocalizationWithICU
project. </li>
<li>Select the LocalizationWithICU project, and go to Settings and click
on the "General" tab. Modify
the build command line to use "nmake /f BuildMessages.mak TYPE=icu
LOCAL=en_US"</li>
- <li>Add the Xerces-C bin directory and ICU bin directory to the PATH </li>
- <li>Add the Xerces-C lib directory and ICU lib directory to the library
directory list </li>
- <li>Add the Xerces-C include directory and ICU include directory to the
include directory list </li>
<li>Open the tools.ini file under Projects\Win32\VC6\Utils\Localization
and add the ICU root
- directory to the ICUROOT variable setting. Another option is to define
ICUROOT as an environmental variable. </li>
+ directory to the ICUROOT variable setting.</li>
<li>Run "Build all" with the configuration of your choice. </li>
</ol>
<p>For building on the Unix platform:</p>
@@ -257,11 +267,11 @@
<li>Run the runConfigure and provide the platform, C compiler, C++
compiler, the message locale
system flavour you are intending to build, and the locale
support.<br/><br/>
Example 1: to use the NLS method for localization support using the
default locale en_US:<br/><br/>
- <ref>AIX (32-bit):</ref> <code>./runConfigure -p aix -c xlc -x
xlC -m nls</code><br/><br/>
- <ref>AIX (64-bit):</ref> .<code>/runConfigure -p aix -c xlc -x
xlC -b 64 -m nls</code><br/><br/>
+ <ref>AIX (32-bit):</ref> <code>./runConfigure -p aix -c xlc_r
-x xlC -m nls</code><br/><br/>
+ <ref>AIX (64-bit):</ref> .<code>/runConfigure -p aix -c xlc_r
-x xlC_r -b 64 -m nls</code><br/><br/>
Example 2: to use the 'icu' method for localization support using the
locale fr_FR:<br/><br/>
- <ref>AIX (32-bit):</ref> <code>./runConfigure -p aix -c xlc -x
xlC -m icu -M fr_Fr</code><br/><br/>
- <ref>AIX (64-bit):</ref> <code>./runConfigure -p aix -c xlc -x
xlC -b 64 -m icu -M fr_Fr</code><br/><br/>
+ <ref>AIX (32-bit):</ref> <code>./runConfigure -p aix -c xlc_r
-x xlC_r -m icu -M fr_Fr</code><br/><br/>
+ <ref>AIX (64-bit):</ref> <code>./runConfigure -p aix -c xlc_r
-x xlC_r -b 64 -m icu -M fr_Fr</code><br/><br/>
</li>
<li>Perform steps 7 and 8 as outlined under "Steps for doing a UNIX
Build" </li>
</ol>
@@ -269,10 +279,10 @@
will be stored in the directory &xslt4c-unix_root;/bin.<br/><br/>
<table>
<tr><th>Localization Build Type</th><th>File Name</th></tr>
- <tr><td><ref>ICU or "in memory" method:</ref></td><td>libxalanMsg17.so
(for UNIX)<br/>
- XalanMessages_1_8_0.dll and XalanMessages_1_8_0.lib (for Windows)
+ <tr><td><ref>ICU or "in memory" method:</ref></td><td>libxalanMsg18.so
(for UNIX)<br/>
+ XalanMessages_1_8.dll and XalanMessages_1_8.lib (for Windows)
</td></tr>
- <tr><td><ref>NLS method:</ref></td><td>xalanMsg1_7.cat can be found in
$XALANCROOT/nls/<locale_name>/ directory</td></tr>
+ <tr><td><ref>NLS method:</ref></td><td>xalanMsg1_8.cat can be found in
$XALANCROOT/nls/<locale_name>/ directory</td></tr>
</table>
</p>
<p>The location of the message library, &xslt4c; and &xml4c; binaries
need to be added to the PATH and
@@ -290,9 +300,24 @@
<li>For an NLS build, the message catalog will need to be added to the
NLSPATH. </li>
</ul>
</s3>
+ <anchor name="xercesdepdom"/>
+ <s3 title="Steps for doing a Build with Xerces Deprecated DOM Support">
+ <p>If you application is dependent on the XercesBridge classes to
interface with the deprecated Xerces DOM, then the following steps must be
taken.</p>
+ <p>For a Windows build using Microsoft Visual C++ version 6.0:</p>
+ <ol>
+ <li>Open the Xalan.dsw workspace</li>
+ <li>Go to "Projects" and select "Settings". From the "Project Settings
panel", highlight the AllInOne project.</li>
+ <li>Click on the "C/C++" tab on the right hand side. From the "Category"
pull down menu, scroll down to find "Preprocessor" and click to highlight this
category.</li>
+ <li>Under the "Preprocessor Definitions" box, add
"XALAN_BUILD_DEPRECATED_DOM_BRIDGE" to the list of definitions.</li>
+ <li>Rebuild &xslt4c; as described under <link anchor="win32">"Steps for
doing a Windows Build"</link></li>
+ </ol>
+ <p>For a UNIX build, the following parameter should be added to your
runConfigure step: <code>-z -DXALAN_BUILD_DEPRECATED_DOM_BRIDGE</code>. for
example,</p>
+ <code>./runConfigure -p aix -c xlc_r -x xlC_r -z
-DXALAN_BUILD_DEPRECATED_DOM_BRIDGE</code><br/><br/>
+
+ </s3>
<anchor name="samples"/>
<s3 title="Rebuilding a Sample application">
- <p>In the Windows32 distribution, all of the sample applications can be
built from the Xalan.dsw Visual C++ workspace.</p>
+ <p>In the 32-bit Windows distribution, all of the sample applications can
be built from the Xalan.dsw Visual C++ workspace.</p>
<p>The Makefile that come with the UNIX distributions include targets for
rebuilding one or all of the sample applications . To rebuild one or more
sample applications, go to the root directory of your source package or the
samples directory of your binary package, and run<br/><br/>
<code>gmake <ref>Target</ref></code><br/><br/>
where <ref>Target</ref> is <code>Samples</code> (all the samples),
<code>ApacheModuleXSLT</code>, <code>CompileStylesheet</code>,
<code>DocumentBuilder</code>, <code>ExternalFunctions</code>,
<code>ParsedSourceWrappers</code>, <code>SerializedNodeSet</code>,
<code>SimpleTransform</code>, <code>SimpleXPathAPI</code>,
<code>SimpleXPathCAPI</code>, <code>StreamTransform</code>,
<code>ThreadSafe</code> (Windows only), <code>TraceListen</code>,
<code>TransformToXercesDOM</code>, <code>UseStylesheetParam</code>,
<code>XPathWrapper</code>, <code>XalanTransform</code>, or
<code>XalanTransformerCallback</code>.</p>
1.43 +3 -3 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.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- samples.xml 26 Feb 2004 22:24:07 -0000 1.42
+++ samples.xml 26 Apr 2004 19:24:56 -0000 1.43
@@ -55,7 +55,7 @@
<note> Each sample application looks for input files in the current
directory, the directory from
which you run the application. The input files are in the samples
subdirectory along with the sample source
files. For the UNIX builds, application executables are in the bin
subdirectory. For the Windows32 build, the
- application executable is in the build subdirectory
(&xslt4c-dist;-<my_Windows_distribution>\Build\Win32\VC6\ Debug and
Release). To run a sample, be sure the
+ application executable is in the bin subdirectory
(&xslt4c-dist;-<my_Windows_distribution>\bin). To run a sample, be sure
the
executable is on the path, and run it from the samples subdirectory
that contains the input files.</note>
</s2><anchor name="xalantransform"/>
<s2 title="XalanTransform">
@@ -98,7 +98,7 @@
<s2 title="XalanTransformerCallback">
<p>What it does: Return transformation output in blocks to a callback
function, which writes the output to a file.
This sample illustrates the use of a callback function to incrementally
process a transformation result, that is to begin
- working with the transformation result before the transformation has beeen
completed. See <link idref="usagepatterns"
+ working with the transformation result before the transformation has been
completed. See <link idref="usagepatterns"
anchor="incremental">Processing output incrementally</link>.</p>
<p>You can run it from the XalanTransformerCallback subdirectory with</p>
<p><code>XalanTransformerCallback foo.xml foo.xsl [foo.out]</code></p>
@@ -277,7 +277,7 @@
/usr/lib; see <link idref="getstarted" anchor="path">Setting up the
path/library path</link>), and copy the Apache module to
/usr/lib/apache.<br/><br/></li>
<li>Add LoadModule and (UNIX only) AddModule entries to the Apache
configuration file: httpd.conf.<br/><br/>
- Windows: <code>LoadModule xslt_module
&xslt4c-dist;-<my_Windows_distribution>\Build\Win32\VC6\Release\ApacheModuleXSLT.dll</code><br/><br/>
+ Windows: <code>LoadModule xslt_module
&xslt4c-dist;-<my_Windows_distribution>\bin\ApacheModuleXSLT.dll</code><br/><br/>
UNIX: <code>AddModule mod_xslt.c</code><br/>
and<br/>
<code>LoadModule
xslt_module /usr/lib/apache/mod_xslt.<ref>xx</ref></code><br/><br/>
1.45 +6 -14 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.44
retrieving revision 1.45
diff -u -r1.44 -r1.45
--- usagepatterns.xml 12 Apr 2004 15:24:17 -0000 1.44
+++ usagepatterns.xml 26 Apr 2004 19:24:56 -0000 1.45
@@ -119,7 +119,7 @@
Whilst you can use the standard C++ namespace syntax directly,
the &xml4c; and &xslt4c; namespaces are linked to the version
number. For example, the Xalan namespace is currently
- <em>xalanc_1_7</em>. The macros will automatically take care
+ <em>xalanc_1_8</em>. The macros will automatically take care
of this when code is re-compiled against a new version of the
libraries. Using the namespaces directly will require each
namespace related statement be updated by hand.
@@ -277,8 +277,6 @@
the string expression (in single quotes). For example:
</p>
<p><code>Xalan -p param1 'boo' foo.xml foo.xsl</code></p>
- <p>or</p>
- <p><code>testXSLT -in foo.xml -xsl foo.xsl -param param1
'boo'</code></p>
<p>
If the string expression includes spaces or other characters that
the shell intercepts, first enclose the string in single quotes
@@ -287,12 +285,6 @@
a single argument. For example:
</p>
<p><code>Xalan -p "'hello there'" foo.xml foo.xsl</code></p>
- <p>or</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
@@ -524,7 +516,7 @@
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" anchor="testxslt">testXSLT command-line
utility</link> and TraceListen both use TraceListenerDefault to write events to
the screen.
+ The TraceListen uses TraceListenerDefault to write events to the
screen.
</p>
</s2>
<anchor name="icu"/>
@@ -553,8 +545,8 @@
developerWorks open source zone.<br/><br/></li>
<li>Do an ICU 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>
+ <br/><em>Important</em> For Windows, define the environment
variable ICUROOT and then restart Visual C++ or Visual Studio .NET.
+ in order for the ICUROOT variable to take effect.<br/><br/></li>
</ol>
<anchor name="icusupport"/>
<s3 title="Enabling ICU support for encoding">
@@ -571,7 +563,7 @@
want to enable ICU support:
</p>
<ol>
- <li>Include the ICUBridge headers.<br/><br/></li>
+ <li>Define the environment variable ICUROOT.<br/><br/></li>
<li>Substitute ICU support for format-number(), xsl:number,
and/or xsl:sort.<br/><br/></li>
<li>Rebuild the Xalan library to include the ICUBridge.</li>
</ol>
@@ -585,7 +577,7 @@
#include <xalanc/ICUBridge/ICUXalanNumberFormatFactory.hpp>
#include <xalanc/ICUBridge/ICUBridgeCollationCompareFunctor.hpp>
</source>
- <p>For Windows, do a clean build of the Xalan library using the
"AllInOneWithICU" project.</p>
+ <p>For Windows, do a clean build of the Xalan library using the
"XalanICU.dsw" workspace (for Visual C++ users) or "XalanICU.sln" solution (for
Visual Studio .NET users).</p>
<p>For UNIX:</p>
<ol>
<li>Define the XALAN_USE_ICU environment
variable.<br/><br/></li>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
