dmitryh 2004/05/06 19:09:24
Modified: c/xdocs DoxyfileXalan
c/xdocs/sources/xalan extensions.xml extensionslib.xml
history.xml usagepatterns.xml
Added: c/xdocs/sources/xalan NET_options.jpg
Log:
Fixes for the apidocs/apiDocs issue and fix for broken links related to the
new doxygen version
Revision Changes Path
1.16 +3 -3 xml-xalan/c/xdocs/DoxyfileXalan
Index: DoxyfileXalan
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/DoxyfileXalan,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- DoxyfileXalan 7 Jan 2004 05:28:38 -0000 1.15
+++ DoxyfileXalan 7 May 2004 02:09:24 -0000 1.16
@@ -272,19 +272,19 @@
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `html' will be used as the default path.
-HTML_OUTPUT = apiDocs
+HTML_OUTPUT = apidocs
# The HTML_HEADER tag can be used to specify a personal HTML header for
# each generated HTML page. If it is left blank doxygen will generate a
# standard header.
-HTML_HEADER = html/apiDocs/header.html
+HTML_HEADER = html/apidocs/header.html
# The HTML_FOOTER tag can be used to specify a personal HTML footer for
# each generated HTML page. If it is left blank doxygen will generate a
# standard footer.
-HTML_FOOTER = html/apiDocs/footer.html
+HTML_FOOTER = html/apidocs/footer.html
# The HTML_STYLESHEET tag can be used to specify a user defined cascading
# style sheet that is used by each HTML page. It can be used to
1.25 +1 -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.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- extensions.xml 26 Apr 2004 19:24:56 -0000 1.24
+++ extensions.xml 7 May 2004 02:09:24 -0000 1.25
@@ -119,7 +119,7 @@
}</source>
</s2><anchor name="install"/>
<s2 title="Installing an extension function">
-<p><jump href="apiDocs/class_xalantransformer.html">XalanTransformer</jump>
provides methods for installing and uninstalling external functions:</p>
+<p><jump href="apidocs/classXalanTransformer.html">XalanTransformer</jump>
provides methods for installing and uninstalling external functions:</p>
<ul>
<li>installExternalFunction() makes the function available in the current
instance of XalanTransformer. Use uninstallExternalFunction() to remove the
function.<br/><br/></li>
<li>installExternalFunctionGlobal() makes the function available globally.
Use uninstallExternalFunctionGlobal() to remove the function. The global
install and uninstall operations are not thread-safe. However, all global
functions should be thread-safe, because multiple threads could call a
particular function instance at the same time.</li>
1.12 +12 -12 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.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- extensionslib.xml 26 Apr 2004 19:24:56 -0000 1.11
+++ extensionslib.xml 7 May 2004 02:09:24 -0000 1.12
@@ -41,12 +41,12 @@
<p>The source files for the implementations are in the XalanEXSLT
subdirectory of the source tree.
See</p>
<ul>
-<li><jump
href="apiDocs/XalanEXSLTCommonImpl_8hpp.html">XalanEXSLTCommonImpl</jump></li>
-<li><jump
href="apiDocs/XalanEXSLTMathImpl_8hpp.html">XalanEXSLTMathImpl</jump></li>
-<li><jump
href="apiDocs/XalanEXSLTSetImpl_8hpp.html">XalanEXSLTSetImpl</jump></li>
-<li><jump
href="apiDocs/XalanEXSLTStringImpl_8hpp.html">XalanEXSLTStringImpl</jump></li>
-<li><jump
href="apiDocs/XalanEXSLTDynamicImpl_8hpp.html">XalanEXSLTDynamicImpl</jump></li>
-<li><jump
href="apiDocs/XalanEXSLTDateTimeImpl_8hpp.html">XalanEXSLTDateTimeImpl</jump></li>
+<li><jump
href="apidocs/XalanEXSLTCommonImpl_8hpp.html">XalanEXSLTCommonImpl</jump></li>
+<li><jump
href="apidocs/XalanEXSLTMathImpl_8hpp.html">XalanEXSLTMathImpl</jump></li>
+<li><jump
href="apidocs/XalanEXSLTSetImpl_8hpp.html">XalanEXSLTSetImpl</jump></li>
+<li><jump
href="apidocs/XalanEXSLTStringImpl_8hpp.html">XalanEXSLTStringImpl</jump></li>
+<li><jump
href="apidocs/XalanEXSLTDynamicImpl_8hpp.html">XalanEXSLTDynamicImpl</jump></li>
+<li><jump
href="apidocs/XalanEXSLTDateTimeImpl_8hpp.html">XalanEXSLTDateTimeImpl</jump></li>
</ul>
<p>For the function specifications, see:</p>
<ul>
@@ -69,7 +69,7 @@
</s2>
<anchor name="nodeset"/>
<s2 title= "nodeset">
-<p>Implemented in <jump
href="apiDocs/class_functionnodeset.html">FunctionNodeSet</jump>, <code>nodeset
(result-tree-fragment)</code> casts a result tree fragment into a node-set.</p>
+<p>Implemented in <jump
href="apidocs/classFunctionNodeSet.html">FunctionNodeSet</jump>, <code>nodeset
(result-tree-fragment)</code> casts a result tree fragment into a node-set.</p>
<note>When you bind a variable to a template, rather than to the value
generated by a select expression, the data type of the variable is result tree
fragment. For more information, see <jump
href="http://www.w3.org/TR/xslt#section-Result-Tree-Fragments";>Result Tree
Fragments</jump>.</note>
<anchor name="ex-nodeset"/>
<s3 title="Example with the nodeset extension function">
@@ -105,22 +105,22 @@
</s3>
</s2><anchor name="intersection"/>
<s2 title="intersection">
-<p>Implemented in <jump
href="apiDocs/class_functionintersection.html">FunctionIntersection</jump>,
<code>intersection (node-set1, node-set2)</code> returns a node-set with all
nodes that are in ns1 and in ns2.</p>
+<p>Implemented in <jump
href="apidocs/classFunctionIntersection.html">FunctionIntersection</jump>,
<code>intersection (node-set1, node-set2)</code> returns a node-set with all
nodes that are in ns1 and in ns2.</p>
</s2><anchor name="difference"/>
<s2 title= "difference">
-<p>Implemented in <jump
href="apiDocs/class_functiondifference.html">FunctionDifference</jump>,
<code>difference(node-set1, node-set2)</code> returns a node-set with the nodes
in node-set1 and not in node-set2.</p>
+<p>Implemented in <jump
href="apidocs/classFunctionDifference.html">FunctionDifference</jump>,
<code>difference(node-set1, node-set2)</code> returns a node-set with the nodes
in node-set1 and not in node-set2.</p>
</s2><anchor name="distinct"/>
<s2 title= "distinct">
- <p>Implemented in <jump
href="apiDocs/class_functiondistinct.html">FunctionDistinct</jump>, distinct
(node-set) returns a node-set containing nodes with distinct string values. If
more than one node in the node-set
+ <p>Implemented in <jump
href="apidocs/classFunctionDistinct.html">FunctionDistinct</jump>, distinct
(node-set) returns a node-set containing nodes with distinct string values. If
more than one node in the node-set
contains the same text node value, distinct only returns the first of these
nodes that it finds.</p>
</s2><anchor name="evaluate"/>
<s2 title= "evaluate">
- <p>Implemented in <jump
href="apiDocs/class_functionevaluate.html">FunctionEvaluate</jump>,
<code>evaluate (xpath-expression)</code> returns the result of evaluating the
xpath-expression in the current
+ <p>Implemented in <jump
href="apidocs/classFunctionEvaluate.html">FunctionEvaluate</jump>,
<code>evaluate (xpath-expression)</code> returns the result of evaluating the
xpath-expression in the current
XPath expression context (automatically passed in by the extension
mechanism).</p>
<p>Use the evaluation extension function when the value of the expression is
not known until run time.</p>
</s2>
<anchor name="hassamenodes"/>
<s2 title= "hasSameNodes">
-<p>Implemented in <jump
href="apiDocs/class_functionhassamenodes.html">FunctionHasSameNodes</jump>,
<code>hasSameNodes(node-set1, node-set2)</code> returns true if both node-set1
and node-set2 contain exactly the same set of nodes.</p>
+<p>Implemented in <jump
href="apidocs/classFunctionHasSameNodes.html">FunctionHasSameNodes</jump>,
<code>hasSameNodes(node-set1, node-set2)</code> returns true if both node-set1
and node-set2 contain exactly the same set of nodes.</p>
</s2>
</s1>
1.13 +3 -3 xml-xalan/c/xdocs/sources/xalan/history.xml
Index: history.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/history.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- history.xml 26 Apr 2004 19:24:56 -0000 1.12
+++ history.xml 7 May 2004 02:09:24 -0000 1.13
@@ -98,10 +98,10 @@
<ul>
<li><link idref="extensionslib">Introduction of a library of extension
functions</link></li>
<li>Support for pre-parsed source documents and pre-compiled
stylesheets in
- <jump
href="apiDocs/class_xalantransformer.html">XalanTransformer</jump> and the C
API.</li>
- <li>Support for stylesheet params in <jump
href="apiDocs/class_xalantransformer.html">XalanTransformer</jump>
+ <jump
href="apidocs/classXalanTransformer.html">XalanTransformer</jump> and the C
API.</li>
+ <li>Support for stylesheet params in <jump
href="apidocs/classXalanTransformer.html">XalanTransformer</jump>
and the C API</li>
- <li>Support for extension functions in <jump
href="apiDocs/class_xalantransformer.html">XalanTransformer</jump></li>
+ <li>Support for extension functions in <jump
href="apidocs/classXalanTransformer.html">XalanTransformer</jump></li>
<li>Performance enhancements</li>
</ul>
</s3>
1.46 +23 -23 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.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- usagepatterns.xml 26 Apr 2004 19:24:56 -0000 1.45
+++ usagepatterns.xml 7 May 2004 02:09:24 -0000 1.46
@@ -36,11 +36,11 @@
<s2 title="Introduction">
<p>
To perform a transformation, use one of the
- <jump href="apiDocs/class_xalantransformer.html">XalanTransformer
+ <jump href="apidocs/classXalanTransformer.html">XalanTransformer
</jump> transform() methods. The transformation requires an XML
source
document and an XSL stylesheet. Both of these objects may be
represented by instances of
- <jump href="apiDocs/class_xsltinputsource.html">XSLTInputSource
+ <jump href="apidocs/classXSLTInputSource.html">XSLTInputSource
</jump>. You can construct an XSLTInputSource with a string (the
system ID for a file or URI), an input stream, or a DOM.
</p>
@@ -48,10 +48,10 @@
If you are using an XSL stylesheet to perform a series of
transformations, you can improve performance by calling transform()
with a compiled stylesheet, an instance of
- <jump href="apiDocs/class_xalancompiledstylesheet.html">
+ <jump href="apidocs/classXalanCompiledStylesheet.html">
XalanCompiledStylesheet</jump>. If you are transforming an XML
source more than once, you should call transform() with a parsed XML
- source, an instance of <jump href="apiDocs/class_xalanparsedsource">
+ source, an instance of <jump
href="apidocs/classXalanParsedSource.html">
XalanParsedSource</jump>. See <link
anchor="compiled">Performing
a series of transformations</link>.
</p>
@@ -62,14 +62,14 @@
</p>
<p>
The transformation output is represented by an
- <jump href="apiDocs/class_xsltresulttarget.html">XSLTResultTarget
+ <jump href="apidocs/classXSLTResultTarget.html">XSLTResultTarget
</jump>, which you can set up to refer to an output stream, the
system ID for a file or URI, or a Formatter for one of the various
styles of DOM output.
</p>
<p>
For detailed API documentation, see
- <jump href="apiDocs/index.html">&xslt4c; API</jump>. For an overview
+ <jump href="apidocs/index.html">&xslt4c; API</jump>. For an overview
of the command-line utility, see <link idref="commandline">
Command-Line Utility</link>.
</p>
@@ -77,7 +77,7 @@
<anchor name="xalantransformer"/>
<s2 title="Basic usage patten with the XalanTransformer C++ API">
<p>
- Using <jump
href="apiDocs/class_xalantransformer.html">XalanTransformer</jump> and the C++
API, you can perform one or more transformations as described in the following
steps.
+ Using <jump
href="apidocs/classXalanTransformer.html">XalanTransformer</jump> and the C++
API, you can perform one or more transformations as described in the following
steps.
</p>
<note>
For a working sample that illustrates these steps, see the <link
idref="samples" anchor="xalantransform">XalanTransform</link> sample.
@@ -142,11 +142,11 @@
<s3 title="5. Perform each transformation.">
<p>
You can explicitly instantiate
- <jump href="apiDocs/class_xsltinputsource.html">XSLTInputSource
+ <jump href="apidocs/classXSLTInputSource.html">XSLTInputSource
</jump> objects for the XML source document and XSL stylesheet,
- and an <jump href="apiDocs/class_xsltresulttarget.html">
+ and an <jump href="apidocs/classXSLTResultTarget.html">
XSLTResultTarget</jump> object for the output, and then call
- <jump
href="apiDocs/class_xalantransformer.html">XalanTransformer
+ <jump href="apidocs/classXalanTransformer.html">XalanTransformer
</jump> transform() with those objects as parameters. For
example:
</p>
<source>
@@ -160,8 +160,8 @@
Alternatively, you can call transform() with the strings
(system
identifiers), streams, and/or DOMs that the compiler needs to
implicitly construct the
- <jump href="apiDocs/class_xsltinputsource.html">XSLTInputSource
- </jump> and <jump href="apiDocs/class_xsltresulttarget.html">
+ <jump href="apidocs/classXSLTInputSource.html">XSLTInputSource
+ </jump> and <jump href="apidocs/classXSLTResultTarget.html">
XSLTResultTarget</jump> objects. For example:
</p>
<source>
@@ -172,9 +172,9 @@
theXalanTransformer.transform(xmlIn,xslIn,xmlOut)
</source>
<p>
- Keep in mind that <jump
href="apiDocs/class_xsltinputsource.html">
+ Keep in mind that <jump
href="apidocs/classXSLTInputSource.html">
XSLTInputSource</jump> and
- <jump
href="apiDocs/class_xsltresulttarget.html">XSLTResultTarget
+ <jump href="apidocs/classXSLTResultTarget.html">XSLTResultTarget
</jump> provide a variety of single-argument constructors that
you
can use in this manner:
</p>
@@ -255,7 +255,7 @@
</p>
<p>
To set a stylesheet parameter, use the
- <jump href="apiDocs/class_xalantransformer.html">XalanTransformer
+ <jump href="apidocs/classXalanTransformer.html">XalanTransformer
</jump> setStylesheetParam() method. The setStytlesheetParam() method
takes two arguments: the parameter name and the expression. For
example:
</p>
@@ -294,7 +294,7 @@
<anchor name="incremental"/>
<s2 title="Processing output incrementally">
<p>
- <jump href="apiDocs/class_xalantransformer.html">XalanTransformer
+ <jump href="apidocs/classXalanTransformer.html">XalanTransformer
</jump> provides a transform() method that sends the output in
blocks to a callback function, which enables you to begin processing
the output while the transformation is still in process:
@@ -324,12 +324,12 @@
the binary representation when you call transform().
</p>
<p>
- <jump href="apiDocs/class_xalantransformer.html">XalanTransformer
+ <jump href="apidocs/classXalanTransformer.html">XalanTransformer
</jump> includes methods for creating compiled stylesheets and
parsed XML documents: the compileStylesheet() method returns a
- pointer to a <jump href="apiDocs/class_xalancompiledstylesheet.html">
+ pointer to a <jump href="apidocs/classXalanCompiledStylesheet.html">
XalanCompiledStylesheet</jump>; the parseSource() method
returns a
- pointer to a <jump href="apiDocs/class_xalanparsedsource.html">
+ pointer to a <jump href="apidocs/classXalanParsedSource.html">
XalanParsedSource</jump>.
</p>
<note>
@@ -371,7 +371,7 @@
<anchor name="dom"/>
<s2 title="Working with DOM input and output">
<p>
- You can set up an <jump href="apiDocs/class_xsltresulttarget.html">
+ You can set up an <jump href="apidocs/classXSLTResultTarget.html">
XSLTResultTarget</jump> to produce a DOM when you perform a
transformation. You can also use a DOM as input for a transformation.
</p>
@@ -444,7 +444,7 @@
<anchor name="xercesdomwrapperparsedsource"/>
<s3 title="Passing in a Xerces DOM to a transformation">
<p>
- You may want to use a Xerces DOM that was created without using
the XalanTransformer class. As the following code snippet illustrates, you can
use <jump
href="apiDocs/class_xercesdomwrapperparsedsource.html">XercesDOMWrapperParsedSource</jump>
to pass in a Xerces DOM as the source for an XSL transformation.
+ You may want to use a Xerces DOM that was created without using
the XalanTransformer class. As the following code snippet illustrates, you can
use <jump
href="apidocs/classXercesDOMWrapperParsedSource.html">XercesDOMWrapperParsedSource</jump>
to pass in a Xerces DOM as the source for an XSL transformation.
</p>
<source>
#include <xercesc/parsers/DOMParser.hpp>
@@ -618,7 +618,7 @@
<anchor name="capi"/>
<s2 title="Basic XalanTransformer usage pattern with the C API">
<p>
- We also include a simple C interface for using the XalanTransformer
class. See <jump
href="apiDocs/XalanCAPI_8h.html">XalanTransformer/XalanCAPI.h</jump>.
+ We also include a simple C interface for using the XalanTransformer
class. See <jump
href="apidocs/XalanCAPI_8h.html">XalanTransformer/XalanCAPI.h</jump>.
The <link idref="samples" anchor="apachemodulexslt">ApacheModuleXSLT</link>
sample illustrates the use of this C API.
</p>
<p>Basic strategy:</p>
@@ -658,7 +658,7 @@
<anchor name="cvar"/>
<s2 title="Variations with the XalanTransformer C API">
<p>
- The <jump href="apiDocs/XalanCAPI_8h.html">Xalan C API</jump>
supports approximately the same set of options as the C++ API. In particular,
you can
+ The <jump href="apidocs/XalanCAPI_8h.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 indicate the URI
of the stylesheet. Supply NULL for the stylesheet argument.<br/><br/></li>
1.1 xml-xalan/c/xdocs/sources/xalan/NET_options.jpg
<<Binary file>>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
