dbertoni 2003/04/16 08:32:01
Modified: c/xdocs/sources/xalan faq.xml
Log:
FAQ contributions.
Revision Changes Path
1.38 +98 -3 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.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- faq.xml 22 Feb 2003 09:06:23 -0000 1.37
+++ faq.xml 16 Apr 2003 15:32:01 -0000 1.38
@@ -96,11 +96,11 @@
<th>Compilers</th>
</tr>
<tr>
- <td>AIX 4.3</td>
+ <td>AIX 5.1</td>
<td>IBM C and C++ for AIX 5.02</td>
</tr>
<tr>
- <td>Solaris 2.6</td>
+ <td>Solaris 2.8</td>
<td>Sun Workshop 6 update 2</td>
</tr>
<tr>
@@ -109,7 +109,7 @@
</tr>
<tr>
<td>Red Hat Linux 7.2</td>
- <td>gcc 3.1</td>
+ <td>Intel C++ Compiler, version 6</td>
</tr>
</table>
<p>For more details see: <link idref="readme" anchor="unix">Steps for doing
a UNIX build</link>.</p>
@@ -231,6 +231,101 @@
<faq title="Patches">
<q>Who do I submit patches to?</q>
<a><p>Your contributions are much appreciated! Please e-mail your patches to
<human-resource-ref idref="xalandev"/>.</p></a>
+</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>
+ <a>
+ <p>Output to a file:</p>
+ <ul>
+ <li> See this <jump
href="http://marc.theaimsgroup.com/?l=xalan-c-users&m=104791991207944&w=2";>mailing
list post</jump>. The short answer: use LocalFileFormatTarget or a DOMWriter
(gotten from DOMImplementation). Note that these are actually &xml4c; classes,
so you will find more extensive API documentation at the <jump
href="http://xml.apache.org/xerces-c/index.html";>&xml4c; website</jump>.</li>
+ </ul>
+ <p>Output to an in-memory string:</p>
+ <ul>
+ <li>Same as to a file, only you use
MemBufFormatTarget.</li>
+ </ul>
+ <p>Input to another tranformation:</p>
+ <ul>
+ <li>The output parameter of XalanTransformer::transform
is an XSLTResultTarget which can be constructed with: a string, a file name, an
output stream, or a FormatterListener. Any of these could be used as the input
to another transformation, but the FormatterToSourceTree is probably the best
for efficiency reasons.</li>
+ </ul>
+ </a>
+</faq>
+
+<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>
+ </a>
+
+</faq>
+
+<faq title="Manipulating XalanDocument DOM">
+ <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>
+ </a>
+
+</faq>
+
+<faq title="Changing Where Error Output is Sent">
+ <q>XalanTransformer outputs errors to the console. How do I, for
example, output error to a file?</q>
+ <a>
+ <p>By default, XalanTransformer creates a
XalanTransformerProblemListener (subclass of ProblemListener) that outputs
erros to std::cerr. To change this you can:</p>
+ <ul>
+ <li>Redirect cerr somewhere else</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>
+ </a>
+</faq>
+
+<faq title="Programmatic Error Information">
+ <q>How do I (programmatically) get the filename, line, column, etc. for
an error?</q>
+ <a>
+ <p>Create a custom ErrorHandler (a &xml4c; class) and call
XalanTransformer::setErrorHnadler before parsing any sources.</p>
+ </a>
+</faq>
+
+<faq title="String Transcoding">
+ <q>How do I make a char* out of XalanDOMString (or vice-versa)?</q>
+ <a>
+ <p>See the static method XalanDOMString::transcode, or the
functions TranscodeToLocalCodePage in the API documentation. However, you
should be very careful when transcoding Unicode characters to the local code
page, because not all Unicode characters can be represented.</p>
+ </a>
+
+</faq>
+
+<faq title="Error Code/Exception Summary">
+<q>Is there a table of error codes somewhere? How about a summary of what
methods throw which exceptions?</q>
+<a>
+<p>There isn't, but we're working on it.</p>
+</a>
+</faq>
+
+<faq title="Extension Functions">
+ <q>The xalan extension functions (xalan:execute, etc.) don't work for
me. Help!</q>
+ <a>
+ <p>Did you declare the namespace on the xsl:stylesheet or
xsl:transform element? It should look like this: </p>
+ <p><xsl:stylesheet version="1.0"
xmlns:xalan="http://xml.apache.org/xalan"> ...rest of stylesheet</p>
+ <p>If you did and you still have problems, you might want to
ask the mailing list.</p>
+ </a>
+</faq>
+
+<faq title="Windows 95/98">
+ <q>Why can't I ouput my results to a file on Windows 95/98?</q>
+ <a>
+ <p>Well, you can, but it doesn't always work. Neither Windows 95 or 98
are supported or tested. There have been reporst of problems on it, especially
regarding Unicode support. See <jump
href="http://marc.theaimsgroup.com/?l=xalan-dev&m=99840914524755&w=2";>this
post</jump> and <jump
href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3825";>this bug</jump>.
+ </p>
+ </a>
+</faq>
+
+<faq title="format-number and ICU">
+ <q>Why does Xalan emit an error message when using the XPath function
format-number with more than one parameter?</q>
+ <a>
+ <p>Did you build with ICU support? See <link
idref="usagepatterns" anchor="icu">Using the International Components for
Unicode (ICU)</link>.</p>
+ </a>
</faq>
</faqs>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
