You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by dl...@apache.org on 2001/02/14 21:10:51 UTC
cvs commit: xml-xalan/c/xdocs/sources/xalan BUGS DONE commandline.xml extensions.xml faq.xml index.xml samples.xml usagepatterns.xml
dleslie 01/02/14 12:10:51
Modified: c/xdocs/sources entities.ent
c/xdocs/sources/xalan BUGS DONE commandline.xml
extensions.xml faq.xml index.xml samples.xml
usagepatterns.xml
Log:
Added XalanSourceTree.dll to list of Windows dlls.
Revision Changes Path
1.16 +1 -1 xml-xalan/c/xdocs/sources/entities.ent
Index: entities.ent
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/entities.ent,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- entities.ent 2001/02/14 17:31:04 1.15
+++ entities.ent 2001/02/14 20:10:50 1.16
@@ -3,7 +3,7 @@
<!ENTITY xslt4c "Xalan-C++">
<!ENTITY xslt4c-dist "Xalan-C_1_1">
<!ENTITY xslt4c-current "Xalan-C++ version 1.1">
-<!ENTITY xslt4c-windlls "DOMSupport.dll, PlatformSupport.dll, XalanDOM.dll, XercesParserLiaison.dll, XMLSupport.dll, XPath.dll, XSLT.dll, XalanTransformer.dll">
+<!ENTITY xslt4c-windlls "DOMSupport.dll, PlatformSupport.dll, XalanDOM.dll, XalanSourceTree,dll, XercesParserLiaison.dll, XMLSupport.dll, XPath.dll, XSLT.dll, XalanTransformer.dll">
<!ENTITY xslt4c-linuxlib "libxalan-c1_1.so">
<!ENTITY xslt4c-aixlib "libxalan-c1_1.a">
<!ENTITY xslt4c-hplib "libxalan-c1_1.sl">
1.7 +2 -2 xml-xalan/c/xdocs/sources/xalan/BUGS
Index: BUGS
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/BUGS,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- BUGS 2001/02/14 17:25:00 1.6
+++ BUGS 2001/02/14 20:10:50 1.7
@@ -1,9 +1,9 @@
<s3 title="Bugs">
<p>Open bugs:</p>
<ul>
-<li>Does not support six or more digits of numerical precision after the decimal.<br/><br/></li>
-<li>The document() function generates a syntax error if called in the following manner: document(<ref>string</ref>,/).<br/><br/></li>
+<li>Does not support 20 or more digits of numerical precision after the decimal.<br/><br/></li>
<li>The namespace axis does not return the default "xml" namespace.</li>
+<li>Does not support case-order and lang attributes in xsl:sort.</li>
</ul>
<note>Please report any bugs you find to the <human-resource-ref idref="xalandev"/>, and please note in the subject line that the bug applies to &xslt4c;.</note>
</s3>
1.13 +4 -1 xml-xalan/c/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/DONE,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- DONE 2001/02/14 17:25:00 1.12
+++ DONE 2001/02/14 20:10:50 1.13
@@ -13,6 +13,7 @@
<li>Added sample illustrating use of XalanTransformer, the new C API, and how to run &xslt4c; and perform transformations on an
Apache Web server: <link idref="samples" anchor="apachemodulexslt">ApacheModuleXSLT</link>.<br/><br/></li>
<li>Added the <link idref="samples" anchor="streamtransform">StreamTransform</link> sample.<br/><br/></li>
+<li>Eliminated dependencies on non-public Xerces headers; accordingly can now build with the Xerces distribution.<br/><br/></li>
<li>Fixed namespace mapping and inheritance problems.<br/><br/></li>
<li>Fixed failure of <copy-of ...> to include CRLFs (if any) in the result.<br/><br/></li>
<li>Fixed bug sorting in reverse document order based on position. <br/><br/></li>
@@ -24,7 +25,9 @@
<li>Fixed problem outputting multiple single-character CDATA sections.<br/><br/></li>
<li>Fixed problem outputting whitespace characters.<br/><br/></li>
<li>Fixed problem transforming from a stream on UNIX platforms.<br/><br/></li>
-<li>Fixed named templates bug accepting global parameter when called with a parameter that the named template does not recognize.</li>
+<li>Fixed a bug with the document() function, which was generating a syntax error if called in the following manner: document(<ref>string</ref>,/).<br/><br/></li>
+<li>Fixed named templates bug accepting global parameter when called with a parameter of the same name that the named template does not
+ recognize.</li>
</ul>
</s3>
1.18 +4 -2 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.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- commandline.xml 2001/02/12 21:43:49 1.17
+++ commandline.xml 2001/02/14 20:10:50 1.18
@@ -97,13 +97,15 @@
-TS (Trace each selection event)
-TTC (Trace the template children as they are being processed)
-XML (Use XML formatter and add XML header)
--TEXT (Use simple Text formatter)
--HTML (Use HTML formatter)
The -XML flag must be set:
-NH (Don't write XML header)
+-HTML (Use HTML formatter)
+The -HTML flag must be set:
+ -NOINDENT (turns off HTML indenting)
The -XML or -HTML flag must be set:
-STRIPCDATA (Strip CDATA sections of their brackets, but do not escape)
-ESCAPECDATA (Strip CDATA sections of their brackets, and escape)
+-TEXT (Use simple Text formatter)
-DOM (Test for well-formed output --format to DOM then to XML for output)
-PARAM name expression (Set a stylesheet parameter)</source>
<p>Use -IN to specify the XML source document.</p>
1.12 +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.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- extensions.xml 2001/02/08 15:54:50 1.11
+++ extensions.xml 2001/02/14 20:10:50 1.12
@@ -72,7 +72,7 @@
<p>You can send arguments to an extension function in the form of XPath expressions, literals (for string, boolean, and number), the values returned by other functions, and XSL variables or parameters set to any of the preceding.</p>
<p>For an example that implements, installs, and uses three extension functions, see the
<link idref="samples" anchor="externalfunctions">External Functions</link> sample.</p>
-<note>&xslt4c; does not yet support extension elements. Support for extension elements will be added soon.</note>
+<note>&xslt4c; does not support extension elements.</note>
</s2><anchor name="implement"/>
<s2 title="Implementing an extension function">
<p>Like the standard XPath functions, the functions you create derive from the Function base class. Set up your
1.11 +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.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- faq.xml 2001/02/12 22:04:03 1.10
+++ faq.xml 2001/02/14 20:10:50 1.11
@@ -78,7 +78,7 @@
</tr>
<tr>
<td>Red Hat Linux 6.1</td>
- <td>glib-2.1.2-11</td>
+ <td>egcs-2.91.66 and glibc-2.1.2-11</td>
<td>No</td>
</tr>
</table>
@@ -88,7 +88,7 @@
<faq title="STLPort">
<q>What is STLPort and why do I need it?</q>
-<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-upsinstalled. If your compiler does not support the STL or its implementation is out of date, you will need to install the STLPort.</p>
+<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>
1.20 +12 -5 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.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- index.xml 2001/02/12 22:04:03 1.19
+++ index.xml 2001/02/14 20:10:50 1.20
@@ -66,7 +66,7 @@
<p>&xslt4c-current; is a robust implementation of the W3C Recommendations
for XSL Transformations (XSLT) and the XML Path Language (XPath). It includes a compatible release of the
&xml4c; XML parser: &xml4c-used;. In addition to adding builds for HP-UX 11 and Solaris, the focus for this release
- is on bug fixes, performance enhancements, and providing a simpler C++ and C API for performing standard transformations.
+ is on bug fixes, performance enhancements, providing a simpler C++ and C API for performing standard transformations, and new samples.
For the details, see the <link idref="readme">Release Notes</link>.</p>
</s2>
@@ -78,33 +78,40 @@
<tr>
<th>Platform</th>
<th>Download</th>
+ <th>Built with</th>
</tr>
<tr>
<td>Windows32</td>
<td><resource-ref idref="xslt4c-win32-download"/></td>
+ <td>MSVC 6.0 SP3</td>
</tr>
<tr>
- <td>Linux</td>
+ <td>Red Hat Linux 6.1</td>
<td><resource-ref idref="xslt4c-linux-download"/></td>
+ <td>egcs-2.91.66 and glibc-2.1.2-11</td>
</tr>
<tr>
- <td>AIX</td>
+ <td>AIX 4.3</td>
<td><resource-ref idref="xslt4c-aix-download"/></td>
+ <td>IBM C and C++ for AIX 3.6.6</td>
</tr>
<tr>
<td>HP-UX 11</td>
<td><resource-ref idref="xslt4c-hp-ux-download"/></td>
+ <td>aCC A.03.27</td>
</tr>
<tr>
- <td>Solaris</td>
+ <td>Solaris 2.6</td>
<td><resource-ref idref="xslt4c-solaris-download"/></td>
+ <td>Workshop 4.2</td>
</tr>
</table>
<p>Volunteers are more than welcome to help develop builds for other platforms!</p>
</s2>
<s2 title="Where do I get Xerces?">
- <p>Right here! The distributions include everything you need to build and run applications that use Xalan and Xerces. Each distribution file includes the Xerces source tree along with the appropriate Xerces runtime environment for Xalan: &xml4c-windll; for
+ <p>Right here! The distributions include everything you need to build and run applications that use Xalan and Xerces. Each distribution
+ file includes the Xerces distribution with the appropriate Xerces runtime environment for Xalan: &xml4c-windll; for
Windows, &xml4c-linuxlib; for Linux, &xml4c-aixlib; for AIX, &xml4c-hplib; for HP-UX 11, and &xml4c-solarislib; for Solaris.</p>
</s2>
<s2 title="How about support for internationalization?">
1.24 +5 -5 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.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- samples.xml 2001/02/13 19:04:17 1.23
+++ samples.xml 2001/02/14 20:10:51 1.24
@@ -88,7 +88,7 @@
</ol>
<note> Each sample application looks for input files in the current directory, the directory from
which you run the application. The input files are in the samples subdirectory along with the sample source
- files. For the UNIX builds, the application executable is also in the samples subdirectory. For the Windows32 build, however, the
+ files. For the UNIX builds, application executables are in the bin subdirectory. For the Windows32 build, the
application executable is in the build subdirectory (xml-xalan\c\Build\Win32\VC6\ Debug and Release). To run a sample, be sure the
executable is on the path, and run it from the samples subdirectory that contains the input files.</note>
</s2><anchor name="xalantransform"/>
@@ -99,7 +99,7 @@
the third argument, XalanTransform writes the transformation output to a stream that is sent to standard out (the screen).</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 a stream. See also: <link idref="usagepatterns"
+ <p>Omit the third argument to write the transformation result to the screen. See also: <link idref="usagepatterns"
anchor="xalantransformer">Using the XalanTransformer class.</link>.</p>
</s2><anchor name="simpletransform"/>
<s2 title="SimpleTransform">
@@ -111,8 +111,8 @@
transformations</link>.</p>
</s2><anchor name="streamtransform"/>
<s2 title="StreamTransform">
- <p>What it does: The StreamTransform class processes character array input streams containing a stylesheet and an XML document, and
- writes the transformation output to a character array output stream. This sample illustrates the process for working with stylesheets and documents that you assemble in memory.</p>
+ <p>What it does: The StreamTransform class processes character input streams containing a stylesheet and an XML document, and
+ writes the transformation output to a character output stream. This sample illustrates the process for working with stylesheets and documents that you assemble in memory.</p>
<p>You can run it from the SimpleTransform subdirectory with</p>
<p><code>StreamTransform</code></p>
</s2><anchor name="usestylesheetparam"/>
@@ -231,7 +231,7 @@
<p>What it does: runs as an Apache module on an Apache Web server; performs transformations and returns the output to a Web
browser. You configure Apache to respond to a given URL request for an output file (html or txt file in the configuration below)
by applying an xsl stylesheet file to an xml document file (both with the specified name in a given location) and returning
- the transformation outupt to the client.</p>
+ the transformation output to the client.</p>
<p>This sample also illustrates use of the XalanTransformer class and the C API defined in src/XalanTransformer/XalanCAPI.h. It returns
transformation output in blocks to a callback function, which enables the browser to start displaying the result before the transformation
has been completed.</p>
1.20 +14 -21 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.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- usagepatterns.xml 2001/02/13 18:48:28 1.19
+++ usagepatterns.xml 2001/02/14 20:10:51 1.20
@@ -103,7 +103,7 @@
<code>const char* xmlOut = "foo.out";</code><br/>
<code>int theResult = 0;</code><br/>
<code>theResult = theXalanTransformer(xmlIn,xslSheet,xmlOut);</code><br/><br/></li>
- <li>Shut down Xalan and Xerces.<br/>
+ <li>Shut down Xalan.<br/>
<code>XalanTransformer::terminate();</code></li>
</ol>
</s3><anchor name="cppvar"/>
@@ -134,8 +134,9 @@
<p>Transform from files to an output handler that receives the output in blocks. </p>
<source>int
-transform(const char* xmlInFile
+transform(const char* xmlInFile,
const char* xslFile,
+ const void* theOutputHandle,
XalanOutputHandlerType theOutputHandler
XalanFlushHanderType theFlushHandler = 0);</source>
<p>The transform() method that the other transform() methods all call:</p>
@@ -152,9 +153,9 @@
<ol>
<li>Include the XalanTransformer C API header.<br/>
<code>#include <XalanTransformer/XalanCAPI.h></code><br/><br/></li>
- <li>Initialize Xalan and Xerces<br/>
+ <li>Initialize Xalan and Xerces.<br/>
<code>XalanInitialize();</code><br/><br/></li>
- <li>Create a Xalan transformer<br/>
+ <li>Create a Xalan transformer.<br/>
<code>XalanHandle xalan = NULL;</code><br/>
<code>xalan = CreateXalanTransformer();</code><br/><br/></li>
<li>Perform each transformation. For example:<br/>
@@ -166,7 +167,7 @@
<code> xslfilename,</code><br/>
<code> outfilename,</code><br/>
<code> xalan);</code><br/><br/></li>
- <li>Shut down Xalan and Xerces<br/>
+ <li>Shut down Xalan.<br/>
<code>XalanTerminate();</code></li>
</ol>
<p>If the XML input file contains a stylesheet processing instruction that you want to use, include an empty string ("") for the xslfilename argument.</p>
@@ -199,7 +200,8 @@
<p>Always start with Include/PlatformDefinitions.hpp, the &xslt4c; base header file. Along with any additional &xslt4c; and other header files that are required for the particular application, be sure to include utils/PlatformUtils.hpp from the &xml4c; distribution.</p>
</s3>
<s3 title="2. Initialize Xalan and Xerces">
-<p>Use the static initializers to initialize the &xslt4c; and &xml4c; platforms. You only need to do this once per session.</p>
+<p>Use the static initializers to initialize the &xslt4c; and &xml4c; platforms. You must initialize &xml4c; once per process. You may
+initialize and terminate &xslt4c; multiple times, but this is not recommended: it is inefficient and is not thread safe.</p>
<source>XMLPlatformUtils::Initialize();
XSLTInit theInit;</source>
</s3><anchor name="step3"/>
@@ -267,11 +269,11 @@
theConstructionContext,
theExecutionContext);</source>
<p>The XSLTResultTarget object receives the transformation output.</p>
-<p>XSLTEngineImpl stores running state information, so it is not thread-safe. To perform multiple transformations, create a new instance for each transformation, or call the XSLTProcessor reset() method between each transformation.</p>
+<p>The support objects store running state information, so they are not thread safe. To perform multiple transformations, create a new instance for each transformation, or call the StylesheetExecutionContext reset() method between each transformation.</p>
<p>If you are using the same stylesheet to perform multiple transformations, for efficiency you should compile the stylesheet and use the appropriate XSLTEngineImpl process() method. Compiled stylesheet (StylesheetRoot) objects are also thread-safe. A single StylesheetRoot object may be called concurrently from multiple threads. For more information, see <link anchor="compiled">Compiling stylesheets</link>.</p>
</s3>
<s3 title="7. Shut down Xerces.">
-<p>When you are done performing transformations, shut down Xerces.</p>
+<p>When you are done performing transformations, shut down Xerces. Once you have shut down Xerces, you can no longer make Xalan or Xerces call in that process.</p>
<source>// Call the static terminator for Xerces.
XMLPlatformUtils::Terminate();
</source>
@@ -279,7 +281,7 @@
</s3>
</s2><anchor name="dom"/>
<s2 title="Working with DOM input and output">
-<p>You can set up an XSLTResultTarget to produce a DOM when you perform a transformation. You can also use a DOM as input for a transformation, either the DOM output of another transformation, or a DOM produced by the Xerces DOMParser.</p>
+<p>You can set up an XSLTResultTarget to produce a DOM when you perform a transformation. You can also use a DOM as input for a transformation.</p>
<p>The following code fragments illustrate the procedures for working with DOM input and output:</p>
<source>
@@ -422,17 +424,13 @@
<br/> &xml4c; and &xslt4c; use UTF-16 encoding to work with Unicode data.
If you integrate the ICU with &xml4c;, both &xml4c; and &xslt4c; use ICU support for
UTF-16 encoding.<br/><br/></li>
- <li><em>xsl:number element</em>
- <br/>Both &xslt4c; and the ICU provide a complete implementation for
- xsl:number.<br/><br/></li>
<li><em>format-number()</em>
<br/>This XSLT function includes two or three arguments (the third is
optional): number, format pattern, and decimal-format name. &xslt4c; ignores the format
pattern and optional decimal-format name. If you install ICU support for format-number(),
this function is fully supported with all its arguments.<br/><br/></li>
<li><em>xsl:sort</em>
- <br/>If you install ICU support for xml:sort, &xslt4c; applies the Unicode sorting
- algorithm.</li>
+ <br/>If you install ICU support for xml:sort, &xslt4c; implements Unicode-style collation.</li>
</ul>
<p>To get the ICU:</p>
@@ -480,15 +478,10 @@
path (LD_LIBRARY_PATH) or copy it to /usr/lib.</p>
<p><em>Number formatting</em></p>
- <p>To enable ICU support for the xsl:number element and the XSLT format-number() function, do
+ <p>To enable ICU support for the XSLT format-number() function, do
the following:</p>
<source>// Install ICU support for the format-number() function.
-FunctionICUFormatNumber::FunctionICUFormatNumberInstaller theInstaller;
-
-// Create and install a factory for using the ICU for xsl:number.
-ICUXalanNumberFormatFactory theXalanNumberFormatFactory;
-StylesheetExecutionContextDefault::installXalanNumberFormatFactory
- (&theXalanNumberFormatFactory);</source>
+FunctionICUFormatNumber::FunctionICUFormatNumberInstaller theInstaller;</source>
<p><em>Sorting</em></p>
<p>To enable ICU support for xsl:sort, do the following:</p>
<source>// Set up a StylesheetExecutionContextDefault object