dbertoni 2003/04/18 17:51:14
Modified: c/xdocs/sources/xalan extensions.xml extensionslib.xml
faq.xml usagepatterns.xml
Log:
More doc updates.
Revision Changes Path
1.18 +3 -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.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- extensions.xml 4 Mar 2003 22:35:14 -0000 1.17
+++ extensions.xml 19 Apr 2003 00:51:13 -0000 1.18
@@ -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 elements</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 functionss</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>
@@ -95,6 +95,8 @@
#include <util/PlatformUtils.hpp>
#include <XalanTransformer/XalanTransformer.hpp>
#include <XPath/XObjectFactory.hpp>
+
+XALAN_CPP_NAMESPACE_USE
// This class defines a function that will return the square root
// of its argument.
1.4 +2 -2 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.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- extensionslib.xml 11 Sep 2002 18:03:53 -0000 1.3
+++ extensionslib.xml 19 Apr 2003 00:51:13 -0000 1.4
@@ -59,7 +59,7 @@
<s1 title="Extensions library">
<ul>
<li><link anchor="intro">Introduction</link></li>
-<li><link anchor="exslt">Alpha support for EXSLT extensions</link></li>
+<li><link anchor="exslt">Beta support for EXSLT extensions</link></li>
<li><link anchor="xalanns">Xalan namespace</link></li>
<li><link anchor="nodeset">nodeset</link></li>
@@ -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.4 includes alpha
implementations for
+standard extension functions to XSLT users. &xslt4c; 1.4 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>
1.41 +9 -10 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.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- faq.xml 18 Apr 2003 23:16:05 -0000 1.40
+++ faq.xml 19 Apr 2003 00:51:13 -0000 1.41
@@ -234,12 +234,12 @@
</faq>
<faq title="Transformation Output Methods">
- <q>How do I output a transformation to [a DOM, a file, an in-memory
string, as input to another transformation]?</q>
+ <q>How do I output a transformation to a DOM, a file, an in-memory
buffer, or as input to another transformation? Since the C++ language can
automatically construct an XSLTResultTarget from any of its constructor's
argument types, you usually don't need to create one explicitly.</q>
<a>
<p>The output parameter of XalanTransformer::transform() is an
XSLTResultTarget which has many constructors.</p>
<p>Output to a file:</p>
<ul>
- <li>The easiest way is to use a null-terminated string
containing the file name to create an XSLTResultTarget. Or, use an instance of
std::ofstream or std::ostringstream to create an XSLTResultTarget.</li>
+ <li>The easiest way is to use a null-terminated string
containing the file name to create an XSLTResultTarget. Or, use an instance of
std::ofstream. The command line executables, and many of the sample
applications use file names, so take a look through the source code for more
information.</li>
</ul>
<p>Output to an in-memory buffer:</p>
<ul>
@@ -255,16 +255,15 @@
<faq title="std:istrstream Problems Using Sun's Forte/Workshop Compiler">
<q>Why won't XSLTInputSource work with std::istrstream on Sun Solaris
using Forte/Sun Workshop compiler?</q>
<a>
- <p>There is a bug in Sun's C++ standard library implementation.
See <jump href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14176";>this
bug</jump>. The short answer is that you need to get a patch. The bug gives
some sample (straight C++, no &xslt4c; library needed) to see if your setup has
the bug. There is also a link to the patch.
- </p>
+ <p>There is a bug in Sun's C++ standard library implementation;
see <jump href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14176";>this
bug</jump>. The short answer is that you need to get a patch. The bug gives
some sample (straight C++, no &xslt4c; library needed) to see if your setup has
the bug. There is also a link to the patch.</p>
</a>
</faq>
-<faq title="Manipulating XalanDocument DOM">
+<faq title="Modifying an instance of XalanDocument">
<q>My transformation outputs to a XalanDocument (actually
XalanSourceTreeDocument underneath) but W3C DOM functions like
DOMElement::setAttribute don't work! Am I going crazy or what?</q>
<a>
- <p>No, you aren't going crazy. The Xalan preferred DOM is
read-only for efficiency reasons. If you need a DOM that supports
modifications, use the Xerces DOM instead. See the TransformToXercesDOM sample
for more information.</p>
+ <p>No, you aren't going crazy. Xalan's default source tree is
read-only for efficiency. If you need a DOM that supports modifications, use
the Xerces DOM instead. See the TransformToXercesDOM sample for more
information.</p>
</a>
</faq>
@@ -274,19 +273,19 @@
<a>
<p>By default, XalanTransformer creates a
XalanTransformerProblemListener (a subclass of ProblemListener) that writes
output to std::cerr. To change this you can:</p>
<ul>
- <li>Redirect cerr somewhere else</li>
+ <li>Redirect std::cerr from the command line.</li>
<li>Call XalanTranformer::setWarningStream with a
different std::ostream before calling XalanTransformer::transform.</li>
<li>Instantiate your own
XalanTransformerProblemListener with a different output stream and call
XalanTransformer::setProblemListener() before calling
XalanTransformer::transform().</li>
<li>Subclass some ProblemListener type and do custom
handling of errors (you still then need to tell XalanTransformer instances to
use your ProblemListener.)</li>
</ul>
- <p>In most case you probably want to do one of the first two.
:)</p>
+ <p>In most case you probably want to do one of the first
two.</p>
</a>
</faq>
<faq title="Programmatic Error Information">
- <q>How do I (programmatically) get the filename, line, column, etc. for
an error?</q>
+ <q>How do I programmatically get the file name, line number, and column
number for an error in an XML file?</q>
<a>
- <p>Create a custom ErrorHandler (a &xml4c; class) and call
XalanTransformer::setErrorHnadler before parsing any sources.</p>
+ <p>Create a custom ErrorHandler (a &xml4c; class) and call
XalanTransformer::setErrorHandler before parsing any sources.</p>
</a>
</faq>
1.39 +2 -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.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- usagepatterns.xml 12 Feb 2003 09:28:53 -0000 1.38
+++ usagepatterns.xml 19 Apr 2003 00:51:13 -0000 1.39
@@ -698,7 +698,7 @@
xalan);
</source>
<note>
- If the XML input file contains a stylesheet processing
instruction that you want to use, include an empty string ("") for the
xslfilename argument.
+ If the XML input file contains a stylesheet processing
instruction that you want to use, use an empty XSLTInputSource for the
stylesheet argument.
</note>
</s3>
<s3 title="5. Shut down Xalan">
@@ -711,7 +711,7 @@
The <jump href="apidocs/XalanCAPI.h.html">Xalan C API</jump> supports
approximately the same set of options as the C++ API. In particular, you can
</p>
<ul>
- <li>Use stylesheet processing instructions (PI) to supply the
stylesheet. Simply supply an empty string ("") for the XSL file
name.<br/><br/></li>
+ <li>Use stylesheet processing instructions (PI) to indicate the URI
of the stylesheet. Supply NULL for the stylesheet argument.<br/><br/></li>
<li>Set stylesheet parameters. Use the SetStylesheetParam()
function.<br/><br/></li>
<li>Compile stylesheets. Use the CompileStylesheet() method to
compile a stylesheet, and the TransformToFileCSS() or TransformToDataCSS()
function to use the compiled stylesheet in a transformation.<br/><br/></li>
<li>Parse XML sources. Use the XalanParseSource() or
XalanParseSouceUseXalan() method.<br/><br/></li>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
