dbertoni 2004/01/06 21:28:39
Modified: c build.xml
c/xdocs DoxyfileXalan
c/xdocs/sources entities.ent xalan.xml xalanLocal.xml
c/xdocs/sources/xalan STATUS commandline.xml extensions.xml
extensionslib.xml faq.xml getstarted.xml
history.xml index.xml readme.xml resources.xml
samples.xml usagepatterns.xml
Log:
Patch for Bugzilla 25176.
Revision Changes Path
1.15 +5 -5 xml-xalan/c/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/build.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- build.xml 5 Aug 2003 15:17:53 -0000 1.14
+++ build.xml 7 Jan 2004 05:28:38 -0000 1.15
@@ -2,10 +2,10 @@
<property name="name" value="xalan"/>
<property name="Name" value="Xalan-C++"/>
- <property name="year" value="2003"/>
+ <property name="year" value="2004"/>
<property name="version.VERSION" value="1"/>
- <property name="version.RELEASE" value="6"/>
+ <property name="version.RELEASE" value="7"/>
<property name="version.MINOR" value="0"/>
<property name="xdocs.dir" value="./xdocs"/>
@@ -42,7 +42,7 @@
</target>
- <target name="docs" depends="prepare">
+ <target name="docs" depends="prepare, apidocs">
<java fork="yes" classname="${doc.generator}"
classpath="${java.class.path}">
<arg line="targetDirectory=${build.docs} ${xdocs.book}
${xdocs.style}"/>
</java>
@@ -52,7 +52,7 @@
<copy todir="${build.apidocs}">
<fileset dir="${xdocs.apidocs}"/>
</copy>
- <exec executable="doxygen.exe" dir="${xdocs.dir}">
+ <exec executable="doxygen" dir="${xdocs.dir}">
<arg value="DoxyfileXalan"/>
</exec>
</target>
@@ -130,7 +130,7 @@
<gzip src="${src.package.name}.tar"
zipfile="${src.package.name}.tar.gz"/>
<delete file="${src.package.name}.tar"/>
- <!-- this rule is not picking up the CVS directories -- anybody know how
to fix? -->
+ <!-- this rule is not picking up the CVS directories dd anybody know how
to fix? -->
<zip zipfile="${src.package.name}.zip" basedir="../.."
includes="xml-xalan/**" excludes="xml-xalan/c/build/** xml-xalan/c/xml-site/**"
defaultexcludes="no"/>
</target>
1.15 +4 -4 xml-xalan/c/xdocs/DoxyfileXalan
Index: DoxyfileXalan
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/DoxyfileXalan,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- DoxyfileXalan 16 Jul 2003 16:17:25 -0000 1.14
+++ DoxyfileXalan 7 Jan 2004 05:28:38 -0000 1.15
@@ -31,7 +31,7 @@
# If a relative path is entered, it will be relative to the location
# where doxygen was started. If left blank the current directory will be
used.
-OUTPUT_DIRECTORY = ../Build
+OUTPUT_DIRECTORY = ../build/docs
# The OUTPUT_LANGUAGE tag is used to specify the language in which all
# documentation generated by doxygen is written. Doxygen will use this
@@ -146,7 +146,7 @@
# classes or files whose names only differ in case and if your file system
# supports case sensitive file names.
-CASE_SENSE_NAMES = NO
+CASE_SENSE_NAMES = YES
# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
# will generate a verbatim copy of the header file for each class for
@@ -204,7 +204,7 @@
# directories like "/usr/src/myproject". Separate the files or directories
# with spaces.
-INPUT = ../src/xalanc/DOMSupport ../src/xalanc/ICUBridge
../src/xalanc/Include ../src/xalanc/PlatformSupport ../src/xalanc/TestXSLT
../src/xalanc/XalanDOM ../src/xalanc/XalanSourceTree
../src/xalanc/XalanTransformer ../src/xalanc/XercesParserLiaison
../src/xalanc/XMLSupport ../src/xalanc/XPath ../src/xalanc/XSLT
../src/xalanc/XalanExtensions ../src/xalanc/XalanExe ../src/xalanc/XPathCAPI
../src/xalanc/XalanEXSLT
+INPUT = ../src/xalanc/DOMSupport ../src/xalanc/ICUBridge
../src/xalanc/Include ../src/xalanc/PlatformSupport ../src/xalanc/TestXSLT
../src/xalanc/XalanDOM ../src/xalanc/XalanSourceTree
../src/xalanc/XalanTransformer ../src/xalanc/XercesParserLiaison
../src/xalanc/XercesParserLiaison/Deprecated ../src/xalanc/XMLSupport
../src/xalanc/XPath ../src/xalanc/XSLT ../src/xalanc/XalanExtensions
../src/xalanc/XalanExe ../src/xalanc/XPathCAPI ../src/xalanc/XalanEXSLT
# If the value of the INPUT tag contains directories, you can use the
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
@@ -272,7 +272,7 @@
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `html' will be used as the default path.
-HTML_OUTPUT = docs/apiDocs
+HTML_OUTPUT = apiDocs
# The HTML_HEADER tag can be used to specify a personal HTML header for
# each generated HTML page. If it is left blank doxygen will generate a
1.32 +84 -22 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.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- entities.ent 6 Jan 2004 02:41:48 -0000 1.31
+++ entities.ent 7 Jan 2004 05:28:38 -0000 1.32
@@ -57,31 +57,93 @@
-->
<!ENTITY xslt4c "Xalan-C++">
-<!ENTITY xslt4c-dist "Xalan-C_1_6">
-<!ENTITY xslt4c-current "Xalan-C++ version 1.6">
-<!ENTITY xslt4c-windll "Xalan-C_1_6_0.dll">
-<!ENTITY xslt4c-linuxlib "libxalan-c1_6.so">
-<!ENTITY xslt4c-aixlib "libxalan-c1_6.so">
-<!ENTITY xslt4c-hplib "libxalan-c1_6.sl">
-<!ENTITY xslt4c-solarislib "libxalan-c1_6.so">
+<!ENTITY xslt4c-dist "Xalan-C_1_7">
+<!ENTITY xslt4c-current "Xalan-C++ version 1.7">
+<!ENTITY xslt4c-windll "Xalan-C_1_7_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 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">
+<!ENTITY hpux11a_64-dist "-hpux_11_64-acc_a03">
+<!ENTITY hpux11c-dist "-hpux_11-acc_c03">
+<!ENTITY hpux11c_64-dist "-hpux_11_64-acc_c03">
+<!ENTITY hpux11i-dist "-hpux_11i-acc_c03">
+<!ENTITY hpux11i_64-dist "-hpux_11i_64-acc_c03">
+<!ENTITY solaris_27-dist "-solaris_27-cc_62">
+<!ENTITY solaris_27_64-dist "-solaris_27_64-cc_62">
+<!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-ecc_71">
+<!ENTITY winnt-dist "-windows_nt-msvc_60">
+<!ENTITY win2k-dist "-windows_2000-msvc_60">
+<!ENTITY winxp-dist "-windows_xp-msvc_60">
+<!ENTITY win_ext ".zip">
+<!ENTITY unix_ext ".tar.gz">
+
+<!ENTITY xslt4c-aix43v5-dist "&xslt4c-dist;&aix43v5-dist;&unix_ext;">
+<!ENTITY xslt4c-aix51v5-dist "&xslt4c-dist;&aix51v5-dist;&unix_ext;">
+<!ENTITY xslt4c-aix51v5_64-dist "&xslt4c-dist;&aix51v5_64-dist;&unix_ext;">
+<!ENTITY xslt4c-aix51v6-dist "&xslt4c-dist;&aix51v6-dist;&unix_ext;">
+<!ENTITY xslt4c-aix51v6_64-dist "&xslt4c-dist;&aix51v6_64-dist;&unix_ext;">
+<!ENTITY xslt4c-hpux11a-dist "&xslt4c-dist;&hpux11a-dist;&unix_ext;">
+<!ENTITY xslt4c-hpux11a_64-dist "&xslt4c-dist;&hpux11a_64-dist;&unix_ext;">
+<!ENTITY xslt4c-redhat72_icc-dist
"&xslt4c-dist;&redhat_72_icc-dist;&unix_ext;">
+<!ENTITY xslt4c-redhat72_ecc-dist
"&xslt4c-dist;&redhat_72_ecc-dist;&unix_ext;">
+<!ENTITY xslt4c-solaris27-dist "&xslt4c-dist;&solaris_27-dist;&unix_ext;">
+<!ENTITY xslt4c-solaris27_64-dist
"&xslt4c-dist;&solaris_27_64-dist;&unix_ext;">
+<!ENTITY xslt4c-suse72_zOS-dist "&xslt4c-dist;&suse_72_zOS-dist;&unix_ext;">
+<!ENTITY xslt4c-suse81_IA-dist "&xslt4c-dist;&suse_81_IA-dist;&unix_ext;">
+<!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-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.3.0">
-<!ENTITY xml4c-dist "xerces-c2_3_0">
-<!ENTITY xml4c-windll "xerces-c_2_3_0.dll">
+<!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-winlib "xerces-c_2.lib">
-<!ENTITY xml4c-linuxlib "libxerces-c2_3_0.so">
-<!ENTITY xml4c-aixlib "libxerces-c2_3_0.a">
-<!ENTITY xml4c-hplib "libxerces-c2_3_0.sl">
-<!ENTITY xml4c-solarislib "libxerces-c2_3_0.so">
-<!ENTITY xml4c-linuxdist "&xml4c-dist;-linux7.2Proton.tar.gz">
-<!ENTITY xml4c-aixdist "&xml4c-dist;-AIX51_6.00.tar.gz">
-<!ENTITY xml4c-aix64dist "&xml4c-dist;-AIX51_6.00_64.tar.gz">
-<!ENTITY xml4c-hpdist "&xml4c-dist;-HP11ACC.tar.gz">
-<!ENTITY xml4c-hp64dist "&xml4c-dist;-HP11ACC_64.tar.gz">
-<!ENTITY xml4c-solarisdist "&xml4c-dist;-Sol2.7ForCC.tar.gz">
-<!ENTITY xml4c-solaris64dist "&xml4c-dist;-Sol2.7ForCC_64.tar.gz">
+<!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-aix43v5-dist "&xml4c-dist;&aix43v5-dist;&unix_ext;">
+<!ENTITY xml4c-aix51v5-dist "&xml4c-dist;&aix51v5-dist;&unix_ext;">
+<!ENTITY xml4c-aix51v6-dist "&xml4c-dist;&aix51v6-dist;&unix_ext;">
+<!ENTITY xml4c-aix51v5_64-dist "&xml4c-dist;&aix51v5_64-dist;&unix_ext;">
+<!ENTITY xml4c-aix51v6_64-dist "&xml4c-dist;&aix51v6_64-dist;&unix_ext;">
+<!ENTITY xml4c-hpux11a-dist "&xml4c-dist;&hpux11a-dist;&unix_ext;">
+<!ENTITY xml4c-hpux11a_64-dist "&xml4c-dist;&hpux11a_64-dist;&unix_ext;">
+<!ENTITY xml4c-redhat72_icc-dist
"&xml4c-dist;&redhat_72_icc-dist;&unix_ext;">
+<!ENTITY xml4c-redhat72_ecc-dist
"&xml4c-dist;&redhat_72_ecc-dist;&unix_ext;">
+<!ENTITY xml4c-redhat80_gcc-dist
"&xml4c-dist;&redhat_80_gcc-dist;&unix_ext;">
+<!ENTITY xml4c-solaris27-dist "&xml4c-dist;&solaris_27-dist;&unix_ext;">
+<!ENTITY xml4c-solaris27_64-dist
"&xml4c-dist;&solaris_27_64-dist;&unix_ext;">
+<!ENTITY xml4c-suse72_zOS-dist "&xml4c-dist;&suse_72_zOS-dist;&unix_ext;">
+<!ENTITY xml4c-suse81_IA-dist "&xml4c-dist;&suse_81_IA-dist;&unix_ext;">
+<!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 xslt4j "Xalan-Java">
-<!ENTITY icu-used "International Components for Unicode(ICU) 2.4 source
files">
+<!ENTITY icu-used "International Components for Unicode(ICU) 2.6.1 source
files">
<!ENTITY icu-windlls "icui18n.dll, icuuc.dll">
<!ENTITY icubridge-win "ICUBridge.dll">
<!ENTITY done SYSTEM "xalan/DONE">
1.15 +4 -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.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- xalan.xml 6 Jan 2004 02:41:48 -0000 1.14
+++ xalan.xml 7 Jan 2004 05:28:38 -0000 1.15
@@ -67,13 +67,11 @@
<separator/>
<document id="index"
- label="Xalan-C++ 1.6"
+ label="Xalan-C++ 1.7"
source="xalan/index.xml"/>
<separator/>
- <external href="getstarted.html#download" label="Downloads"/>
-
<document id="overview"
label="Overview"
source="xalan/overview.xml"/>
@@ -120,8 +118,11 @@
<document id="readme"
label="Release Notes"
source="xalan/readme.xml"/>
+ <external href="getstarted.html#download" label="Downloads"/>
+
<separator/>
+<external href="http://cvs.apache.org/viewcvs.cgi/xml-xalan/c";
label="CVS Repository"/>
<external href="readme.html#bugs" label="Bugs"/>
1.9 +4 -3 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.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- xalanLocal.xml 6 Jan 2004 02:41:48 -0000 1.8
+++ xalanLocal.xml 7 Jan 2004 05:28:38 -0000 1.9
@@ -68,8 +68,6 @@
<separator/>
- <external href="getstarted.html#download" label="Downloads"/>
-
<document id="getstarted"
label="Getting Started"
source="xalan/getstarted.xml"/>
@@ -109,9 +107,12 @@
<document id="readme"
label="Release Notes"
source="xalan/readme.xml"/>
+ <external href="getstarted.html#download" label="Downloads"/>
+
<separator/>
-
+ <external href="http://cvs.apache.org/viewcvs.cgi/xml-xalan/c";
label="CVS Repository"/>
+
<external href="readme.html#bugs" label="Bugs"/>
<external href="http://xml.apache.org/xalan-j/test/run.html#how-to-run-c";
label="Testing"/>
1.16 +3 -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.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- STATUS 28 Jul 2003 21:46:29 -0000 1.15
+++ STATUS 7 Jan 2004 05:28:38 -0000 1.16
@@ -6,9 +6,11 @@
</s3><anchor name="to-do"/>
<s3 title="To-do tasks for future &xslt4c; releases">
<ul>
+ <li>Pluggable Memory Management<br/><br/></li>
+ <li>Add EXSLT functionality<br/><br/></li>
+ <li>Support for XSLT 2.0 and XPath 2.0<br/><br/></li>
<li>Add support for extension elements<br/><br/></li>
<li>Fix any conformance bugs we or our users find<br/><br/></li>
- <li>Expand the XalanTransformer simplified API.<br/><br/></li>
</ul>
<p>Watch the <human-resource-ref idref="xalandev"/> for more information
and for ideas about how you can get involved.</p>
</s3>
1.28 +3 -87 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.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- commandline.xml 6 Jan 2004 02:41:48 -0000 1.27
+++ commandline.xml 7 Jan 2004 05:28:38 -0000 1.28
@@ -63,19 +63,15 @@
<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="testxslt">Using TestXSLT</link></li>
-<li><link anchor="icu">Enabling ICU support for the Xalan executable and/or
testXSLT</link></li>
</ul><anchor name="use"/>
<s2 title="Using a command-line utility">
<p>To perform a transformation, you can call &xslt4c; from the command line
(or script),
or from within an application (see <link idref="usagepatterns">Usage
Patterns</link>).</p>
-<p>To perform a transformation from the command line or a script, you can
use Xalan or testXSLT. The testXSLT executable has been around since the
inception of &xslt4c; and supports a variety of options. The Xalan executable
is newer, simpler to use, and supports fewer options.</p>
-<p>To perform a transformation from the command line or a script with either
executable,
- do the following:</p>
+<p>To perform a transformation from the command line or a script, do the
following:</p>
<ol>
<li><link idref="getstarted" anchor="download">Download
&xslt4c;</link>.<br/><br/></li>
<li><link idref="getstarted" anchor="path">Set the path/library
path</link> to include the Xalan executable and the Xalan and Xerces
libraries.<br/><br/></li>
- <li>Call the executable with the appropriate flags and arguments
(described below).</li>
+ <li>Call the Xalan executable with the appropriate flags and arguments
(described below).</li>
</ol>
</s2><anchor name="xalanexe"/>
<s2 title="Using the Xalan executable">
@@ -97,85 +93,5 @@
</table>
<p>To display a list of the options call the Xalan executable as
follows:</p>
<p><code>Xalan -?</code></p>
-</s2><anchor name="testxslt"/>
-<s2 title="Using TestXSLT">
- <p>Call the testXSLT executable with the flags and arguments described
below. The following command line, for example, includes the -IN, -XSL, and
-OUT flags with their accompanying arguments -- the XML source document, the XSL
- stylesheet, and the output file:<br/><br/>
- <code>testXSLT -IN foo.xml -XSL foo.xsl -OUT foo.out</code></p>
- <p>The testXSLT executable can take the following flags and arguments
(the flags are case insensitive):</p>
- <source>-IN inputXMLURL
--XSL XSLTransformationURL
--OUT outputFileName
--H (Display list of command-line options)
--? (Display list of command-line options)
--V (Version info)
--QC (Quiet Pattern Conflicts Warnings)
--Q (Quiet Mode)
--INDENT (Number of spaces to indent each level in output tree --default is 0)
--VALIDATE (Validate the XSL and XML input -- default is not to validate)
--TT (Trace the templates as they are being called)
--TG (Trace each result tree generation event)
--TS (Trace each selection event)
--TTC (Trace the template children as they are being processed)
--XML (Use XML formatter and add XML header)
-The -XML flag must be set:
- -NH (Don't write XML header)
--HTML (Use HTML formatter)
-The -HTML flag must be set:
- -NOINDENT (turns off HTML indenting)
-The -XML or -HTML flag must be set:
- -STRIPCDATA (Strip CDATA sections of their brackets, but do not
escape)
- -ESCAPECDATA (Strip CDATA sections of their brackets, and escape)
--TEXT (Use simple Text formatter)
--DOM (Test for well-formed output --format to DOM then to XML for output)
--XST (Format to Xalan source tree, then to XML for output)
--XD (Use Xerces DOM instead of Xalan source tree)
--DE Disable built-in extension functions)
--EN (Specify the namespace URI for Xalan extension functions; the default
- is 'http://xml.apache.org/xslt')
--PARAM name expression (Set a stylesheet parameter)</source>
- <p>Use -IN to specify the XML source document.</p>
- <p>Use -XSL to specify the XSL stylesheet file.</p>
- <p>Use -DE not to load the standard set of <link
idref="extensionslib">extension functions</link>.</p>
- <p>Use -TEXT if you want the output to include only text nodes without
any escaping.</p>
- <p>Use -HTML to write 4.0 transitional HTML (some elements, such as
<br>, are
- not well formed XML).</p>
- <p>To set stylesheet parameters from the command line, use <br/>
- <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 the Xalan executable and/or
testXSLT">
- <p>You can set up the <resource-ref idref="icu"/> to enhance the
support that &xslt4c; provides for encoding, number
- formatting, and sorting. For more information, see <link
idref="usagepatterns" anchor="icu">Using the ICU</link>.</p>
- <p>If you have built and integrated the ICU with &xml4c;, Xalan and
testXSLT (like any &xslt4c; application) automatically uses ICU
- support for output encoding. See <resource-ref
idref="xerces-build-icu"/>.</p>
- <p>The Xalan executable depends on the use of an ICU-enabled Xalan
library for number formatting and sorting (see below). The testXSLT
executable conditionally includes ICU support for number formatting and
sorting. For testXSLT, look in process.cpp for the
- <code>#if defined(XALAN_USE_ICU)</code> blocks. These blocks #include
the ICUBridge headers, and
- substitutes ICU support for xsl:number, format-number(), and xsl:sort.
To activate this support:</p>
- <ol>
- <li>Download and build the ICU (see <link idref="usagepatterns"
anchor="icu">Using the ICU</link>).<br/><br/></li>
- <li>Rebuild Xalan and or testXSLT with the ICU enabled (see
below).</li>
- </ol>
- <s3 title="Rebuilding Xalan and/or TestXSLT in Windows">
- <ol>
- <li>For Windows, the ICUBridge is part of the Xalan library. Build
an ICU-enabled Xalan library using the AllInOneWithICU project.<br/><br/></li>
- <li>For TestXSLT, uncomment "#define XALAN_USE_ICU" in
process.cpp.<br/><br/></li>
- <li>Build Xalan.exe and/or TestXSLT.exe.</li>
- </ol>
- </s3>
- <s3 title="Rebuilding Xalan and/or testXSLT in UNIX">
- <p>In the Linux, AIX, HP-UX 11, and Solaris builds, the ICUBridge is in
the core Xalan library (&xslt4c-linuxlib; in Linux; &xslt4c-aixlib; in
- AIX; &xslt4c-hplib; in HP-UX 11; &xslt4c-solarislib; in Solaris ), so
you must rebuild this library along with Xalan and/or testXSLT.</p>
- <p>Before you do the build, define the XALAN_USE_ICU environment
variable. For information about defining this
- environment variable and doing a build, see <link idref="readme"
anchor="unix">Steps for doing a
- UNIX build</link>.</p>
- <note>The make file uses the XALAN_USE_ICU environment variable to do
the equivalent of a #define and to add
- ICUBridge to the list of dependencies for testXSLT. If you uncomment
the <code>#define XALAN_USE_ICU</code>
- statement in process.cpp (which is the right thing to do in Windows),
you will get an error in AIX ("The
- macro 'XALAN_USE_ICU' has already been defined"), an error in HP-UX 11
("Redefinition of macro 'XALAN_USE_ICU'
- differs from previous definition"), or a warning in Linux or Solaris
about duplicate settings when you
- run the make, and testXSLT does not link with ICUBridge.</note>
- </s3>
- </s2>
+</s2>
</s1>
1.21 +1 -1 xml-xalan/c/xdocs/sources/xalan/extensions.xml
Index: extensions.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/extensions.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- extensions.xml 6 Jan 2004 02:41:48 -0000 1.20
+++ extensions.xml 7 Jan 2004 05:28:38 -0000 1.21
@@ -65,7 +65,7 @@
<li><link anchor="use">Using an extension function</link></li>
</ul><anchor name="intro"/>
<s2 title="Introduction">
-<p>At times, you may want to call your own custom C functions from a
stylesheet. For these situations, &xslt4c; supports the creation and use of
extension functions. &xslt4c; also provides a <link
idref="extensionslib">library of extension functionss</link> for your use.</p>
+<p>At times, you may want to call your own custom C functions from a
stylesheet. For these situations, &xslt4c; supports the creation and use of
extension functions. &xslt4c; also provides a <link
idref="extensionslib">library of extension functions</link> for your use.</p>
<p>You can think of extension functions as extending the core library of
functions that XPath provides. Like the
XPath functions, an extension function returns an XObject, which may contain
a value of any of the five XSLT
data types: node-set, result-tree-fragment, string, boolean, or number.</p>
1.8 +5 -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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- extensionslib.xml 6 Jan 2004 02:41:48 -0000 1.7
+++ extensionslib.xml 7 Jan 2004 05:28:38 -0000 1.8
@@ -77,7 +77,7 @@
</s2><anchor name="exslt"/>
<s2 title="EXSLT extensions">
<p>&xslt4c; supports the <jump href="http://exslt.org/";>EXSLT</jump>
initiative to provide a set of
-standard extension functions to XSLT users. &xslt4c; 1.5 includes beta
implementations for
+standard extension functions to XSLT users. &xslt4c; includes beta
implementations for
functions in four of the EXSLT namespaces (some are calls to extension
already in the Xalan namespace).</p>
<p>The source files for the implementations are in the XalanEXSLT
subdirectory of the source tree.
See</p>
@@ -86,6 +86,8 @@
<li><jump
href="apidocs/XalanEXSLTMathImpl.hpp.html">XalanEXSLTMathImpl</jump></li>
<li><jump
href="apidocs/XalanEXSLTSetImpl.hpp.html">XalanEXSLTSetImpl</jump></li>
<li><jump
href="apidocs/XalanEXSLTStringImpl.hpp.html">XalanEXSLTStringImpl</jump></li>
+<li><jump
href="apidocs/XalanEXSLTDynamicImpl.hpp.html">XalanEXSLTDynamicImpl</jump></li>
+<li><jump
href="apidocs/XalanEXSLTDateTimeImpl.hpp.html">XalanEXSLTDateTimeImpl</jump></li>
</ul>
<p>For the function specifications, see:</p>
<ul>
@@ -93,6 +95,8 @@
<li><jump href="http://www.exslt.org/math/math.html";>EXSLT math
functions</jump></li>
<li><jump href="http://www.exslt.org/set/set.html";>EXSLT set
functions</jump></li>
<li><jump href="http://www.exslt.org/str/str.html";>EXSLT string
functions</jump></li>
+<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
at the <human-resource-ref idref="xalandev"/>.</p>
1.44 +3 -27 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.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- faq.xml 6 Jan 2004 02:41:48 -0000 1.43
+++ faq.xml 7 Jan 2004 05:28:38 -0000 1.44
@@ -106,7 +106,7 @@
Xalan, using the internal DOM implementation is the best approach.</p>
<p>In cases where you want to modify the DOM document on the fly,
-you should use the Xerces DOM as the base document. You can wrap the
+wyou should use the Xerces DOM as the base document. You can wrap the
Xerces DOM in a wrapper (see <link anchor="xercesdomwrapperparsedsource">
passing in a Xerces DOM</link>) to then use as an input to a Xalan
transformation. Alternatively you can output the result of
@@ -145,31 +145,7 @@
<faq title="Building on UNIX">
<q>What do I need to rebuild &xslt4c; on UNIX?</q>
-<a><p>To build &xslt4c; on supported UNIX platforms, you need &xml4c;, the
GNU make utility, and a supported C++ compilers (see the table below).</p>
-<p>For more details see: http://xml.apache.org/xalan-c/readme.html#unix</p>
- <table>
- <tr>
- <th>Platform - Operating System</th>
- <th>Compilers</th>
- </tr>
- <tr>
- <td>AIX 5.1</td>
- <td>IBM C and C++ for AIX 6.00</td>
- </tr>
- <tr>
- <td>Solaris 2.8</td>
- <td>Sun Workshop 6 update 2</td>
- </tr>
- <tr>
- <td>HP/UX 11.0</td>
- <td>aCC A.03.37</td>
- </tr>
- <tr>
- <td>RedHat Linux 7.2</td>
- <td>Intel C++ Compiler, version 6.0.1</td>
- </tr>
- </table>
- <p>For more details see: <link idref="readme" anchor="unix">Steps for doing
a UNIX build</link>.</p>
+<a><p>To build &xslt4c; on supported UNIX platforms, you need &xml4c;, the
GNU make utility, and a supported C++ compiler. For more details see: <link
idref="readme" anchor="unix">Steps for doing a UNIX build</link>.</p>
</a></faq>
<faq title="Make errors on UNIX platforms">
@@ -183,7 +159,7 @@
<a><p>The International Components for Unicode(ICU) is a C and C++ library
that provides robust and full-featured Unicode support on a wide variety of
platforms. &xslt4c; uses the ICU to extend support for encoding, number
formatting, and sorting.</p>
<p>The ICU is available for download from <jump
href="http://oss.software.ibm.com/icu/index.html";>http://oss.software.ibm.com/icu/index.html</jump>.</p>
-<p>This release of Xalan was tested with ICU 2.4.</p>
+<p>This release of Xalan was tested with ICU 2.6.1.</p>
<p>For more details see: <link idref="usagepatterns" anchor="icu">Using the
International Components for Unicode (ICU)</link>.</p><!--icuNote--><anchor
name="gnutar"/><p/></a>
</faq>
1.43 +151 -76 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.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- getstarted.xml 6 Jan 2004 02:41:48 -0000 1.42
+++ getstarted.xml 7 Jan 2004 05:28:38 -0000 1.43
@@ -68,59 +68,134 @@
</ul>
<anchor name="download"/>
<s2 title="Downloading what you need">
-<p>For &xslt4c-current;, we are distributing a Windows32 Visual C++ build
and 7 UNIX builds with makefiles: a Red Hat Linux GNU build, AIX xlC (32 and 64
bit) builds, HP-UX 11 aCC (32 and 64 bit) builds, and Solaris 2.7 (32 and 64
bit) builds.
-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.3.0
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 Xalan-C_1_6-docs.zip. For UNIX, documentation is packaged
with the file name of Xalan-C_1_6-docs.tar.gz.</note>
- <table>
- <tr>
- <th>Xalan distribution files</th>
- <th>Xerces distribution files</th>
- <th>Platform</th>
- </tr>
- <tr>
- <td>&xslt4c-dist;-win32.zip</td>
- <td>&xml4c-dist;-win32.zip</td>
- <td>Windows32</td>
- </tr>
- <tr>
- <td>&xslt4c-dist;-linux7.2Proton.tar.gz</td>
- <td>&xml4c-linuxdist;</td>
- <td>Redhat Linux 7.2</td>
- </tr>
- <tr>
- <td>&xslt4c-dist;-AIX51_600.tar.gz</td>
- <td>&xml4c-aixdist;</td>
- <td>AIX 5.1</td>
- </tr>
- <tr>
- <td>&xslt4c-dist;-AIX51_600_64.tar.gz</td>
- <td>&xml4c-aix64dist;</td>
- <td>AIX 5.1 (64 bit)</td>
- </tr>
- <tr>
- <td>&xslt4c-dist;-Sol2.7ForCC.tar.gz </td>
- <td>&xml4c-solarisdist;</td>
- <td>Solaris 2.7</td>
- </tr>
- <tr>
- <td>&xslt4c-dist;-Sol2.7ForCC_64.tar.gz </td>
- <td>&xml4c-solaris64dist;</td>
- <td>Solaris 2.7</td>
- </tr>
- <tr>
- <td>&xslt4c-dist;-HP11ACC.tar.gz</td>
- <td>&xml4c-hpdist;</td>
- <td>HP-UX 11.0 (32 bit)</td>
- </tr>
- <tr>
- <td>&xslt4c-dist;-HP11ACC_64.tar.gz</td>
- <td>&xml4c-hp64dist;</td>
- <td>HP-UX 11.0 (64 bit)</td>
- </tr>
- </table>
- <p>The Windows32 distribution was built with MSVC 6.0 SP3 and <jump
href="http://www.dinkumware.com/vc_fixes.html";>Dinkumware C++ library
fixes</jump>. The Red Hat Linux 7.2 32-bit distribution was built with Intel
C++ Compiler version 7.0. The AIX 5.1 32-bit and 64-bit distributions were
built with IBM C and C++ for AIX 6.00. The Solaris 2.7 32-bit and 64-bit
distributions were built with Sun Workshop 6, update 2.
-The HP-UX 11 32-bit and 64-bit distributions were built with aCC A.03.37.</p>
+<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>HP-UX 11 32-bit and 64-bit aCC builds</li>
+<li>Solaris 2.7 32-bit and 64-bit Forte C++ builds</li>
+</ul>
+</p>
+<p>New to the &xslt4c-current; binary distribution list, we are also
providing the following:
+<ul>
+<li>SuSE Linux 7.2 for S/390 32-bit gcc 2.95 build </li>
+<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>
+<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>
+ <th>Xalan distribution files</th>
+ <th>Xerces distribution files</th>
+ <th>Platform</th>
+ </tr>
+ <tr>
+ <td>&xslt4c-aix51v6-dist;</td>
+ <td>&xml4c-aix51v6-dist;</td>
+ <td>AIX 5.1 (32-bit)</td>
+ </tr>
+ <tr>
+ <td>&xslt4c-aix51v6_64-dist;</td>
+ <td>&xml4c-aix51v6_64-dist;</td>
+ <td>AIX 5.1 (64 bit)</td>
+ </tr>
+ <tr>
+ <td>&xslt4c-hpux11a-dist;</td>
+ <td>&xml4c-hpux11a-dist;</td>
+ <td>HP-UX 11.0 (32 bit)</td>
+ </tr>
+ <tr>
+ <td>&xslt4c-hpux11a_64-dist;</td>
+ <td>&xml4c-hpux11a_64-dist;</td>
+ <td>HP-UX 11.0 (64 bit)</td>
+ </tr>
+ <tr>
+ <td>&xslt4c-redhat72_icc-dist;</td>
+ <td>&xml4c-redhat72_icc-dist;</td>
+ <td>Redhat Linux 7.2 (32-bit)</td>
+ </tr>
+ <tr>
+ <td>&xslt4c-redhat72_ecc-dist;</td>
+ <td>&xml4c-redhat72_ecc-dist;</td>
+ <td>Redhat Linux 7.2 (64-bit)</td>
+ </tr>
+ <tr>
+ <td>&xslt4c-solaris27-dist;</td>
+ <td>&xml4c-solaris27-dist;</td>
+ <td>Solaris 2.7 (32-bit)</td>
+ </tr>
+ <tr>
+ <td>&xslt4c-solaris27_64-dist; </td>
+ <td>&xml4c-solaris27_64-dist;</td>
+ <td>Solaris 2.7 (64-bit)</td>
+ </tr>
+ <tr>
+ <td>&xslt4c-suse72_zOS-dist;</td>
+ <td>&xml4c-suse72_zOS-dist;</td>
+ <td>SuSE Linux 7.2 for S/390 (32-bit)</td>
+ </tr>
+ <tr>
+ <td>&xslt4c-suse81_IA-dist;</td>
+ <td>&xml4c-suse81_IA-dist;</td>
+ <td>SuSE Linux 8.1 (32-bit)</td>
+ </tr>
+ <tr>
+ <td>
+ &xslt4c-winnt-dist;<br/>
+ &xslt4c-win2k-dist;<br/>
+ &xslt4c-winxp-dist;<br/>
+ </td>
+ <td>
+ &xml4c-winnt-dist;<br/>
+ &xml4c-win2k-dist;<br/>
+ &xml4c-winxp-dist;<br/>
+ </td>
+ <td>
+ Windows NT<br/>
+ Windows 2000<br/>
+ Windows XP<br/>
+ </td>
+ </tr>
+</table>
+<p>The compiler version used for each platform is listed in the table below.
+ <table>
+ <tr>
+ <th>Platform - Operating System</th>
+ <th>Compilers</th>
+ </tr>
+ <tr>
+ <td>AIX 5.1</td>
+ <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.13</td>
+ </tr>
+ <tr>
+ <td>Red Hat Linux 7.2</td>
+ <td>Intel C++ Compiler, version 7.1</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/>
+ Intel C++ Compiler, version 7.0 (for 64-bit)</td>
+ </tr>
+ </table>
+</p>
<note>Use GNU tar to untar the Solaris distribution file; see <link
idref="faq" anchor="gnutar">A tar checksum error on Solaris </link>.</note>
<anchor name="xalandists"/>
@@ -134,42 +209,42 @@
<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>
<ul>
-<li>Put xml-xalan\c\Build\Win32\VC6\Release and &xml4c-dist;-win32\bin on
the path.</li>
+<li>Put
&xslt4c-dist;-<my_Windows_distribution>\Build\Win32\VC6\Release 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>
<ul>
- <li>Add the path to &xml4c-dist;-win32\include to the list of
directories of Include files (see the figure below).</li>
- <li>Add the path to &xml4c-dist;-win32\lib to the list of directories
of Library files (see the figure below).</li></ul>
-<p><img src="options-include.gif" alt="Visual C++ 6.0 Include
Directories"/></p>
+ <li>Add the path to
&xml4c-dist;-<my_Windows_distribution>\include to the list of directories
of Include files.</li>
+ <li>Add the path to &xml4c-dist;-<my_Windows_distribution>\lib
to the list of directories of Library files.</li>
+ </ul>
</s3><anchor name="unixpath"/>
<s3 title="For UNIX">
-<p>To use one of the UNIX distributions, you must place the Xalan executable
on the path, and the Xalan and Xerces libraries on the library path.</p>
-<p>For the &xslt4c; Linux distribution:</p>
-<ul>
-<li>Put xml-xalan/c/bin on the path (PATH).</li>
-<li>Put xml-xalan/c/lib and &xml4c-linuxdist;/lib on the library path
(LD_LIBRARY_PATH), or copy the shared libraries to /usr/lib.</li>
-</ul>
-<p>For the &xslt4c; AIX distribution:</p>
+<p>To use one of the UNIX 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 xml-xalan/c/bin on the path (PATH).</li>
-<li>Put xml-xalan/c/lib and &xml4c-aixdist;/lib on the library path
(LIBPATH), or copy the shared libraries to /usr/lib.</li>
+<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 32-bit distribution:</p>
+<p>For the &xslt4c; HP-UX 11 distributions:</p>
<ul>
-<li>Put xml-xalan/c/bin on the path (PATH).<br/><br/></li>
-<li>Put xml-xalan/c/lib and &xml4c-hpdist;/lib on the library path
(SHLIB_PATH), or copy the shared libraries to /usr/lib.</li>
+<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; HP-UX 11 64-bit distribution:</p>
+<p>For the &xslt4c; Solaris distributions:</p>
<ul>
-<li>Put xml-xalan/c/bin on the path (PATH).<br/><br/></li>
-<li>Put xml-xalan/c/lib and &xml4c-hp64dist;/lib on the library path
(SHLIB_PATH), or copy the shared libraries to /usr/lib.</li>
+<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; Solaris distribution:</p>
+<p>For the &xslt4c; RedHat and SuSE Linux distributions:</p>
<ul>
-<li>Put xml-xalan/c/bin on the path (PATH).<br/><br/></li>
-<li>Put xml-xalan/c/lib and &xml4c-linuxdist;/lib on the library path
(LD_LIBRARY_PATH), or copy the shared libraries to /usr/lib.</li>
+<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>
</s2><anchor name="samples"/>
@@ -178,7 +253,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
-xml-xalan\c\Build\Win32\VC6\Release. In the UNIX distributions, the
executables are in xml-xalan/c/bin.</li>
+&xslt4c-dist;-<my_Windows_distribution>\Build\Win32\VC6\Release. 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.9 +13 -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.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- history.xml 6 Jan 2004 02:41:48 -0000 1.8
+++ history.xml 7 Jan 2004 05:28:38 -0000 1.9
@@ -55,6 +55,19 @@
* <http://www.apache.org/>.
-->
+ <s3 title="Changes for &xslt4c; version 1.6">
+ <p>Major updates since version 1.5 include:</p>
+ <ul>
+ <li><resource-ref idref="bugsfixedforthisrelease"/>.</li>
+ <li>Directory "sane include" reorganization. A new sub-directory
called 'xalanc' has been added to the src directory (for source
distribution packages) and include directory (for binary distribution
packages). New source files which include Xalan headers will need to be
modified to include the 'xalanc' prefix in the header path.
+ For example: <br/><br/>
+ <code>#include <XPath/XObject.hpp></code><br/><br/>
+ will need to be changed to <br/><br/>
+ <code>#include <xalanc/XPath/XObject.hpp></code><br/><br/>
+ For Windows users, all project files have been modified to
reflect this change. For UNIX users, please see <link anchor="unix">Steps for
doing a UNIX build</link> for migration considerations.</li>
+ </ul>
+ </s3>
+
<s3 title="Changes for &xslt4c; version 1.5">
<p>Major updates since version 1.4 include:</p>
<ul>
1.36 +1 -1 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.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- index.xml 6 Jan 2004 02:41:48 -0000 1.35
+++ index.xml 7 Jan 2004 05:28:38 -0000 1.36
@@ -65,7 +65,7 @@
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, support for C++ namespaces, and beta support for a number of 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 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>
</s2>
<s2 title="How do I get it?">
1.49 +201 -47 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.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- readme.xml 6 Jan 2004 02:41:48 -0000 1.48
+++ readme.xml 7 Jan 2004 05:28:38 -0000 1.49
@@ -71,30 +71,43 @@
<anchor name="status"/>
<s2 title="Status">
<ul>
- <li><link anchor="done">Changes since &xslt4c; version 1.5</link></li>
+ <li><link anchor="done">Changes for &xslt4c; version 1.7</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 since &xslt4c; version 1.5">
- <p>Major updates since version 1.5 include:</p>
+ <anchor name="done"/>
+ <s3 title="Changes for &xslt4c; version 1.7">
+ <p>Major updates since version 1.6 include:</p>
<ul>
- <li><resource-ref idref="bugsfixedforthisrelease"/>.</li>
- <li>Directory "sane include" reorganization. A new
sub-directory called 'xalanc' has been added to the src directory
(for source distribution packages) and include directory (for binary
distribution packages). New source files which include Xalan headers will need
to be modified to include the 'xalanc' prefix in the header path.
-
-For example: <br/><br/>
-
-<code>#include <XPath/XObject.hpp></code><br/><br/>
-
-will need to be changed to <br/><br/>
-
-<code>#include <xalanc/XPath/XObject.hpp></code><br/><br/>
-
-For Windows users, all project files have been modified to reflect this
change. For UNIX users, please see <link anchor="unix">Steps for doing a UNIX
build</link> for migration considerations.</li>
+ <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>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>
- <anchor name="bugs"/>
+
+ <anchor name="bugs"/>
<s3 title="Bug reporting">
<p>All known &xslt4c; bugs are listed in <resource-ref
idref="bugzilla"/>. For a list of open bugs with links to each bug
report, see <resource-ref idref="buglist"/>. If you find a new bug,
please enter a XalanC bug report in this
@@ -118,6 +131,7 @@
<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="unix">Steps for doing a UNIX build</link></li>
+ <li><link anchor="locale">Steps for doing a Build with Message
Localization 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
@@ -137,11 +151,16 @@
<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>).<br/><br/></li>
- <li>Use Visual C++ to open the Xalan workspace from the
xml-xalan\c\Projects\Win32\VC6.
+ 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-dist;-src\Projects\Win32\VC6. If you are building with ICU, then use
XalanICU.dsw. Otherwise, open the Xalan.dsw workspace.
<br/><br/></li>
- <li>Use Visual C++ to build the Xalan library (the "AllInOne" project)
and executables of interest. If you want to enable ICU support for number
formatting and sorting, do a clean build of the Xalan library using the
AllInOneWithICU project before building any executables. ICU support for the
testXSLT application requires uncommenting of the #define XALAN_USE_ICU
statement in process.cpp. (See <link idref="commandline"
- anchor="icu">Enabling ICU support for the Xalan and/or TestXSLT
executable</link>).</li>
+ <li>From Visual C++, go to "Tools" and select "Options". 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>
@@ -151,36 +170,171 @@
<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/xalan", you would set the XALANCROOT to "/home/xalan/xml-xalan/c".
<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>)<br/><br/></li>
- <li>Change directory to xml-xalan/c/src/xalanc in the &xslt4c;
distribution. 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 with the platform, C compiler, and
C++ compiler flags as indicated below.<br/><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>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/>
- To see the other runConfigure flags you may include, use the help
flag:<br/><br/>
- <code>./runConfigure
-h</code><br/><br/></li>
+ distribution. For example, if the distribution is located in
"/home/xalan", you would set the XALANCROOT to "/home/xalan/&xslt4c-dist;-src".
<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-dist;-src in the &xslt4c;
distribution. 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
+ indicated below. The runConfigure utility is used to generate the
appropriate Makefile for
+ the desired build platform based on the options specified by the
user. Valid options for the
+ runConfigure utility are:<br/><br/>
+ <code>./runConfigure -p <value> -c <value> -x
<value> [-[flag] <value>]</code><br/><br/>
+ <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>
+ <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.
+ Default is icu.</td></tr>
+ <tr><td>M</td><td>Locale for Message Localization Support. Default
is "en_US'</td></tr>
+ <tr><td>r</td><td>Threads option. Valid values include: pthread or
dce. Default is <br/>dce</td></tr>
+ <tr><td>b</td><td>Specify whether it is a 32-bit or 64-bit build.
Valid values are 32 <br/>and 64.
+ Default is 32-bit</td></tr>
+ <tr><td>P</td><td>Install root directory. Used if invoking build
with gmake install or <br/>gmake
+ install-package. Default install root directory is
/usr/local</td></tr>
+ <tr><td>l</td><td>Extra link options other than the default.
Default is null</td></tr>
+ <tr><td>z</td><td>Extra compiler options other than the default.
Default is null</td></tr>
+ <tr><td>C</td><td>Extra configuration options.</td></tr>
+ <tr><td>h</td><td>To get help on the above commands. Default is no
help.</td></tr>
+ </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>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/>
+ 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/>
+ Following the build process, standard binary directories bin, lib,
and include would be created
+ under my_xalan.<br/><br/>
+ To see the other runConfigure flags you may include, use the help
flag:<br/><br/>
+ <code>./runConfigure
-h</code><br/><br/></li>
<li>Purge the previous build:<br/><br/>
- <code> make clean</code><br/><br/></li>
- <li>Build the Xalan library and command-line executables:<br/><br/>
- <code>make</code><br/>
- or<br/>
- <code>make
<ref>targ</ref></code><br/><br/>
- where <ref>targ</ref> is omitted or is <code>all</code> (rebuild all),
<code>lib</code> (the XSLT library), <code>Xalan</code> (the Xalan executable),
or
- <code>testXSLT</code> (the testXSLT executable). ICUBridge is included
in the build of Xalan and TestXSLT if XALAN_USE_ICU is
- defined. You can build the sample applications using the target
<code>samples</code>.<br/><br/></li>
+ <code> make
clean</code><br/><br/></li>
+ <li>Run the new build:<br/><br/>
+ <code>make</code><br/>
+ or<br/>
+ <code>make
<ref>targ</ref></code><br/><br/>
+ where <ref>targ</ref> can be one of:
+ <table>
+ <tr><th>targ</th><th>Description</th></tr>
+ <tr><td>all</td><td>Build the libraries and Xalan executable. This
is the default target <br/>if no targ
+ is specified.</td></tr>
+ <tr><td>clean</td><td>Deletes existing binaries, executables,
libraries, tests, and <br/>samples.</td></tr>
+ <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>
+ </table>
+ </li>
</ol>
- <note>To recompile existing applications without changing your source
code, be sure to modify the command line in your Makefile to pick up the Xalan
headers from it's new location. e.g: if your xalan source location is in
/home/xml-xalan,</note><p>
- <br/> <code>CC ...
-I/home/xml-xalan/c/src -I/home/xml-xalan/c/src/xalanc mysrc.cpp</code><anchor
name="64"/></p>
- </s3><anchor name="samples"/>
+ <note>To recompile existing applications without changing your source
code, be sure to modify the command line in your Makefile to pick up the Xalan
headers from it's new location. e.g: if your xalan source location is in
/home/&xslt4c-dist;-src,</note><p>
+ <br/> <code>CC ...
-I/home/&xslt4c-dist;-src/src -I/home/&xslt4c-dist;-src/src/xalanc
mysrc.cpp</code><anchor name="64"/></p>
+ </s3>
+ <anchor name="locale"/>
+ <s3 title="Steps for doing a Build with Message Localization Support">
+ <p>Message Localization Support is a new feature to allow users to build
XSLT4C such that
+ diagnostic messages are issued in the language of their choice. Message
localization support
+ comes in three flavours:</p>
+ <ul>
+ <li>Building static messages in the form of a library (DLL or shared
object) which can be bound
+ to the Xalan executable. This method is referred to as "in memory". </li>
+ <li>Building messages in the form of a library using localization support
provided by the
+ International Components for Unicode (ICU). By default, XSLT4C is built
using ICU localization
+ support. </li>
+ <li>Building messages in the form of a message catalog. This method
utilizes the localization
+ support provided by the Unix National Language Support (NLS) system. This
method is supported
+ for UNIX platforms only. </li>
+ </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 beta 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
+ information.) All message files must be written and conform with the
XLIFF 1.1 standard.</p>
+ <p>Once an XLIFF message file has been created, the XLIFF file should be
stored under
+ &xslt4c-dist;-src/c/src/xalanc/NLS directory (for example, the default
XLIFF message file
+ provided is xslt4cMessages_en_US.xlf). To build, you will need to follow
the same steps
+ 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>Open the Xalan workspace using Microsoft Visual C++. </li>
+ <li>Select the Localization project, and go to Settings and click on the
"General" tab. Modify
+ the build command line to use "nmake /f Localization.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>Open the Xalan workspace using Microsoft Visual C++. </li>
+ <li>Select the AllInOneWithICU project, and ensure that the project
depends on the Localization
+ project. </li>
+ <li>Select the Localization project, and go to Settings and click on the
"General" tab. Modify
+ the build command line to use "nmake /f Localization.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. </li>
+ <li>Run "Build all" with the configuration of your choice. </li>
+ </ol>
+ <p>For building on the Unix platform:</p>
+ <ol>
+ <li>Repeat steps 1 through 5 as outlined under "Steps for doing a UNIX
Build" </li>
+ <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/>
+ 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/>
+ </li>
+ <li>Perform steps 7 and 8 as outlined under "Steps for doing a UNIX
Build" </li>
+ </ol>
+ <p>After XSLT4C and associated libraries have been successfully built,
the message catalog
+ will be stored in the directory
&xslt4c-dist;-src/c/src/xalanc/NLS/<locale_name> (for example
+ &xslt4c-dist;-src/c/src/xalanc/NLS/en_US/) under the file name:<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>libxslt4cMessages_1_7.so (for UNIX)<br/>
+ xslt4cMessages_1_7.dll and xslt4cMessages_1_7.lib (for Windows)
+ </td></tr>
+ <tr><td><ref>NLS method:</ref></td><td>xslt4cMessages_1_7.cat</td></tr>
+ </table>
+ </p>
+ <p>The location of the message library, &xslt4c; and &xml4c; binaries
need to be added to the PATH and
+ library path variables. Depending on the Message Localization Support
method you've chosen, the
+ following steps will need to be performed such that XSLT4C will be able
to utilize the message
+ library. </p>
+ <ul>
+ <li>For an "in memory" or "icu" build, the location of the XSLT4C and
XML4C executables need to
+ be added to the PATH variable. The location of the message library will
need to be added to:
+ <ul>
+ <li>the LIBPATH variable for AIX users </li>
+ <li>the LD_LIBRARY_PATH variable for RedHat, SuSE, and Solaris users </li>
+ <li>the SHLIB_PATH variable for HP-UX users. </li>
+ </ul></li>
+ <li>For an NLS build, the message catalog will need to be added to the
NLSPATH. </li>
+ </ul>
+ </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. If you modify a sample and want
to recompile it, you can recompile the .cpp file(s) and rebuild the
executable.</p>
-<p>The Makefile that come with the UNIX distributions include targets for
rebuilding one or all of the sample applications (with the exception of the
ThreadSafe sample, which in its current form only runs under Windows). To
rebuild one or more sample applications, go to the xml-xalan/c/src/xalanc
directory and run<br/><br/>
+<p>The Makefile that come with the UNIX 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 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>
<note>For information on building Apache Module, see <link idref="samples"
anchor="apachemodulexslt">ApacheModuleXSLT</link></note>
1.27 +1 -1 xml-xalan/c/xdocs/sources/xalan/resources.xml
Index: resources.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/resources.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- resources.xml 6 Jan 2004 02:41:48 -0000 1.26
+++ resources.xml 7 Jan 2004 05:28:38 -0000 1.27
@@ -115,6 +115,6 @@
<resource id="bugsfixedforthisrelease"
title="XalanC bugs fixed for this release"
-
location="http://nagoya.apache.org/bugzilla/buglist.cgi?resolution=FIXED&bugidtype=include&bug_id=&changedin=&chfield=resolution&chfieldfrom=04%2F15%2F2003&chfieldto=07%2F20%2F2003&chfieldvalue=FIXED&product=XalanC&short_desc=&short_desc_type=allwordssubstr"/>
+
location="http://nagoya.apache.org/bugzilla/buglist.cgi?resolution=FIXED&bugidtype=include&bug_id=&changedin=&chfield=resolution&chfieldfrom=07%2F20%2F2003&chfieldto=12%2F31%2F2003&chfieldvalue=FIXED&product=XalanC&short_desc=&short_desc_type=allwordssubstr"/>
</resources>
1.40 +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.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- samples.xml 6 Jan 2004 02:41:48 -0000 1.39
+++ samples.xml 7 Jan 2004 05:28:38 -0000 1.40
@@ -96,7 +96,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
(xml-xalan\c\Build\Win32\VC6\ Debug and Release). To run a sample, be sure 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
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">
@@ -318,7 +318,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
xml-xalan\c\Build\Win32\VC6\Release\ApacheModuleXSLT.dll</code><br/><br/>
+ Windows: <code>LoadModule xslt_module
&xslt4c-dist;-<my_Windows_distribution>\Build\Win32\VC6\Release\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/>
@@ -336,7 +336,7 @@
Note: It is up to the stylesheet to apply the appropriate xsl:output
method to the output. Whether the user specifies html or txt is, of
itself, immaterial.<br/><br/></li>
<li>Put xml/xsl file pairs in the <Location> subdirectory (xslt in
the example)) under the document root directory specified in httpd.conf by the
- DocumentRoot and <Directory> settings. Alternatively, you can
modify these settings to point to xml-xalan/c/samples/ApacheModuleXSLT,
+ DocumentRoot and <Directory> settings. Alternatively, you can
modify these settings to point to
&xslt4c-dist;-<my_UNIX_distribution>/samples/ApacheModuleXSLT,
which includes an xslt subdirectory with xml/xsl file pairs
(foo.xml/xsl, apachemod.xml/xsl).<br/><br/></li>
<li>Start the Apache server.<br/><br/></li>
<li>From a Web browser, call the module with a URL as follows:<br/>
1.42 +3 -2 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.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- usagepatterns.xml 6 Jan 2004 02:41:48 -0000 1.41
+++ usagepatterns.xml 7 Jan 2004 05:28:38 -0000 1.42
@@ -4,7 +4,7 @@
* The Apache Software License, Version 1.1
*
*
- * Copyright (c) 1999-2004 The Apache Software Foundation. All rights
+ * Copyright (c) 1999-2003 The Apache Software Foundation. All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or without
@@ -160,7 +160,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_5</em>. The macros will automatically take care
+ <em>xalanc_1_7</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.
@@ -587,6 +587,7 @@
<br/>If you install ICU support for xml:sort, &xslt4c;
implements Unicode-style collation.</li>
</ul>
+ <p>If you choose to build Xalan with ICU, you will need to rebuild
Xerces with ICU as well.</p>
<p>To get the ICU:</p>
<ol>
<li>Download and unzip the <resource-ref idref="icu-download"/> from
the IBM
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
