dleslie 01/08/14 10:41:48
Modified: c/xdocs/sources/xalan commandline.xml faq.xml getstarted.xml
overview.xml resources.xml samples.xml
Log:
Updates for 1.2
Revision Changes Path
1.19 +13 -13 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.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- commandline.xml 2001/02/14 20:10:50 1.18
+++ commandline.xml 2001/08/14 17:41:48 1.19
@@ -62,24 +62,24 @@
<s1 title="&xslt4c; Command-Line Utility">
<ul>
<li><link anchor="use">Using the Command-Line Utility</link></li>
-<li><link anchor="icu">Enabling ICU support for TestXSLT</link></li>
+<li><link anchor="icu">Enabling ICU support for testXSLT</link></li>
</ul><anchor name="use"/>
<s2 title="Using the Command-Line Utility">
<p>To perform a transformation, you can call &xslt4c; from the command
line (or script),
or from within an application (see <link idref="usagepatterns">Usage
Patterns</link>).</p>
- <p>TestXSLT provides a command-line interface
+ <p>The testXSLT executable provides a command-line interface
for performing XSL transformation. 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</link> to include the build
directory.<br/><br/></li>
- <li>Call the TestXSLT executable with the appropriate flags and
+ <li>Call the testXSLT executable with the appropriate 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>
+ <code>testXSLT -IN foo.xml -XSL foo.xsl -OUT foo.out</code>
</li></ol>
<p>The command line utility can take the following flags and arguments
(the flags are case insensitive):</p>
<source>-IN inputXMLURL
@@ -114,21 +114,21 @@
<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/>
+ <code>testXSLT -PARAM <ref>name expression</ref></code><br/>
To set the parameter to a string value, enclose the string in single
quotes (') to
make it an expression.</p>
</s2><anchor name="icu"/>
- <s2 title="Enabling ICU support for TestXSLT">
+ <s2 title="Enabling ICU support for testXSLT">
<p>You can set up the <resource-ref idref="icu"/> to enhance the
support that &xslt4c; provides for encoding, number
formatting, and sorting. For more information, see <link
idref="usagepatterns" anchor="icu">Using the ICU</link>.</p>
- <p>If you have built and integrated the ICU with &xml4c;, TestXSLT
(like any &xslt4c; application) automatically uses ICU
+ <p>If you have built and integrated the ICU with &xml4c;, testXSLT
(like any &xslt4c; application) automatically uses ICU
support for output encoding. See <resource-ref
idref="xerces-build-icu"/>.</p>
- <p>TestXSLT also conditionally includes ICU support for number
formatting and sorting. Look in process.cpp for the
+ <p>The testXSLT executable also conditionally includes ICU support for
number formatting and sorting. Look in process.cpp for the
<code>#if defined(XALAN_USE_ICU)</code> blocks. In these blocks,
process.cpp #includes the ICUBridge headers, and
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 TestXSLT with the ICU enabled (see below).</li>
+ <li>Rebuild testXSLT with the ICU enabled (see below).</li>
</ol>
<s3 title="Rebuilding TestXSLT in Windows">
<ol>
@@ -137,18 +137,18 @@
<li>Build TestXSLT.exe.</li>
</ol>
</s3>
- <s3 title="Rebuilding TestXSLT in UNIX">
+ <s3 title="Rebuilding 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 TestXSLT.</p>
+ AIX; &xslt4c-hplib; in HP-UX 11; &xslt4c-solarislib; in Solaris), 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 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>
+ 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>
+ run the make, and testXSLT does not link with ICUBridge.</note>
</s3>
</s2>
</s1>
1.20 +2 -2 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.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- faq.xml 2001/05/07 15:26:32 1.19
+++ faq.xml 2001/08/14 17:41:48 1.20
@@ -89,7 +89,7 @@
<a><p>The Standard Template Library, or STL, is a C++ library of container
classes, algorithms, and iterators; it provides many of the basic computer
science algorithms and data structures. &xslt4c; implementation uses the SLT.
STLport ports SGI STL to any platform possible and provides all necessary
wrap-ups installed. If your compiler does not support the STL or its
implementation is out of date, you will need to install the STLPort.</p>
-<p>The STLPort is available for download from the site: <jump
href="http://www.stlport.org/";>http://www.stlport.org/</jump>.</p>
+<p>The STLPort version 4.0 for download from the site: <jump
href="http://www.stlport.org/";>http://www.stlport.org/</jump>.</p>
<p>For more details on the STL, see: <jump
href="http://www.sgi.com/tech/stl/stl_introduction.html";>http://www.sgi.com/tech/stl/stl_introduction.html</jump>.</p></a>
</faq>
@@ -188,7 +188,7 @@
an invalid structure. For example, text nodes are not allowed as
children
of the document node.</p>
- <p>This is also a very common error when attempting to transform
to DOM.
+ <p>This is a common error when attempting to transform to DOM.
Source documents and stylesheets that might produce valid
serialized XML
might not produce value DOM. The usual suspect is text nodes being
generated before the document element is generated.</p>
1.27 +5 -5 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.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- getstarted.xml 2001/06/08 18:54:48 1.26
+++ getstarted.xml 2001/08/14 17:41:48 1.27
@@ -39,25 +39,25 @@
<p><em>Linux</em></p>
<ul>
- <li>The executable: TestXSLT</li>
+ <li>The executable: testXSLT</li>
<li>The Xalan-C++ shared library: &xslt4c-linuxlib;</li>
<li>The Xerces-C++ shared library: &xml4c-linuxlib;</li>
</ul>
<p><em>AIX</em></p>
<ul>
- <li>The executable: TestXSLT</li>
+ <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 executable: testXSLT</li>
<li>The Xalan-C++ shared library: &xslt4c-hplib;</li>
<li>The Xerces-C++ shared library: &xml4c-hplib;</li>
</ul>
<p><em>Solaris</em></p>
<ul>
- <li>The executable: TestXSLT</li>
+ <li>The executable: testXSLT</li>
<li>The Xalan-C++ shared library: &xslt4c-solarislib;</li>
<li>The Xerces-C++ shared library: &xml4c-solarislib;</li>
</ul>
@@ -106,7 +106,7 @@
<s2 title="Performing your own transformations from the command line">
<p>TestXSLT provides a basic utility for performing transformations from the
command line. The command line for
most standard transformations is as follows:</p>
-<p><code>TestXSLT -in <ref>xmlSource</ref> -xsl <ref>stylesheet</ref> -out
<ref>outputfile</ref></code></p>
+<p><code>testXSLT -in <ref>xmlSource</ref> -xsl <ref>stylesheet</ref> -out
<ref>outputfile</ref></code></p>
<p>where <ref>xmlSource</ref> is the XML source file name,
<ref>stylesheet</ref> is the XSL stylesheet file name, and
<ref>outputfile</ref> is the output file name.</p>
<p>If you want the output to be displayed on the screen, simply omit the
-out flag and outputfile.</p>
<p>You can use this utility to try out XSL stylesheets you have written, to
make sure they do what you expect with the XML source files they are designed
to transform. The utility provides useful messages if the source file or
stylesheet is not well formed. If you include a DOCTYPE statement in your XML
source files and include the -validate flag on the command line, the utility
will also let you know whether the XML document is valid (conforms to that
DOCTYPE). For more information, see <link idref="commandline">Command-Line
Utility</link>.</p>
1.15 +25 -15 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.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- overview.xml 2001/02/16 21:41:48 1.14
+++ overview.xml 2001/08/14 17:41:48 1.15
@@ -119,31 +119,41 @@
<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 XSL Companion, 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>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 (Web pages, but
designed for sequential reading)</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>Doug Tidwell's <jump
href="http://www.oreilly.com/catalog/xslt/";>XSLT</jump>, O'Reilly,
2001<br/><br/></li>
+ <li>Bob Ducharme's <jump
href="http://www.manning.com/ducharme/index.html";>XSLT Quickly</jump>, Manning
Publications,
+ 2001<br/><br/></li>
+ <li>John Robert Gardner and Zarella Rendon's
+ <jump
href="http://vig.prenhall.com/catalog/academic/product/1,4096,0130404462,00.html";>XSLT
and XPath: A Guide to
+ Transformations</jump>, Prentice-Hall, 2001<br/><br/></li>
+ <li>Michael Kay's <jump
href="http://www.wrox.com/Books/Book_Details.asp?ISBN=1861005067";>XSLT
Programmer's
+ Reference</jump>, 2nd ed., Wrox Press, 2001<br/><br/></li>
+ <li>Steven Holzner's <jump
href="http://www.newriders.com/books/title.cfm?isbn=0735711364";>Inside
XSLT</jump>,
+ New Riders, 2001<br/><br/></li>
+ <li>Neil Bradley's <jump
href="http://www.awlonline.com/product/0,2627,0201674874,00.html";>XSL
Companion</jump>,
+ Addison-Wesley, 2000<br/><br/></li>
+ <li>Khun Yee Fung's <jump
href="http://www.awlonline.com/product/0,2627,0201711036,00.html";>XSLT: Working
with XML and
+ HTML</jump>, Addison-Wesley, 2001<br/><br/></li>
+ <li>Dave Pawson's <resource-ref idref="dpawsonxslfaq"/> to search
out particular answers and techniques<br/><br/></li>
+ <li>Miloslav Nic's <jump
href="http://zvon.vscht.cz/HTMLonly/XSLTutorial/Books/Book1/index.html";>XSL
Tutorial</jump>,
+ a collection of stylesheet examples<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>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 <resource-ref
idref="dpawsonxslfaq"/><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>Objects by Design;'s <jump
href="http://objectsbydesign.com/projects/xslt/xslt_by_example.html";>XSLT by
- Example</jump><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>
+ XML transformations) and their related <jump
href="http://objectsbydesign.com/projects/xslt/xslt_by_example.html";>XSLT
+ by Example</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</li>
+ Designers</jump><br/><br/></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>
1.14 +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.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- resources.xml 2001/08/09 20:10:36 1.13
+++ resources.xml 2001/08/14 17:41:48 1.14
@@ -26,7 +26,7 @@
<resource id="xslt4c-solaris-download" title="&xslt4c-dist;-solaris.tar.gz"
location="http://xml.apache.org/dist/xalan-c/&xslt4c-dist;-solaris.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"/>
+<resource id="icu-download" title="International Components for Unicode
(ICU) 1.8.1 source files"
location="http://oss.software.ibm.com/developerworks/opensource/icu/project/download/index.html"/>
<resource id="xerces-build-icu" title="Building ICU for &xml4c;"
location="http://xml.apache.org/xerces-c/build.html#BuildICU"/>
<resource id="stlport" title="STLport" location="http://www.stlport.org/"/>
1.30 +16 -10 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.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- samples.xml 2001/08/10 19:16:43 1.29
+++ samples.xml 2001/08/14 17:41:48 1.30
@@ -99,10 +99,10 @@
<p>What it does: XalanTransform uses the XalanTransformer class and the
associated C++ API to apply an XSL stylesheet file to an XML document file and
write
the transformation output to either an output file or to a stream.
XalanTransform takes command-line
arguments for the XML document to be transformed, the XSL stylesheet to
apply, and an optional output file argument. If you omit
- the third argument, XalanTransform writes the transformation output to a
stream that is sent to standard out (the screen).</p>
+ the third argument, XalanTransform writes the transformation output to a
stream that is sent to standard out (the console).</p>
<p>You can run XalanTransform from the XalanTransform subdirectory
with</p>
<p><code>XalanTransform foo.xml foo.xsl foo.out</code></p>
- <p>Omit the third argument to write the transformation result to the
screen. See also: <link idref="usagepatterns"
+ <p>Omit the third argument to write the transformation result to the
console. See also: <link idref="usagepatterns"
anchor="xalantransformer">Using the XalanTransformer class.</link>.</p>
</s2><anchor name="simpletransform"/>
<s2 title="SimpleTransform">
@@ -139,7 +139,7 @@
anchor="incremental">Processing output incrementally</link>.</p>
<p>You can run it from the XalanTransformerCallback subdirectory with</p>
<p><code>XalanTransformerCallback foo.xml foo.xsl [foo.out]</code></p>
- <note>If you omit the third argument, the transformation result is written
to the screen.</note>
+ <note>If you omit the third argument, the transformation result is written
to the console.</note>
</s2>
<anchor name="tracelisten"/>
<s2 title="TraceListen">
@@ -148,15 +148,21 @@
<p>You can run it from the TraceListen subdirectory with</p>
<p><code>TraceListen <ref>traceFlags</ref></code></p>
<p>where <ref>traceFlags</ref> is one or more of the following:</p>
- <p> <code>-TT</code> (Trace the templates as they are being
called)</p>
- <p> <code>-TG</code> (Trace each result tree generation
event)</p>
- <p> <code>-TS</code> (Trace each selection event)</p>
- <p> <code>-TTC</code> (Trace the template children as they are
being processed)</p>
+ <p> <code>-tt</code> (Trace the templates as they are being
called)</p>
+ <p> <code>-tg</code> (Trace each result tree generation
event)</p>
+ <p> <code>-ts</code> (Trace each selection event)</p>
+ <p> <code>-ttc</code> (Trace the template children as they are
being processed)</p>
<p>These flags are also available in the <link
idref="commandline">command-line utility (TestXSLT)</link>.</p>
<p>The core of this example is the following fragment:</p>
<source>// Set up a diagnostic writer to be used by the TraceListener...
XalanStdOutputStream theStdErr(cerr);
XalanOutputStreamPrintWriter diagnosticsWriter(theStdErr);
+// Make sure that error reporting, which includes any TraceListener
+// output does not throw exceptions when transcoding, since that could
+// result in an exception being thrown while another exception is active.
+// In particular, characters that the TraceListener writes might not be
+// representable in the local code page.
+theStdErr.setThrowTranscodeException(false);
// Set up the TraceListener...
// traceTemplates, traceTemplateChildren, traceGenerationEvent,
@@ -190,7 +196,7 @@
</s2><anchor name="threadsafe"/>
<s2 title="ThreadSafe (Windows32 Only)">
<p>What it does: Multiple threads use a single compiled stylesheet
(StylesheetRoot) and DOM source tree (XalanNode) to perform
- transformations concurrently. The application tracks the progress of the
threads in messages to the screen, and each thread
+ transformations concurrently. The application tracks the progress of the
threads in messages to the console, and each thread
writes its own output file. Imagine a server application responding to
multiple clients who happen to request the same
transformation.</p>
<note>This sample uses Windows libraries, but could readily be adapted to
run under Linux, AIX, or other environments. It
@@ -234,7 +240,7 @@
<p><code>SimpleXPathAPI foo.xml /doc name/@last</code></p>
<p>and</p>
<p><code>SimpleXPathAPI foo.xml /
'//name[position()="4"]/@first'</code></p>
- <note>If a SimpleXPathAPI argument includes characters (such as *) that
the shell intercepts, enclose the argument
+ <note>If a SimpleXPathAPI argument includes characters (such as *) that
the shell interprets incorrectly, enclose the argument
in double quotes.</note>
<p>See also: <link idref="usagepatterns" anchor="xpath">Working with
XPath expressions</link>.</p>
</s2><anchor name="externalfunctions"/>
@@ -271,7 +277,7 @@
/usr/lib; see <link idref="getstarted" anchor="path">Setting up the
path/library path</link>), and copy the Apache module to
/usr/lib/apache.<br/><br/></li>
<li>Add LoadModule and (UNIX only) AddModule entries to the Apache
configuration file: httpd.conf.<br/><br/>
- Windows: <code>LoadModule mod_xslt
xml-xalan\c\Build\Win32\VC6\Release\ApacheModuleXSLT.dll</code><br/><br/>
+ Windows: <code>LoadModule xslt_module
xml-xalan\c\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/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
