Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

This commit was manufactured by cvs2svn to create tag

'Xalan-C_1_0_0'.

git-svn-id: https://svn.apache.org/repos/asf/xalan/c/tags/Xalan-C_1_0_0@339024 13f79535-47bb-0310-9956-ffa450edef68
  • Loading branch information...
commit cb9df2b0fd752c3c610412768269e5203c7b603a 1 parent 85335f5
No Author authored
5 src/Makefile.in
View
@@ -55,6 +55,9 @@
#
#
# $Log$
+# Revision 1.19 2000/10/10 16:34:56 auriemma
+# Update version number.
+#
# Revision 1.18 2000/10/03 14:58:14 auriemma
# Added Xerces include to the include path.
#
@@ -285,7 +288,7 @@ SAMPLES_DIR = ${XALANCROOT}/samples
PROJECT_NAME = xalan-c
LIBNAME = lib${PROJECT_NAME}
THISLIB = ${LIB_DIR}/${LIBNAME}
-VER = 0_40
+VER = 1_0
PRODUCTNAME=xalan
PRODUCTVERSION=${VER}
22 xdocs/sources/xalan/BUGS
View
@@ -1,6 +1,18 @@
-<s3 title="Bug reporting">
- <p>Outstanding bugs are recorded in the Apache XML <jump href="http://xml.apache.org/bugs/">Bug Tracking System</jump>.
- If you find a bug, please use this system to report it.</p>
- <note>If the Apache XML Bug Tracking System is not working, please report the bug to the
- <human-resource-ref idref="xalandev"/>, and please be sure to note in the subject line that the bug applies to &xslt4c;.</note>
+<s3 title="Bugs">
+<p>Open bugs:</p>
+<ul>
+<li>Problems mapping namespaces from the stylesheet to the source document, and elements do not inherit namespaces correctly<br/><br/></li>
+<li>&lt;xsl:copy-of ...&gt; within an attribute element does not include CRLFs (if any) in the result.<br/><br/></li>
+<li>If you use &lt;xsl:output method="HTML"&gt; to generate HTML with a &lt;HEAD&gt; element, the &lt;HEAD&gt; element fails to include a &lt;META&gt; tag (with the encoding).<br/><br/></li>
+<li>&lt;xsl:number&gt; does not support letter-value="traditional" for "classical" Greek numbering.<br/><br/></li>
+<li>Unable to sort in reverse document order based on position. <br/><br/></li>
+<li>Does not support six or more digits of numerical precision after the decimal.<br/><br/></li>
+<li>&lt;xsl:fallback&gt; within a top-level function is not recognized and does not throw an error.<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>Problems using key() in match patterns to find descendants. For example, key('mykey','Introduction')//p finds all p elements, not just those that match the criteria.<br/><br/></li>
+<li>The id() function doesn't work in some complex match patterns.<br/><br/></li>
+<li>In some cases, output a single CDATA section in multiple single-character CDATA sections.<br/><br/></li>
+<li>Minor problems outputting whitespace characters.</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>
4 xdocs/sources/xalan/DONE
View
@@ -1,9 +1,9 @@
-<s3 title="Changes since &xslt4c; version 0.30.0">
+<s3 title="Changes since &xslt4c; version 0.40.0">
<p>Major updates since version 0.40.0 include:</p>
<ul>
<li>Full support for namespace handling<br/><br/></li>
<li>Full implementation of the format-number() function and support for the decimal-format element<br/><br/></li>
-<li>Integration with the <resource-ref idref="icu"/>for number formatting, sorting, and output encoding<br/><br/></li>
+<li>Integration with the <resource-ref idref="icu"/> for number formatting, sorting, and output encoding<br/><br/></li>
<li>Support for the exclude-result-prefixes attribute<br/><br/></li>
<li>Support for the output encoding attribute</li>
</ul>
5 xdocs/sources/xalan/STATUS
View
@@ -7,9 +7,10 @@ For information about including The Xerces-C++ dynamic link or shared object lib
<s3 title="To-do tasks for future &xslt4c; releases">
<ul>
<li>Add support for extension elements<br/><br/></li>
- <li>Fix any conformance bugs we or our users find<br/><br/></li>
+ <li>Fix any conformance bugs we or our users find<br/><br/></li>
+ <li>Investigate introducing an API along the lines of the Java TRaX (Transformations for XML) interfaces<br/><br/></li>
<li>Implement a more efficient mechanism for storing and navigating DOM trees, along the lines of the &xslt4j; Document
- Table Model (DTM)<br/><br/></li>
+ Table Model (DTM)</li>
</ul>
<p>Watch the <human-resource-ref idref="xalandev"/> for more information and for ideas about how you can get involved.</p>
</s3>
2  xdocs/sources/xalan/overview.xml
View
@@ -144,7 +144,7 @@
Designers</jump></li>
</ul>
<p>When you come across other useful introductory or background materials, please email <human-resource-ref
- idref="dleslie"/>, so he can add them to this list.</p>
+ idref="xalandev"/>, so we can add them to this list.</p>
</s2><anchor name="glossary"/>
<s2 title="Glossary">
8 xdocs/sources/xalan/readme.xml
View
@@ -70,7 +70,7 @@
<anchor name="status"/>
<s2 title="Status">
<ul>
- <li><link anchor="done">Changes since &xslt4c; version 0.30.0</link></li>
+ <li><link anchor="done">Changes since &xslt4c; version 0.40.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>
@@ -152,7 +152,11 @@
(This step is not required for Linux because The Linux GNU compiler includes the STL (Standard Template
Library.)<br/><br/></li>
<li>(Optional) If you are including the ICUBridge, install the ICU (see <link idref="usagepatterns"
- anchor="icu">Using the ICU</link>) and define XALAN_USE_ICU.<br/><br/></li>
+ anchor="icu">Using the ICU</link>) and use the shell to define XALAN_USE_ICU.<br/><br/>
+ If you are using Bourne Shell, K Shell, or Bash:
+ <br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<code>export XALAN_USE_ICU "1"</code><br/><br/>
+ If you are using C Shell:
+ <br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<code>setenv XALAN_USE_ICU="1"</code><br/><br/></li>
<li>Change directory to xml-xalan/c/src in the &xslt4c; distribution.<br/><br/></li>
<li>Use the chmod +x command to set the executable flags for conf* and
runConfigure.<br/><br/>
11 xdocs/sources/xalan/resources.xml
View
@@ -39,18 +39,7 @@
<resource id="XPath" title="XML Path Language (XPath) Version 1.0" location="http://www.w3.org/TR/xpath"/>
<resource id="DOM" title="DOM" location="http://www.w3.org/DOM"/>
-
-
<human-resource id="xalandev" name="Xalan Development Mailing List" mailto="xalan-dev@xml.apache.org"/>
- <human-resource id="sboag" name="Scott Boag" mailto="scott_boag@lotus.com"/>
- <human-resource id="dnbertoni" name="David N. Bertoni" mailto="david_n_bertoni@lotus.com"/>
- <human-resource id="mmidy" name="Myriam Midy" mailto="myriam_midy@lotus.com"/>
- <human-resource id="scurcuru" name="Shane Curcuru" mailto="shane_curcuru@lotus.com"/>
- <human-resource id="dleslie" name="Don Leslie" mailto="donald_leslie@lotus.com"/>
- <human-resource id="pdick" name="Paul Dick" mailto="paul_dick@lotus.com"/>
-
- <human-resource id="nmendelsohn" name="Noah Mendelsohn" mailto="noah_mendelsohn@lotus.com"/>
- <human-resource id="sanjiva" name="Sanjiva Weerawarana" mailto="sanjiva@watson.ibm.com"/>
</resources>
24 xdocs/sources/xalan/samples.xml
View
@@ -161,14 +161,18 @@ theProcessor.addTraceListener(&amp;theTraceListener);
<p>See also: <link idref="usagepatterns" anchor="compiled">Compiling stylesheets</link>.</p>
</s2><anchor name="xpathwrapper"/>
<s2 title="XPathWrapper">
- <p>This sample uses TestDriver, an executable, and two classes: XPathWrapper and XPathWrapperImp. </p>
- <p>What it does: TestDriver passes XPathWrapper an XML file name, a context node location path, and an XPath
- expression. XPathWrapper in turn passes these arguments to the XPathWrapperImpl evaluate() method, which executes
- the XPath expression from specified context node in the XML document and returns the nodes it finds (if any).</p>
+ <p>This sample uses an executable (TestDriver in Windows, XPathWrapper in Linux and AIX), and two classes: XPathWrapper and
+ XPathWrapperImp.</p>
+ <p>What it does: The executable passes XPathWrapper an XML file name, a context node location path, and an XPath
+ expression. XPathWrapper in turn passes these arguments to the XPathWrapperImpl evaluate() method, which executes the
+ XPath expression from specified context node in the XML document and returns the nodes it finds (if any).</p>
<note>You can use this sample as an aid when you want to find out what a given XPath expression returns from a
given context node in an XML file.</note>
<p>Run this sample from the XPathWrapper subdirectory with</p>
- <p><code>TestDriver <ref>XMLFile ContextNode XPathExpression</ref></code></p>
+ <p>Windows:<br/>
+ &nbsp;&nbsp;<code>TestDriver <ref>XMLFile ContextNode XPathExpression</ref></code></p>
+ <p>Linux or AIX:<br/>
+ &nbsp;&nbsp;<code>XPathWrapper <ref>XMLFile ContextNode XPathExpression</ref></code></p>
<p>where <ref>XMLFile</ref> is an XML source file, <ref>ContextNode</ref> is the location path to the context
node, and <ref>XPathExpression</ref> is an XPath expression to apply to that context node. The XPathWrapper
subdirectory contains an XML file named xml.foo (part of it appears below).</p>
@@ -180,9 +184,15 @@ theProcessor.addTraceListener(&amp;theTraceListener);
&lt;name first="Paul" last="Dick"/&gt;
&lt;/doc&gt;</source>
<p>You can try command lines like</p>
- <p><code>TestDriver foo.xml /doc name/@last</code></p>
+ <p>Windows:<br/>
+ &nbsp;&nbsp;<code>TestDriver foo.xml /doc name/@last</code></p>
+ <p>Linux or AIX:
+ &nbsp;&nbsp;<code>XPathWrapper foo.xml /doc name/@last</code></p>
<p>and</p>
- <p><code>TestDriver foo.xml //name[position()="4"]./@first</code></p>
+ <p>Windows:<br/>
+ &nbsp;&nbsp;<code>TestDriver foo.xml / '//name[position()="4"]/@first'</code></p>
+ <p>Linux or AIX:<br/>
+ &nbsp;&nbsp;<code>XPathWrapper foo.xml / '//name[position()="4"]/@first'</code></p>
<note>If an XPathWrapper argument includes characters (such as *) that the shell intercepts, enclose the argument
in double quotes.</note>
<p>See also: <link idref="usagepatterns" anchor="xpath">Working with XPath expressions</link>.</p>
Please sign in to comment.
Something went wrong with that request. Please try again.