dleslie 01/12/20 14:12:30
Modified: c/xdocs/sources/xalan commandline.xml faq.xml getstarted.xml
index.xml readme.xml samples.xml usagepatterns.xml
Log:
More updates for release 1.3.
Revision Changes Path
1.22 +3 -3 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.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- commandline.xml 2001/12/20 13:57:15 1.21
+++ commandline.xml 2001/12/20 22:12:29 1.22
@@ -63,7 +63,7 @@
<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="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">
@@ -159,9 +159,9 @@
<li>Build Xalan.exe and/or TestXSLT.exe.</li>
</ol>
</s3>
- <s3 title="Rebuilding testXSLT in UNIX">
+ <s3 title="Rebuilding Xalan and/or testXSLT in UNIX">
<p>In the Linux, AIX, HP-UX 11, and Solaris builds &solarisbuild;, the
ICUBridge is in the core Xalan library (&xslt4c-linuxlib; in Linux;
&xslt4c-aixlib; in
- AIX; &xslt4c-hplib; in HP-UX 11; &xslt4c-solarislib; lib; in Solaris ),
so you must rebuild this library along with Xalan and/or testXSLT.</p>
+ 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>
1.26 +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.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- faq.xml 2001/12/20 13:57:15 1.25
+++ faq.xml 2001/12/20 22:12:29 1.26
@@ -62,12 +62,12 @@
</tr>
<tr>
<td>AIX 4.3</td>
- <td>IBM C and C++ for AIX 3.6.6</td>
+ <td>IBM C and C++ for AIX 5.02</td>
<td>Yes</td>
</tr>
<tr>
<td>Solaris 2.6 &solarisbuild;</td>
- <td>Workshop 4.2</td>
+ <td>[Workshop 4.2]</td>
<td>Yes</td>
</tr>
<tr>
1.29 +4 -4 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.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- getstarted.xml 2001/12/20 13:57:15 1.28
+++ getstarted.xml 2001/12/20 22:12:29 1.29
@@ -22,9 +22,9 @@
<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"/>. This Red Hat Linux 6.1 distribution was built
with egcs-2.91.66 and glibc-2.1.2-11.</p>
-<p>For the AIX build, download <resource-ref idref="xslt4c-aix-download"/>.
This AIX 4.3 distribution was built with IBM C and C++ for AIX 3.6.6.</p>
+<p>For the AIX build, download <resource-ref idref="xslt4c-aix-download"/>.
This AIX 4.3 distribution was built with IBM C and C++ for AIX 5.02.</p>
<p>For the HP-UX 11 build, download <resource-ref
idref="xslt4c-hp-ux-download"/>. This HP-UX 11 distribution was built with aCC
A.03.27.</p>
-<p>For the Solaris build, download <resource-ref
idref="xslt4c-Solaris-download"/>. This Solaris distribution was built with
Workshop 4.2.</p>
+<p>For the Solaris build, download <resource-ref
idref="xslt4c-Solaris-download"/>.[This Solaris distribution was built with
Workshop 4.2.]</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>
<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>
@@ -61,7 +61,7 @@
<li>The Xalan-C++ shared library: &xslt4c-solarislib;</li>
<li>The Xerces-C++ shared library: &xml4c-solarislib;</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/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>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 Xalan or 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 the Xalan and/or
TestXSLT executable</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 or Solaris 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>
@@ -104,7 +104,7 @@
<p>For more information about the samples, see <link
idref="samples">&xslt4c; Samples</link>.</p>
</s2><anchor name="commandline"/>
<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
+<p>The Xalan executable lets you perform transformations from the command
line. The command line for
most standard transformations is as follows:</p>
<p><code>Xalan -o <ref>outputfile</ref> <ref>xmlSource</ref>
<ref>stylesheet</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>
1.26 +3 -3 xml-xalan/c/xdocs/sources/xalan/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/index.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- index.xml 2001/12/20 13:57:15 1.25
+++ index.xml 2001/12/20 22:12:29 1.26
@@ -92,7 +92,7 @@
<tr>
<td>AIX 4.3</td>
<td><resource-ref idref="xslt4c-aix-download"/></td>
- <td>IBM C and C++ for AIX 3.6.6</td>
+ <td>IBM C and C++ for AIX 5.02</td>
</tr>
<tr>
<td>HP-UX 11</td>
@@ -102,8 +102,8 @@
<tr>
<td>Solaris 2.6</td>
<td><resource-ref idref="xslt4c-Solaris-download"/>*<br/>
- *Use GNU tar to untar; see <link idref="faq"
anchor="gnutar">FAQs</link></td>
- <td>Workshop 4.2</td>
+ [*Use GNU tar to untar; see <link idref="faq"
anchor="gnutar">FAQs</link>]</td>
+ <td>[Workshop 4.2]</td>
</tr>
</table>
<p>Volunteers are more than welcome to help develop builds for other
platforms!</p>
1.32 +6 -6 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.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- readme.xml 2001/12/20 13:57:15 1.31
+++ readme.xml 2001/12/20 22:12:29 1.32
@@ -71,7 +71,7 @@
<anchor name="status"/>
<s2 title="Status">
<ul>
- <li><link anchor="done">Changes since &xslt4c; version 1.1</link></li>
+ <li><link anchor="done">Changes since &xslt4c; version 1.2</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>
@@ -143,10 +143,10 @@
<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/>
- If you want TestXSLT to use ICU support for number formatting and
sorting, install the ICU,
+ If you want the Xalan and/or testXSLT executable to use ICU support
for number formatting and sorting, install the ICU,
uncomment the <code>#define XALAN_USE_ICU</code> statement in
process.cpp, and use the Visual C++
- Project Dependencies command to add ICUBridge to the list of TestXSLT
dependencies (see <link idref="commandline"
- anchor="icu">Enabling ICU support for TestXSLT</link>).<br/><br/></li>
+ Project Dependencies command to add ICUBridge to the list of
XalanTransformer and/or TestXSLT dependencies (see <link idref="commandline"
+ anchor="icu">Enabling ICU support for the Xalan and/or TestXSLT
executable</link>).<br/><br/></li>
<li>Use Visual C++ to open the Xalan workspace from the
xml-xalan\c\Projects\Win32\VC6.
<br/><br/></li>
<li>Use Visual C++ to rebuild everything or specific dynamic link
libraries and executables of
@@ -185,8 +185,8 @@
<code>make</code><br/>
or<br/>
<code>make
<ref>targ</ref></code><br/><br/>
- where <ref>targ</ref> is ommitted or is <code>all</code> (rebuild
all), <code>lib</code> (the XSLT libary), or
- <code>testXSLT</code> (the testSXSLT executable). ICUBridge is
included in the build of TestXSLT if XALAN_USE_ICU is
+ where <ref>targ</ref> is ommitted or is <code>all</code> (rebuild
all), <code>lib</code> (the XSLT libary), <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.<br/><br/></li>
</ol>
<note>The command you use for setting environment variables depends on
the shell you are
1.34 +1 -1 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.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- samples.xml 2001/12/20 13:57:15 1.33
+++ samples.xml 2001/12/20 22:12:29 1.34
@@ -71,7 +71,7 @@
<li><link anchor="threadsafe">ThreadSafe</link></li>
<li><link anchor="xpathwrapper">XPathWrapper</link></li>
<li><link anchor="simplexpathapi">SimpleXPathAPI</link></li>
- <li><link anchor="simplexapthcapi">SimpleXPathCAPI</link></li>
+ <li><link anchor="simplexpathcapi">SimpleXPathCAPI</link></li>
<li><link anchor="serializenodeset">SerializeNodeSet</link></li>
<li><link anchor="externalfunctions">ExternalFunctions</link></li>
<li><link anchor="apachemodulexslt">ApacheModuleXSLT</link></li>
1.32 +14 -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.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- usagepatterns.xml 2001/12/20 13:57:15 1.31
+++ usagepatterns.xml 2001/12/20 22:12:29 1.32
@@ -154,8 +154,12 @@
theXalanTransformer.transform("foo.xml","foo.xsl","foo-out.xml")</source>
<note>If the expression is a string, enclose it in single quotes to make it
a string expression.</note>
<p>You can include the -param flag with two arguments when you call the
<link idref="commandline">command line utility</link>. The first argument is
the parameter name or key, and the second argument is the string expression (in
single quotes). For example:</p>
+<p><code>Xalan -p param1 'boo' foo.xml foo.xsl</code></p>
+<p>or</p>
<p><code>TestXSLT -in foo.xml -xsl foo.xsl -param param1 'boo'</code></p>
<p>If the string expression includes spaces or other characters that the
shell intercepts, first enclose the string in single quotes so &xslt4c;
interprets it as a string expression, and then enclose the resulting string in
double quotes so the shell interprets it as a single argument. For example:</p>
+<p><code>Xalan -p "'hello there'" foo.xml foo.xsl</code></p>
+<p>or</p>
<p><code>TestXSLT -in foo.xml -xsl foo.xsl -param param1 "'hello
there'"</code></p>
<p>The <link idref="samples"
anchor="usestylesheetparam">UseStylesheetParam</link> sample application also
uses a command-line parameter.</p>
</s2><anchor name="incremental"/>
@@ -245,7 +249,12 @@
XMLFileReporter &logFile)
{
DOMParser the Parser;
+
+ // You MUST instruct the Xerces DOMParser NOT to create a DOM_XMLDecNode
+ // in the DOM to represent the XML declaration. See "Limitations" above.
theParser.setToCreateXMLDeclTypeNode(false);
+
+ // Turn on validatiion and namespace support.
theParser.setDoValidation(true);
theParser.setDoNamespaces(true);
@@ -253,7 +262,10 @@
DOM_Document theDOM = theParser.getDocument();
theDOM.normalize();
XercesDOMSupport theDOMSupport;
- XercdesParserLiaison theParserLiaison(theDOMSupport);
+ XercesParserLiaison theParserLiaison(theDOMSupport);
+
+ // Use the DOM to create a XercesDOMWrapperParsedSource,
+ // which you can pass to the transform method.
try
{
const XercesDOMWrapperParsedSource parsedSource(
@@ -288,7 +300,7 @@
<li>Result tree generation events</li>
</ul>
<p>To construct a TraceListener with TraceListenerDefault, you need a
PrintWriter and a boolean for each of these four tracing options. You can then
use the XSLTEngimeImpl setTraceSelects and addTraceListener methods to add the
TraceListener to an XSLTProcessor. See the <link idref="samples"
anchor="tracelisten">TraceListen</link> sample application.</p>
-<p>The <link idref="commandline">command-line utility (testXSLT)</link> and
TraceListen both use TraceListenerDefault to write events to the screen.</p>
+<p>The <link idref="commandline" anchor="testxslt">testXSLT command-line
utility</link> and TraceListen both use TraceListenerDefault to write events to
the screen.</p>
</s2><anchor name="icu"/>
<s2 title="Using the ICU">
<p>You can use the <resource-ref idref="icu"/> to extend support for
encoding, number
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
