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...@locus.apache.org on 2000/06/29 22:13:26 UTC
cvs commit: xml-xalan/c/xdocs/sources/xalan commandline.xml DONE extensions.xml faq.xml getstarted.xml readme.xml STATUS
dleslie 00/06/29 13:13:24
Modified: c/xdocs/sources/xalan commandline.xml DONE extensions.xml
faq.xml getstarted.xml readme.xml STATUS
Log:
Updates for 0.40.0
Revision Changes Path
1.5 +1 -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.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- commandline.xml 2000/06/27 16:46:16 1.4
+++ commandline.xml 2000/06/29 20:13:18 1.5
@@ -81,13 +81,11 @@
<source>-IN inputXMLURL
-XSL XSLTransformationURL
-OUT outputFileName
--E (Do not expand entity refs)
-ESCAPE chars(Which characters to escape -- default is <>&"'\r\n)
-V (Version info)
-QC (Quiet Pattern Conflicts Warnings)
-Q (Quiet Mode)
-INDENT (Number of spaces to indent each level in output tree --default is 0)
--VALIDATE (Validate the XML and XSL input -- validation is off by default)
-TT (Trace the templates as they are being called)
-TG (Trace each result tree generation event)
-TS (Trace each selection event)
@@ -95,6 +93,7 @@
-XML (Use XML formatter and add XML header)
-TEXT (Use simple Text formatter)
-HTML (Use HTML formatter)
+-NH (Don't write XML header. Only works with -HTML flag set.)
-PARAM name expression (Set a stylesheet parameter)</source>
<p>Use -IN to specify the XML source document.</p>
<p>Use -XSL to specify the XSL stylesheet file.</p>
1.2 +15 -4 xml-xalan/c/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/DONE,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- DONE 2000/04/26 13:05:55 1.1
+++ DONE 2000/06/29 20:13:18 1.2
@@ -1,4 +1,15 @@
-<s3 title="Things completed since the last version">
-<p><ref>does not apply</ref></p>
-</s3>
-
+<s3 title="Changes since &xslt4c; version 0.30.0">
+<p>We continue to work towards the functional completion our implementation of the XSLT and XPath specs. Major updates since version 0.30.0 include:</p>
+<ul>
+<li>Permitting OS file names (as well as URLs) as command-line arguments with TestXSLT<br/><br/></li>
+<li>Stricter compliance for HTML and XML output<br/><br/></li>
+<li>Improved handling of relative URI's<br/><br/></li>
+<li>Improved handling of Import and Include<br/><br/></li>
+<li>Better namespace handling (although there are still problems here)<br/><br/></li>
+<li>Support for Document() function<br/><br/></li>
+<li>Support for XPath predicates<br/><br/></li>
+<li>Better handling of parameters to stylesheet and templates<br/><br/></li>
+<li>Full implementation of axes ( with the exception of namespace:: )<br/><br/></li>
+</ul>
+</s3>
+
1.4 +2 -2 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.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- extensions.xml 2000/06/27 16:46:17 1.3
+++ extensions.xml 2000/06/29 20:13:18 1.4
@@ -188,7 +188,7 @@
The <ref>prefix</ref> identifies the namespace, and <ref>URI</ref> matches the namespace specified when the function
is installed.<br/><br/>
By default, namespace declarations are included in the transformation output. To exclude namespaces from the output,
-use<br/><br/>
+use (<em>NOT YET IMPLEMENTED</em>)<br/><br/>
<code>exclude-result-prefixes="<ref>prefix-1 prefix-2 ...</ref>"</code><br/><br/>
in the stylesheet element or<br/><br/>
<code>xsl:exclude-result-prefixes="<ref>prefix-1 prefix-2 ...</ref>"</code><br/><br/>
@@ -227,7 +227,7 @@
<p>Please keep in mind that <em>all</em> LocationPath expressions return a node-set, even if the expression only
returns a single attribute or a text node (node-sets with one member). You can use the XSLT string() function
to convert a node-set value to string, and the number() function to convert a node-set value to number (a double).</p>
-<p>If you want to pass a node-set to an extension function, set up the function to accept a <jump href="apidocs/class_nodereflistbase.html">NodeRefListBase</jump>.</p>
+<p>If you want to pass a node-set to an extension function, set up the function to accept a <jump href="apidocs/class_xnodeset.html">XNodeSet</jump>.</p>
<p>Suppose, for example, you have a ProcessNodes function class that uses<br/><br/>
<code>const NodeRefListBase& theNodeList = args[0]->nodeset();</code><br/><br/>
in the execute() method to get a reference to the node-set.</p>
1.5 +3 -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.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- faq.xml 2000/06/27 16:46:17 1.4
+++ faq.xml 2000/06/29 20:13:19 1.5
@@ -32,8 +32,9 @@
method after each transformation. You may want to serialize access to this object, so it can't accidently start another
transformation while a transformation is in progress.</p>
<p>StylesheetRoot objects, on the other hand, are thread-safe. A single StylesheetRoot object may be called concurrently
- from multiple threads. Keep in mind, however, that the StylesheetRoot uses an XSLTEgineImpl to store running state information
- for each transformation, so you must call the XSLTEngineImpl reset() method between each transformation.</p>
+ from multiple threads. Keep in mind, however, that the StylesheetRoot uses an XSLTEgineImpl to store running state
+ information for each transformation, so you must call the XSLTEngineImpl reset() method and the StylesheetExecutionDefault
+ reset() method between each transformation.</p>
<p>For more detail, see <link idref="samples" anchor="compilestylesheet">CompileStylesheet</link>.</p></a>
</faq>
1.8 +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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- getstarted.xml 2000/06/28 20:10:39 1.7
+++ getstarted.xml 2000/06/29 20:13:19 1.8
@@ -17,7 +17,7 @@
</s3>
<p>For the Windows32 build, download <resource-ref idref="xslt4c-win32-download"/>.</p>
<p>For the Linux build, download <resource-ref idref="xslt4c-linux-download"/></p>
-<p>Each distribution contains all you need to run the Xalan command-line utility for performing transformations. To build your own applications, you also need a compatible Xerces-C++ distribution and the <resource-ref idref="icu"/>.</p>
+<p>Each distribution contains all you need to run the Xalan command-line utility for performing transformations. To build your own applications, you also need a compatible Xerces-C++ distribution and (<em>NOT FOR THIS RELEASE</em>)the <resource-ref idref="icu"/>.</p>
<s3 title="What you need to run the Xalan command-line utility">
<p>To run the Xalan executable for performing transformations, you need the following:</p>
<p><em>Windows32</em></p>
@@ -37,7 +37,7 @@
<li>(<em>NOT FOR THIS RELEASE</em>) The International Components for Unicode (ICU) shared library: &icu-unixlib;</li>
<li>(<em>NOT FOR THIS RELEASE</em>) The ICU locale data files</li>
</ul>
-<p>(<em>NOT FOR THIS RELEASE</em>) <em>Important</em> ICU requires you to set the ICU_DATA environment variable to point to the directory containing the ICU locale data files. In the Windows32 distribution, this is xml-xalan\c\Build\Win32\VC6\Release\Data. In the Linux distribution, it is xml-xalan/c/lib/data.</p>
+<p>(<em>NOT FOR THIS RELEASE</em> and we will place the locale data files where they can be found) ICU requires you to set the ICU_DATA environment variable to point to the directory containing the ICU locale data files. In the Windows32 distribution, this is xml-xalan\c\Build\Win32\VC6\Release\Data. In the Linux distribution, it is xml-xalan/c/lib/data.</p>
<p>For information about using the command-line utility, see <link idref="commandline">Command-Line Utility</link>.</p>
</s3>
<s3 title="What you need to build applications">
@@ -52,7 +52,7 @@
</s2><anchor name="path"/>
<s2 title="Setting up the path">
<p>For the Xalan-C++ Windows32 distribution, place xml-xalan\c\Build\Win32\VC6\Release on the path.</p>
-<p>For the Xalan-C++ Linux distribution, place xml-xalan/c/bin and xml-xalan/c/lib on the shared library path (LD_LIBRARY_PATH for Red Hat Linux 6.1).</p>
+<p>For the Xalan-C++ Linux distribution, place xml-xalan/c/bin and xml-xalan/c/lib on the shared library path (LD_LIBRARY_PATH for Red Hat Linux 6.1), or copy &xslt4c-linuxlib; to /usr/lib..</p>
<p>If you do your own Xalan, ICU, and Xerces builds, be sure to include the directories that contain the libraries and the TextXSLT executable on your path.</p>
</s2><anchor name="samples"/>
<s2 title="Trying out the samples">
@@ -60,7 +60,7 @@
and you can review the source files -- all of which are brief -- to see just how they work. In the Windows32 distribution, we have precompiled these samples for you so they are ready to run. In the Linux distribution, you need to build them first.</p>
<p>To run the samples, do the following:</p>
<ol>
-<li>(Linux only) Compile the sample sources (you may need to make some minor changes in the header files to accommodate Linux) and build an executable for each sample application.</li>
+<li>(Linux only) Set up make files and compile the sample sources (you may need to make some minor changes in the header files to accommodate Linux) and build an executable for each sample application.</li>
<li>Set up your path (see above). In the Windows32 distribution, the sample executables are in
xml-xalan\c\Build\Win32\VC6\Release. For Linux, we suggest you build the executables in xml-xalan/c/bin.</li>
<li>Go to the samples subdirectory containing the sample (use the DOS shell in Windows).</li>
1.8 +12 -8 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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- readme.xml 2000/06/28 20:10:42 1.7
+++ readme.xml 2000/06/29 20:13:19 1.8
@@ -67,22 +67,26 @@
<li><link anchor="build">Build Notes</link></li>
<li><link anchor="contact">Getting in touch</link></li>
</ul>
- <s2 title="Status">
+ <anchor name="status"/>
+ <s2 title="Status">
<ul>
- <li><link anchor="bugs">Bug reporting</link></li>
- <li><link anchor="status">Version of &xml4c; to use</link></li>
+ <li><link anchor="done">Changes since &xslt4c; version 0.30.0</link></li>
+ <li><link anchor="bugs">Bug reporting</link></li>
+ <li><link anchor="xml4j">Version of &xml4c; to use</link></li>
+ <li><link anchor="to-do">To-do tasks for future &xslt4c; releases</link></li>
</ul>
+ <anchor name="done"/>
+ &done-c;
<anchor name="bugs"/>
- &bugs-c;
- <anchor name="status"/>
+ &bugs-c;
+ <anchor name="xml4j"/>
&status-c;
- </s2>
- <anchor name="build"/>
+
+ </s2><anchor name="build"/>
<s2 title="Build Notes">
<ul>
<li><link anchor="jar">Rebuilding &xslt4c;</link></li>
<li><link anchor="samples">Rebuilding sample applications</link></li>
-
</ul>
<anchor name="jar"/>
<s3 title="Rebuilding &xslt4c;">
1.7 +8 -5 xml-xalan/c/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/STATUS,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- STATUS 2000/06/28 20:10:39 1.6
+++ STATUS 2000/06/29 20:13:19 1.7
@@ -3,12 +3,15 @@
<p><em>Important</em> You may experience unpredictable anomalies if your Xalan and Xerces builds are not in synch. If you download an update to Xalan, check the release notes to determine which version of Xerces you should use.</p>
</s3><anchor name="to-do"/>
<s3 title="To-do tasks for future &xslt4c; releases">
- <p>To complete our implementation of the <resource-ref idref="XSLT"/>, we must add support for</p>
+ <p>To complete our implementation of the <resource-ref idref="XSLT"/>, we must do the following:</p>
<ul>
- <li>The fallback element<br/><br/></li>
- <li>The exclude-result-prefixes attribute<br/><br/></li>
- <li>The output encoding attribute<br/><br/></li>
- <li>Extension elements<br/><br/></li>
+ <li>Integrate the International Components for Unicode (ICU) for number formatting and output encoding<br/><br/></li>
+ <li>Complete implementation of the format-number() function and support for the decimal-format element<br/><br/></li>
+ <li>Add support for the exclude-result-prefixes attribute<br/><br/></li>
+ <li>Add support for the output encoding attribute<br/><br/></li>
+ <li>Add support for extension elements<br/><br/></li>
+ <li>Fix namespace bugs<br/><br/></li>
+ <li>Continue to run our suite of conformance tests and fix any conformance bugs we find<br/><br/></li>
</ul>
<p>The XSLT specification makes no such requirement, but we plan to implement a more efficient mechanism for storing and
navigating DOM trees, along the lines of the &xslt4j; Document Table Model (DTM)</p>