dleslie 00/12/12 14:47:38
Modified: c/xdocs/sources entities.ent
c/xdocs/sources/xalan STATUS commandline.xml getstarted.xml
index.xml overview.xml readme.xml resources.xml
samples.xml usagepatterns.xml xalan-cdist.gif
Log:
Updates in progress for Xalan-C 1.1
Revision Changes Path
1.9 +6 -4 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.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- entities.ent 2000/09/29 15:44:27 1.8
+++ entities.ent 2000/12/12 22:47:31 1.9
@@ -1,17 +1,19 @@
<?xml encoding="US-ASCII"?>
<!ENTITY xslt4c "Xalan-C++">
-<!ENTITY xslt4c-dist "Xalan-C_1_0">
-<!ENTITY xslt4c-current "Xalan-C++ version 1.0">
+<!ENTITY xslt4c-dist "Xalan-C_1_1">
+<!ENTITY xslt4c-current "Xalan-C++ version 1.1">
<!ENTITY xslt4c-windlls "DOMSupport.dll, PlatformSupport.dll, XalanDOM.dll,
XercesParserLiaison.dll, XMLSupport.dll, XPath.dll, XSLT.dll">
-<!ENTITY xslt4c-linuxlib "libxalan-c1_0.so">
-<!ENTITY xslt4c-aixlib "libxalan-c1_0.a">
+<!ENTITY xslt4c-linuxlib "libxalan-c1_1.so">
+<!ENTITY xslt4c-aixlib "libxalan-c1_1.a">
+<!ENTITY xslt4c-hplib "libxalan-c1_1.sl">
<!ENTITY xml4c "Xerces-C++">
<!ENTITY xml4c-used "Xerces-C++ version 1.3.0">
<!ENTITY xml4c-windll "xerces-c_1_3.dll">
<!ENTITY xml4c-winlib "xerces-c_1.lib">
<!ENTITY xml4c-linuxlib "libxerces-c1_3.so">
<!ENTITY xml4c-aixlib "libxerces-c1_3.a">
+<!ENTITY xml4c-hplib "libxerces-c1_3.sl">
<!ENTITY xslt4j "Xalan-Java">
<!ENTITY icu-used "International Components for Unicode(ICU) 1.6 source
files">
<!ENTITY icu-windlls "icui18n.dll, icuuc.dll">
1.11 +1 -3 xml-xalan/c/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/STATUS,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- STATUS 2000/10/10 15:46:28 1.10
+++ STATUS 2000/12/12 22:47:31 1.11
@@ -1,7 +1,5 @@
<s3 title="Version of &xml4c; to use">
-<p>&xslt4c-current; has been tested with &xml4c-used;. The &xslt4c-current;
Windows32 download includes &xml4c-windll;.
-The &xslt4c-current; Linux download includes &xml4c-linuxlib;. The
&xslt4c-current; AIX download includes &xml4c-aixlib;
-For information about including The Xerces-C++ dynamic link or shared object
library on the path, see <link idref="getstarted" anchor="path">Setting up the
system path</link>.</p>
+<p>&xslt4c-current; has been tested with &xml4c-used;. Each &xslt4c-current;
download includes the entire Xerces-C++ source tree and the required binaries
for the specified platform. 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"/>
<s3 title="To-do tasks for future &xslt4c; releases">
1.12 +6 -6 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.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- commandline.xml 2000/10/03 20:30:21 1.11
+++ commandline.xml 2000/12/12 22:47:32 1.12
@@ -135,17 +135,17 @@
<li>Build TestXSLT.exe.</li>
</ol>
</s3>
- <s3 title="Rebuilding TestXSLT in Linux or AIX">
- <p>In Linux and AIX, the ICUBridge is in the core Xalan library
(&xml4c-linuxlib; in Linux; &xml4c-aixlib; in
- AIX), so you must rebuild this library along with TestXSLT.</p>
+ <s3 title="Rebuilding TestXSLT in UNIX">
+ <p>In Linux, AIX, and HP-UX 11, the ICUBridge is in the core Xalan
library (&xml4c-linuxlib; in Linux; &xml4c-aixlib; in
+ AIX; &xml4c-hplib; in HP-UX 11), so you must rebuild this library along
with 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 Linux or AIX build, see <link
idref="readme" anchor="unix">Steps for doing a
- Linux or AIX build</link>.</p>
+ 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_USER{ICU' has already been defined") and a warning in
Linux about duplicate settings when you
- run the make, and TextXSLT will not link with ICUBridge.</note>
+ run the make, and TextXSLT will not link with ICUBridge. WHAT HAPPENS
IN HP??</note>
</s3>
</s2>
</s1>
1.15 +29 -14 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.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- getstarted.xml 2000/10/03 20:30:22 1.14
+++ getstarted.xml 2000/12/12 22:47:32 1.15
@@ -11,14 +11,21 @@
</ul>
<anchor name="download"/>
<s2 title="Downloading what you need">
-<p>For &xslt4c-current;, we are distributing a Windows32 Visual C++ build, a
Red Hat Linux GNU build, and an AIX xlC_r build. Please contact us at
<human-resource-ref idref="xalandev"/> if you would like to help provide builds
for other platforms.</p>
-<s3 title="&xslt4c; Distributions">
-<p><img src="xalan-cdist.gif" alt="xalan-cdist.gif"/></p>
+<p>For &xslt4c-current;, we are distributing a Windows32 Visual C++ build
and three UNIX builds with a makefile: a Red Hat Linux GNU build, an AIX xlC_r
build, and an HP-UX 11 aCC build.
+Please contact us at <human-resource-ref idref="xalandev"/> if you would
like to help provide builds for other platforms.</p>
+<anchor name="xalandists"/>
+<s3 title="&xslt4c; Windows Distribution">
+<p><img src="xalan-c-windist.gif" alt="xalan-cdist.gif"/></p>
</s3>
<p>For the Windows32 build, download <resource-ref
idref="xslt4c-win32-download"/>.</p>
+<s3 title="&xslt4c; UNIX Distributions">
+<p><img src="xalan-c-unixdist.gif" alt="xalan-cdist.gif"/></p>
+</s3>
<p>For the Linux build, download <resource-ref
idref="xslt4c-linux-download"/></p>
<p>For the AIX build, download <resource-ref
idref="xslt4c-aix-download"/></p>
-<p>Each distribution contains all you need to run the Xalan command-line
utility for performing transformations. To build your own applications, you
also need a compatible &xml4c; binary distribution. If you want to take
advantage of the support for number formatting, sorting, and encoding the ICU
provides, you should also download and install the <resource-ref idref="icu"/>;
see <link idref="usagepatterns" anchor="icu">Using the ICU</link>,</p>
+<p>For the HP-UX 11 build, download <resource-ref
idref="xslt4c-hp-download"/></p>
+<p>Each distribution contains all you need to run the Xalan command-line
transformations utility and to build your own applications.
+If you want to take advantage of the support for number formatting, sorting,
and encoding the ICU provides, you should also download and install the
<resource-ref idref="icu"/>; see <link idref="usagepatterns" anchor="icu">Using
the ICU</link>,</p>
<s3 title="What you need to run the Xalan command-line utility">
<p>To run the Xalan executable for performing transformations, you need the
following:</p>
<p><em>Windows32</em></p>
@@ -39,20 +46,27 @@
<li>The executable: TestXSLT</li>
<li>The Xalan-C++ load library: &xslt4c-aixlib;</li>
<li>The Xerces-C++ load library: &xml4c-aixlib;</li>
+</ul>
+<p><em>HP-UX 11</em></p>
+<ul>
+ <li>The executable: TestXSLT</li>
+ <li>The Xalan-C++ shared library: &xslt4c-hplib;</li>
+ <li>The Xerces-C++ shared library: &xml4c-hplib;</li>
</ul>
-<p>If you want to enable ICU support for the command-line utility, you must
build the ICU and rebuild the Xalan-C++ shared/load library (Linux/AIX) and
TestXSLT (all platforms) with the ICUBridge. See <link idref="usagepatterns"
anchor="icu">Using the ICU</link> and <link idref="commandline"
anchor="icu">Enabling ICU support for TestXSLT</link>.</p>
+<p>If you want to enable ICU support for the command-line utility, you must
build the ICU and rebuild the Xalan-C++ shared/load library (Linux/AIX/HP-UX
11) and TestXSLT (all platforms) with the ICUBridge. See <link
idref="usagepatterns" anchor="icu">Using the ICU</link> and <link
idref="commandline" anchor="icu">Enabling ICU support for TestXSLT</link>.</p>
<p>For information about using the command-line utility, see <link
idref="commandline">Command-Line Utility</link>.</p>
<note>If you want to do your own AIX build, you must download <resource-ref
idref="stlport"/> and set the STLPORTROOT
environment variable to the complete path to the STLPort distribution (see
the <link idref="readme" anchor="build">Build notes</link>)</note>
</s3>
-<s3 title="What you need to build applications">
+<s3 title="What you need to build and run applications">
<p>To build your own applications with Xalan and Xerces, you also need need
the
-Xalan-C++ and Xerces-C++ header (.hpp) files and (for Windows) the &xslt4c;
and &xml4c; libraries (.lib files).</p>
-<p>The Xalan-C++ header files are in the src directory tree in both
distributions.</p>
-<p>In the Windows32 distribution (built with Microsoft® Visual C++®
6.0), the dlls and libraries are in the Build - Win32 -V6 - Release
subdirectory.</p>
-<p>In the Linux distribution (built with a make file and the GNU C++
compiler on Red Hat Linux 6.1), the shared object library is in the lib
subdirectory.</p>
-<p>In the AIX distribution (built with the make file and xlC_r), the load
library is in the lib subdirectory.</p>
-<p>To get the Xerces-C++ header and (for Windows) .lib files, download and
expand the &xml4c; binary distribution for your platform from the <resource-ref
idref="xml4c-distdir"/>. For information about which &xml4c; distribution has
been tested with this &xslt4c; release, see <link idref="readme"
anchor="status">Version of &xml4c; to use</link>.</p>
+Xalan-C++ and Xerces-C++ header (.hpp) files and (for Windows) the &xslt4c;
and &xml4c; libraries (.lib files). To run your applications, you need the
&xslt4c; and &xml4c; library files (.dll files for Windows, shared or load
libraries for the UNIX platforms).</p>
+<p>The Xalan-C++ and Xerces-C++ header files are in the src directory trees
in both distributions.</p>
+<p>In the Windows32 distribution (built with Microsoft® Visual C++®
6.0), the .dlls and libraries are in the Build\Win32\V6 Debug and Release
subdirectories.</p>
+<p>In the Linux distribution (built with a make file and the GNU C++
compiler on Red Hat Linux 6.1), the shared object libraries are in the lib
subdirectories.</p>
+<p>In the AIX distribution (built with the make file and xlC_r), the load
libraries are in the lib subdirectories.</p>
+<p>In the HP-UX 11 distribution (built with the make file and aCC), the
shared libraries are in the lib subdirectories.</p>
+<note>For your convenience, both the Xalan and Xerces libraries are placed
together in the pertinent xml-xalan directory, whereas the corresponding
xml-xerces directory only contains Xerces libraries.</note>
<p>If you want to enable ICU support in your applications, you must rebuild
the Xalan-C++ shared/load library (Linux/AIX) and include the ICUBridge headers
(all platforms).</p>
<p>For the requirements for rebuilding &xslt4c;, see the <link
idref="readme" anchor="build">Build notes</link>.</p>
</s3>
@@ -60,7 +74,8 @@
<s2 title="Setting up the path">
<p>For the Xalan-C++ Windows32 distribution, place
xml-xalan\c\Build\Win32\VC6\Release on the path.</p>
<p>For the Xalan-C++ Linux distribution, place xml-xalan/c/bin and
xml-xalan/c/lib on the shared library path (LD_LIBRARY_PATH for Red Hat Linux
6.1), or copy &xslt4c-linuxlib; to /usr/lib.</p>
-<p>For the Xalan-C++ AIX distribution, place xml-xalan/c/bin and
xml-xalan/c/lib on the load library path (LIB_PATH for AIX), or copy
&xslt4c-aixlib; to /usr/lib.</p>
+<p>For the Xalan-C++ AIX distribution, place xml-xalan/c/bin and
xml-xalan/c/lib on the load library path (LIB_PATH), or copy &xslt4c-aixlib; to
/usr/lib.</p>
+<p>For the Xalan-C++ HP-UX 11 distribution, place xml-xalan/c/bin and
xml-xalan/c/lib on the shared library path (SHLIB_PATH), or copy
&xslt4c-aixlib; to /usr/lib.</p>
<p>If you do your own Xalan, ICU, and Xerces builds, be sure to include the
directories that contain the libraries and the TextXSLT executable on your
path.</p>
</s2><anchor name="samples"/>
@@ -69,7 +84,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 Linux and AIX distributions, the
executables are in xml-xalan/c/bin.</li>
+xml-xalan\c\Build\Win32\VC6\Release. In the UNIX distributions, the
executables are in xml-xalan/c/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 +6 -4 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.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- index.xml 2000/10/02 12:17:04 1.11
+++ index.xml 2000/12/12 22:47:32 1.12
@@ -89,15 +89,17 @@
<td>AIX</td>
<td><resource-ref idref="xslt4c-aix-download"/></td>
</tr>
+ <tr>
+ <td>HP-UX 11</td>
+ <td><resource-ref idref="xslt4c-hp-download"/></td>
+ </tr>
</table>
<p>Volunteers are more than welcome to help develop builds for other
platforms!</p>
</s2>
<s2 title="Where do I get Xerces?">
- <p>The distributions include the Xerces runtime environment for Xalan:
&xml4c-windll; for
- Windows, &xml4c-linuxlib; for Linux, and &xml4c-aixlib; for AIX.</p>
- <p>To build applications with Xalan and Xerces, you also need the
&xml4c; binary distribution
- for your platform, which you can download from the <resource-ref
idref="xml4c-distdir"/>.</p>
+ <p>Right here! The distributions include everything you need to build
and run applications that use Xalan and Xerces. Each distribution file includes
the Xerces source tree along with the appropriate Xerces runtime environment
for Xalan: &xml4c-windll; for
+ Windows, &xml4c-linuxlib; for Linux, &xml4c-aixlib; for AIX, and
&xml4c-hplib; for HP-UX 11.</p>
</s2>
<s2 title="How about support for internationalization?">
<p>To extend Unicode support for encoding, number formatting, and
sorting, you can download,
1.9 +29 -28 xml-xalan/c/xdocs/sources/xalan/overview.xml
Index: overview.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/overview.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- overview.xml 2000/10/10 15:46:26 1.8
+++ overview.xml 2000/12/12 22:47:32 1.9
@@ -119,35 +119,39 @@
<p>If you are still working through the details of the XSLT spec (the
W3C 1.0 Recommendation), you may want
to consult one or more of the following:</p>
<ul>
- <li>Michael Kay's <jump
href="http://www.wrox.com/Consumer/Store/Details.asp?ISBN=1861003129";>XSLT
Programmer's
- Reference</jump>, Wrox Press, 2000<br/><br/></li>
- <li>Neil Bradley's <jump
href="http://cseng.aw.com/bookpage.taf?ISBN=0-201-67487-4";>XSL Companion</jump>,
- Addison-Wesley, 2000<br/><br/></li>
- <li>Elliotte Rusty Harold's <jump
href="http://metalab.unc.edu/xml/books/bible/updates/14.html";>Chapter 14 of
- the XML Bible: XSL Transformations</jump> (the online version is more
current than the version in the printed
- book)<br/><br/></li>
- <li>Crane Softwright's <jump
href="http://www.CraneSoftwrights.com/training/";>Free preview of Practical
- Transformation Using XSLT and XPath</jump><br/><br/></li>
- <li>The Mulberry <jump
href="http://www.mulberrytech.com/xsl/xsl-list/";>XSL-List -- Open Forum on
XSL</jump>
- (of interest to XSL users at all levels)<br/><br/></li>
- <li>Dave Pawson's <jump
href="http://freespace.virgin.net/b.pawson/xsl/xslfaq.html";>XSL Frequently Asked
- Questions</jump><br/><br/></li>
- <li>Objects by Design's <jump
href="http://www.objectsbydesign.com/projects/xmi_to_html.html";>Transforming
XMI to
- HTML</jump> (oriented towards XMI, "an XML-based, stream representation
of a UML model," but also covers "generic"
- XML transformations)<br/><br/></li>
- <li>Nic Miloslav's <jump
href="http://zvon.vscht.cz/HTMLonly/XSLTutorial/Books/Book1/index.html";>XSL
Tutorial</jump>
- <br/><br/></li>
- <li>OASIS (the Organization for the Advancement of Structured
Information Standards):
- <jump href="http://www.oasis-open.org/cover/xsl.html";>Extensible
Stylesheet Language (XSL)</jump> by Robin
- Cover<br/><br/></li>
- <li>Donald Ball's <jump
href="http://www.webslingerZ.com/balld/xsl/designer_manual.xml";>A Guide to XML
and XSL for
- Designers</jump></li>
+ <li>Michael Kay's <jump
href="http://www.wrox.com/Consumer/Store/Details.asp?ISBN=1861003129";>XSLT
Programmer's
+ Reference</jump>, Wrox Press, 2000<br/><br/></li>
+ <li>Neil Bradley's <jump
href="http://cseng.aw.com/bookpage.taf?ISBN=0-201-67487-4";>XSL Companion</jump>,
+ Addison-Wesley, 2000<br/><br/></li>
+ <li>Elliotte Rusty Harold's <jump
href="http://metalab.unc.edu/xml/books/bible/updates/14.html";>Chapter 14 of
+ the XML Bible: XSL Transformations</jump><br/><br/></li>
+ <li>Crane Softwright's <jump
href="http://www.CraneSoftwrights.com/training/";>Free preview of Practical
+ Transformation Using XSLT and XPath</jump><br/><br/></li>
+ <li>The Mulberry <jump
href="http://www.mulberrytech.com/xsl/xsl-list/";>XSL-List -- Open Forum on
XSL</jump>
+ (of interest to XSL users at all levels)<br/><br/></li>
+ <li>Dave Pawson's <jump
href="http://www.dpawson.freeserve.co.uk/";>XSL Frequently Asked
+ Questions</jump><br/><br/></li>
+ <li>Objects by Design's <jump
href="http://www.objectsbydesign.com/projects/xmi_to_html.html";>Transforming
XMI to
+ HTML</jump> (oriented towards XMI, "an XML-based, stream
representation of a UML model," but also covers "generic"
+ XML transformations)<br/><br/></li>
+ <li>Miloslav Nic's <jump
href="http://zvon.vscht.cz/HTMLonly/XSLTutorial/Books/Book1/index.html";>XSL
Tutorial</jump>
+ <br/><br/></li>
+ <li>OASIS (the Organization for the Advancement of Structured
Information Standards):
+ <jump href="http://www.oasis-open.org/cover/xsl.html";>Extensible
Stylesheet Language (XSL)</jump> by Robin
+ Cover<br/><br/></li>
+ <li>Donald Ball's <jump
href="http://www.webslingerZ.com/balld/xsl/designer_manual.xml";>A Guide to XML
and XSL for
+ Designers</jump><br/><br/></li>
+ <li>XSLT - XSL Transformations in
+ <jump href="http://www.brics.dk/~amoeller/XML/";>The XML Revolution:
Technologies for the future Web</jump> by
+ Anders Møller and Michael I. Schwartzbach<br/><br/></li>
+ <li>Elizabeth Castro's <jump
href="http://www.peachpit.com/books/catalog/71098.html";>XML for the World Wide
Web:
+ Visual Quickstart Guide</jump></li>
</ul>
<p>When you come across other useful introductory or background
materials, please email <human-resource-ref
idref="xalandev"/>, so we can add them to this list.</p>
</s2><anchor name="glossary"/>
- <s2 title="Glossary">
+ <s2 title="Glossary">
<gloss>
<label>XSLT Namespace</label>
<item>The <jump href="http://www.w3.org/TR/REC-xml-names/";>XML
namespace</jump> for XSLT. An XML namespace is a
@@ -172,10 +176,7 @@
<label>Result Tree</label>
<item>The tree that is output by the XSL process.<br/><br/></item>
-
- <label>Stylesheet Tree</label>
- <item>The stylesheet tree produced from the XSL
file.<br/><br/></item>
-
+
<label>Match Pattern</label>
<item>The part of a template that defines the kind(s) of nodes to
which the template applies.<br/><br/></item>
1.16 +15 -21 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.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- readme.xml 2000/10/10 15:46:27 1.15
+++ readme.xml 2000/12/12 22:47:33 1.16
@@ -70,7 +70,7 @@
<anchor name="status"/>
<s2 title="Status">
<ul>
- <li><link anchor="done">Changes since &xslt4c; version
0.40.0</link></li>
+ <li><link anchor="done">Changes since &xslt4c; version 1.0</link></li>
<li><link anchor="bugs">Bug reporting</link></li>
<li><link anchor="xml4j">Version of &xml4c; to use</link></li>
<li><link anchor="to-do">To-do tasks for future &xslt4c;
releases</link></li>
@@ -93,16 +93,15 @@
<ul>
<li><link anchor="layout">Layout of Xerces-C and ICU</link></li>
<li><link anchor="win32">Steps for doing a Windows build</link></li>
- <li><link anchor="unix">Steps for doing a Linux or AIX build</link></li>
+ <li><link anchor="unix">Steps for doing a UNIX build</link></li>
</ul>
- <p>If you want to rebuild &xslt4c; (to produce a debug build, for
example), you need the following:</p>
+ <p>If you want to rebuild &xslt4c;, you need the following:</p>
<ul>
<li>The &xslt4c; source files</li>
<li>The &xml4c; header and (for Windows) .lib files</li>
<li>(Optional) The ICU header and (for Windows) .lib files</li>
</ul>
- <p>The &xslt4c; source files are in the distribution.</p>
- <p>The required &xml4c; files are in the &xml4c; binary distributions.</p>
+ <p>The &xslt4c; source files and The required &xml4c; files are in the
distribution.</p>
<p>For information on using the <resource-ref idref="icu"/>, see
<link idref="usagepatterns" anchor="icu">Using the ICU</link>.</p>
<note>If you are not rebuilding with the ICU, you do not need the ICU
header or .lib files.</note>
@@ -112,20 +111,17 @@
xml-xalan directory.</p>
</s3><anchor name="layout"/>
<s3 title="Layout">
- <p><em>Important</em> We have set up the Visual C++ projects and the
Linux and AIX make files to look for Xerces in a directory structure that
results from downloading xml-xerces/c from the <jump
href="http://xml.apache.org/websrc/cvsweb.cgi/";>Apache XML CVS
repository</jump> and building with the Visual C++ project files or the Linux
make file. This structure parallels the &xslt4c; source tree and build
structure.</p>
-<p>If you are using a &xml4c; binary distribution, you must either modify
the &xslt4c; project files or makefile, or rearrange the build directory
structure as indicated in the following illustration.</p>
-<p>For Linux and AIX, the XERCESROOT environment variable points to the
Xerces-C root directory. For Windows, the Xerces-C root directory must be named
xml-xerces, and it must be at the same level as the &xslt4c; root directory.
For all environments, the ICU root directory must be named icu, and it must be
at the same level as the &xslt4c; root directory.</p>
-<s4 title="&xml4c; and ICU layout for &xslt4c; build">
-<p><img src="xerces-icu.gif" alt="xerces-icu.gif"/></p>
+ <p><em>Important</em> We have set up the Visual C++ projects and the UNIX
make files to look for Xerces in the directory structure replicated in our
distribution files (see <link idref="getstarted" anchor="xalandists">&xslt4c;
Distributions</link>). This matches the structure that results from downloading
xml-xerces/c from the <jump
href="http://xml.apache.org/websrc/cvsweb.cgi/";>Apache XML CVS
repository</jump> and building with the Visual C++ project files or the UNIX
make file.</p>
+<p>If you are using a &xml4c; binary distribution that you have obtained
independently from this &xslt4c; distribution, you must either modify the
&xslt4c; project files or makefile, or rearrange the build directory structure
as indicated in the following illustration.</p>
+<p>For UNIX, the XERCESROOT environment variable points to the Xerces-C root
directory. For Windows, the Xerces-C root directory must be named xml-xerces,
and it must be at the same level as the &xslt4c; root directory. For all
environments, the ICU root directory must be named icu, and it must be at the
same level as the &xslt4c; root directory.</p>
+<s4 title="ICU layout for &xslt4c; build">
+<p><img src="icu.gif" alt="icu.gif"/></p>
</s4>
-<note>Keep in mind that at any given point in time the &xslt4c; and &xml4c;
source trees in the Apache XML repository may not be consistent. When we
release a version of &xslt4c; we certify that it is compatible with a given
release of &xml4c;. To be safe, stick with distributions that we certify to be
compatible. Reminder: &xslt4c-current; is compatible with
&xml4c-used;.<br/><br/>
+<note>Keep in mind that at any given point in time the &xslt4c; and &xml4c;
source trees in the Apache XML repository may not be consistent. When we
release a version of &xslt4c; we certify that it is compatible with a given
version of &xml4c;. To be safe, stick with distributions that we certify to be
compatible. Reminder: &xslt4c-current; is compatible with the &xml4c; that is
included with the distribution..<br/><br/>
&xslt4c-current; has been tested with &icu-used;. You may be able to use
newer ICU releases as they appear.</note>
</s3><anchor name="win32"/>
<s3 title="Steps for doing a Windows build">
<ol>
- <li>Rearrange the &xml4c; binary distribution as indicated above so the
headers are in
- the xml-xerces/c/src tree and xml-xerces is at the same level as the
xml-xerces root
- directory.<br/><br/></li>
<li>(Optional) If you are rebuilding the ICUBridge, install the ICU so
the icu root directory
is at the same level as the xml-xerces root directory (see <link
idref="usagepatterns" anchor="icu">Using the ICU</link>.<br/><br/>
@@ -140,16 +136,14 @@
interest.<br/><br/></li>
</ol>
</s3><anchor name="unix"/>
-<s3 title="Steps for doing a Linux or AIX build">
+<s3 title="Steps for doing a UNIX build">
<ol>
- <li>Rearrange the &xml4c; binary distribution as indicated above so
the headers are in the
- <ref>xerces-c_x_y_z-platform</ref>/c/src tree, and set the
XERCESCROOT environment variable
- to the complete path to
<ref>xerces-c_x_y_z-platform</ref>.<br/><br/></li>
+ <li>Set the XERCESCROOT environment variable to the root of
xml-xerces.<br/><br/></li>
<li>Set the XALANCROOT environment variable to the complete path to
the root of the &xslt4c;
distribution.<br/><br/></li>
<li>AIX only: Download <resource-ref idref="stlport"/> and set the
STLPORTROOT environment
variable to the complete path to the STLPort distribution. <br/>
- (This step is not required for Linux because The Linux GNU compiler
includes the STL (Standard Template
+ (This step is not required for Linux or HP-UX 11 because The Linux
GNU compiler and HP aCC compiler include the STL (Standard Template
Library.)<br/><br/></li>
<li>(Optional) If you are including the ICUBridge, install the ICU
(see <link idref="usagepatterns"
anchor="icu">Using the ICU</link>) and use the shell to define
XALAN_USE_ICU.<br/><br/>
@@ -158,13 +152,13 @@
If you are using C Shell:
<br/> <code>setenv
XALAN_USE_ICU="1"</code><br/><br/></li>
<li>Change directory to xml-xalan/c/src in the &xslt4c;
distribution.<br/><br/></li>
- <li>Use the chmod +x command to set the executable flags for conf* and
- runConfigure.<br/><br/>
+ <li>Use the chmod +x command to set the executable flags for conf* and
runConfigure.<br/><br/>
<code>chmod +x runConfigure</code><br/>
<code>chmod +x
conf*</code><br/><br/></li>
<li>Run the runConfigure utility with at least the platform flag
(Linux) or the platform, C compilier, and C++ compiler flags (AIX) as indicated
below.<br/><br/>
<ref>Linux:</ref> <code>runConfigure -p linux</code><br/>
<ref>AIX:</ref> <code>runConfigure -p aix -c
xlc_r -x xlC_r</code><br/><br/>
+ <ref>HP-UX 11:</ref> <code>runConfigure -p hp-11 -c cc -x
aCC</code><br/><br/>
To see the other runConfigure flags you may include, use the help
flag:<br/><br/>
<code>runConfigure
-h</code><br/><br/></li>
<li>Purge the previous build:<br/><br/>
1.8 +1 -0 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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- resources.xml 2000/10/10 15:46:27 1.7
+++ resources.xml 2000/12/12 22:47:33 1.8
@@ -23,6 +23,7 @@
<resource id="xslt4c-win32-download" title="&xslt4c-dist;-win32.zip"
location="http://xml.apache.org/dist/xalan-c/&xslt4c-dist;-win32.zip"/>
<resource id="xslt4c-linux-download" title="&xslt4c-dist;-linux.tar.gz"
location="http://xml.apache.org/dist/xalan-c/&xslt4c-dist;-linux.tar.gz"/>
<resource id="xslt4c-aix-download" title="&xslt4c-dist;-aix.tar.gz"
location="http://xml.apache.org/dist/xalan-c/&xslt4c-dist;-aix.tar.gz"/>
+<resource id="xslt4c-hp-download" title="&xslt4c-dist;-hp.tar.gz"
location="http://xml.apache.org/dist/xalan-c/&xslt4c-dist;-hp.tar.gz"/>
<resource id="icu" title="International Components for Unicode (ICU)"
location="http://oss.software.ibm.com/developerworks/opensource/icu/project/index.html"/>
<resource id="icu-download" title="International Components for Unicode
(ICU) 1.6 source files"
location="http://oss.software.ibm.com/developerworks/opensource/icu/project/download/index.html"/>
1.13 +12 -4 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.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- samples.xml 2000/10/10 15:46:28 1.12
+++ samples.xml 2000/12/12 22:47:33 1.13
@@ -61,6 +61,7 @@
<ul>
<li><link anchor="getstarted">Samples to help you get started</link></li>
<li><link anchor="simpletransform">SimpleTransform</link></li>
+ <li><link anchor="streamtransform">StreamTransform</link></li>
<li><link anchor="usestylesheetparam">UseStylesheetParam</link></li>
<li><link anchor="tracelisten">TraceListen</link></li>
<li><link anchor="compilestylesheet">CompileStylesheet</link></li>
@@ -85,7 +86,8 @@
</ol>
<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. The application executable, on the other hand, is in the build
subdirectory. To run a sample, be sure the
+ files. For the UNIX builds, the application executable is also in the
samples subdirectory. For the Windows32 build, however, the
+ application executable is in the build subdirectory
(xml-xalan\c\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="simpletransform"/>
<s2 title="SimpleTransform">
@@ -95,6 +97,12 @@
<p><code>SimpleTransform</code></p>
<p>See also: <link idref="usagepatterns" anchor="basic">Basic procedures
for performing XSL
transformations</link>.</p>
+ </s2><anchor name="streamtransform"/>
+ <s2 title="StreamTransform">
+ <p>What it does: The StreamTransform class processes input streams
containing a stylesheet and an XML document, and
+ writes the transformation output to an output stream.</p>
+ <p>You can run it from the SimpleTransform subdirectory with</p>
+ <p><code>StreamTransform</code></p>
</s2><anchor name="usestylesheetparam"/>
<s2 title="UseStylesheetParam">
<p>What it does: Set a stylesheet parameter that the stylesheet uses
during the transformation.</p>
@@ -171,7 +179,7 @@
<p>Run this sample from the XPathWrapper subdirectory with</p>
<p>Windows:<br/>
<code>TestDriver <ref>XMLFile ContextNode
XPathExpression</ref></code></p>
- <p>Linux or AIX:<br/>
+ <p>UNIX:<br/>
<code>XPathWrapper <ref>XMLFile ContextNode
XPathExpression</ref></code></p>
<p>where <ref>XMLFile</ref> is an XML source file,
<ref>ContextNode</ref> is the location path to the context
node, and <ref>XPathExpression</ref> is an XPath expression to apply to
that context node. The XPathWrapper
@@ -186,12 +194,12 @@
<p>You can try command lines like</p>
<p>Windows:<br/>
<code>TestDriver foo.xml /doc name/@last</code></p>
- <p>Linux or AIX:
+ <p>UNIX:<br/>
<code>XPathWrapper foo.xml /doc name/@last</code></p>
<p>and</p>
<p>Windows:<br/>
<code>TestDriver foo.xml /
'//name[position()="4"]/@first'</code></p>
- <p>Linux or AIX:<br/>
+ <p>UNIX:<br/>
<code>XPathWrapper foo.xml /
'//name[position()="4"]/@first'</code></p>
<note>If an XPathWrapper argument includes characters (such as *) that
the shell intercepts, enclose the argument
in double quotes.</note>
1.10 +6 -3 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.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- usagepatterns.xml 2000/10/02 12:17:06 1.9
+++ usagepatterns.xml 2000/12/12 22:47:35 1.10
@@ -135,7 +135,7 @@
XSLTInputSource theStylesheetSource(c_wstr(theXSLFileName));
// For the output, create an XSLTResultTarget object.
-const XalanDOMString theOutputFile("foo.out");
+const XalanDOMString theOutputFile("foo.out");
XSLTResultTarget theResultTarget(theOutputFile);
</source>
<p>For the other constructors you can use to set up input and output objects
(with input and output streams, for example), see <jump
href="apidocs/class_xsltinputsource.html">XSLTInputSource</jump> and <jump
href="apidocs/class_xsltresulttarget.html">XSLTResultTarget</jump>. See also
<link anchor="dom">Working with
@@ -344,7 +344,7 @@
<li>Include the ICUBridge headers.<br/><br/></li>
<li>Substitute ICU support for format-number(), xsl:number, and/or
xsl:sort.<br/><br/></li>
<li>Windows: Provide your application access to the ICUBridge
library.<br/>
- Linux or AIX: Rebuild the Xalan library to include the ICUBridge.</li>
+ Linux, AIX, or HP-UX 11: Rebuild the Xalan library to include the
ICUBridge.</li>
</ol>
<p><em>ICUBridge</em></p>
<p>All &xslt4c; references to ICU are centralized in the ICUBridge
module, which supplies the
@@ -356,8 +356,11 @@
<p>For Windows be sure &icubridge-win;,the ICUBridge library, is on the
path.</p>
<p>For Linux, rebuild &xslt4c-linuxlib; with XALAN_USE_ICU defined, and
place it on the shared library path
(LD_LIBRARY_PATH for Red Hat Linux 6.1) or copy it to /usr/lib.</p>
- <p>For AIX, rebuild &xslt4c-linuxlib;/&xslt4c-aixlib; with XALAN_USE_ICU
defined, and place it on the load library
+ <p>For AIX, rebuild &xslt4c-aixlib; with XALAN_USE_ICU defined, and
place it on the load library
path (LIB_PATH) or copy it to /usr/lib.</p>
+ <p>For HP-UX 11, rebuild &xslt4c-hplib; with XALAN_USE_ICU defined, and
place it on the shared library
+ path (LIB_PATH) or copy it to /usr/lib.</p>
+
<p><em>Number formatting</em></p>
<p>To enable ICU support for the xsl:number element and the XSLT
format-number() function, do
the following:</p>
1.6 +18 -19 xml-xalan/c/xdocs/sources/xalan/xalan-cdist.gif
<<Binary file>>
