june 2004/12/17 06:49:58
Modified: c/xdocs/sources/xalan build_instruct.xml history.xml
install.xml overview.xml programming.xml
resources.xml STATUS usagepatterns.xml whatsnew.xml
Log:
More changes to docs for 1.9 release.
Revision Changes Path
1.3 +4 -0 xml-xalan/c/xdocs/sources/xalan/build_instruct.xml
Index: build_instruct.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/build_instruct.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- build_instruct.xml 6 Nov 2004 06:39:41 -0000 1.2
+++ build_instruct.xml 17 Dec 2004 14:49:57 -0000 1.3
@@ -32,7 +32,9 @@
<li><link anchor="dotNet">Steps for doing a Windows Build with Visual
Studio .NET</link></li>
<li><link anchor="unix">Steps for doing a UNIX build</link></li>
<li><link anchor="locale">Steps for doing a Build with Message
Localization Support</link></li>
+ <!--
<li><link anchor="xercesdepdom">Steps for doing a Build with Xerces
Deprecated DOM Support</link></li>
+ -->
</ul>
</s3>
@@ -277,6 +279,7 @@
</ul>
</s3>
+<!--
<anchor name="xercesdepdom"/>
<s3 title="Steps for doing a Build with Xerces Deprecated DOM Support">
<p>If your application is dependent on the XercesBridge classes to interface
with the deprecated Xerces DOM, then the following
@@ -294,5 +297,6 @@
For example,</p>
<code>./runConfigure -p aix -c xlc_r -x xlC_r -z
-DXALAN_BUILD_DEPRECATED_DOM_BRIDGE</code><br/><br/>
</s3>
+-->
</s1>
1.15 +4 -10 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.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- history.xml 3 Nov 2004 16:54:09 -0000 1.14
+++ history.xml 17 Dec 2004 14:49:57 -0000 1.15
@@ -17,7 +17,6 @@
<s3 title="Changes for &xslt4c; version 1.8">
<p>Major updates since version 1.7 include:</p>
<ul>
- <li><resource-ref idref="bugsfixedforthisrelease"/>.</li>
<li>Upgrade from Xerces-C 2.4 to Xerces-C 2.5. </li>
<li>Provide build support for Cygwin and HP-UX 11.00 on Itanium.
Although binary distributions are not provided for the Cygwin environment and
HP-UX 11.00 on Itanium platform, the build configuration files
provided in the source distribution can be used to build on these platforms.
</li>
@@ -41,7 +40,6 @@
<s3 title="Changes for &xslt4c; version 1.7">
<p>Major updates since version 1.7 include:</p>
<ul>
- <li><resource-ref idref="bugsfixedforthisrelease"/>.</li>
<li>Message Localization Support. This feature enables &xslt4c; to
issue diagnostic messages
in languages other than the default language (English). In order to
utilize this feature,
the user must provide a version of the &xslt4c; message catalog that
has been translated in
@@ -72,7 +70,6 @@
<s3 title="Changes for &xslt4c; version 1.6">
<p>Major updates since version 1.5 include:</p>
<ul>
- <li><resource-ref idref="bugsfixedforthisrelease"/>.</li>
<li>Directory "sane include" reorganization. A new sub-directory
called 'xalanc' has been added to the src directory (for source
distribution packages) and include directory (for binary distribution
packages). New source files which include Xalan headers will need to be
modified to include the 'xalanc' prefix in the header path.
For example: <br/><br/>
<code>#include <XPath/XObject.hpp></code><br/><br/>
@@ -85,13 +82,10 @@
<s3 title="Changes for &xslt4c; version 1.5">
<p>Major updates since version 1.4 include:</p>
<ul>
- <li><resource-ref idref="bugsfixedforthisrelease"/>.</li>
- <li>For Windows, Xalan-C++ is now packaged as a single DLL.
The project files to build separate DLLs are now deprecated and will not be
maintained.</li>
- <li>Support for &xml4c; DOMNode classes.</li>
- <li>New sample <em>TransformToXercesDOM</em> that illustrates
how
- to perform a transform resulting in a &xml4c; DOMDocument</li>
- <li>Usage of the &xml4c; C++ namespace and creation of &xslt4c;
- namespace.</li>
+ <li>For Windows, Xalan-C++ is now packaged as a single DLL. The
project files to build separate DLLs are now deprecated and will not be
maintained.</li>
+ <li>Support for &xml4c; DOMNode classes.</li>
+ <li>New sample <em>TransformToXercesDOM</em> that illustrates how to
perform a transform resulting in a &xml4c; DOMDocument</li>
+ <li>Usage of the &xml4c; C++ namespace and creation of &xslt4c;
namespace.</li>
</ul>
</s3>
<s3 title="Changes for &xslt4c; version 1.4">
1.2 +1 -1 xml-xalan/c/xdocs/sources/xalan/install.xml
Index: install.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/install.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- install.xml 3 Nov 2004 16:54:09 -0000 1.1
+++ install.xml 17 Dec 2004 14:49:57 -0000 1.2
@@ -30,7 +30,7 @@
</ul>
<p>The Visual C++ Xalan project included with the Windows release knows the
relative paths to the Xalan headers and libraries, but it
does not know where you have unzipped the Xerces distribution. If you
plan to use Visual C++ to build Xalan applications or <link
- idref="readme" anchor="jar">rebuild Xalan</link>, you must also provide
Visual C++ with access to the Xerces headers and libraries.</p>
+ idref="build_instruct" anchor="rebuild">rebuild Xalan</link>, you must
also provide Visual C++ with access to the Xerces headers and libraries.</p>
<p>Use the Visual C++ Tools menu to open the Options dialog box, go to the
Directories tab, and do the following:</p>
<ul>
<li>Add the path to &xml4c-dist;-<my_Windows_distribution>\include
to the list of directories of Include files.</li>
1.21 +1 -1 xml-xalan/c/xdocs/sources/xalan/overview.xml
Index: overview.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/overview.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- overview.xml 3 Nov 2004 16:54:09 -0000 1.20
+++ overview.xml 17 Dec 2004 14:49:57 -0000 1.21
@@ -164,7 +164,7 @@
<item>The part of a template that defines the kind(s) of nodes to
which the template applies.<br/><br/></item>
</gloss>
-<p>For more definitions of XSLT terminology, see Dave Pawson's <jump
href="http://www.dpawson.co.uk/xsl/vocab.html";>XSLT
+<p>For more definitions of XSLT terminology, see Dave Pawson's <jump
href="http://www.dpawson.co.uk/xsl/xslvocab.html";>XSLT
Terminology Clarification</jump> and the Glossary in Michael Kay's
<jump
href="http://www.wrox.com/Consumer/Store/Details.asp?ISBN=1861003129";>XSLT
Programmer's Reference</jump>.</p>
</s2>
1.3 +2 -0 xml-xalan/c/xdocs/sources/xalan/programming.xml
Index: programming.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/programming.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- programming.xml 7 Dec 2004 20:05:12 -0000 1.2
+++ programming.xml 17 Dec 2004 14:49:57 -0000 1.3
@@ -78,6 +78,8 @@
// Method for deallocating memory
void deallocate(void *p);
</source>
+<p>For an example of how to use this feature, please see the <link
idref="samples" anchor="simpletransform">
+SimpleTransform</link> sample that has been provided in the binary
distributions.</p>
</s3>
</s2>
1.30 +1 -1 xml-xalan/c/xdocs/sources/xalan/resources.xml
Index: resources.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/resources.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- resources.xml 3 Nov 2004 16:54:09 -0000 1.29
+++ resources.xml 17 Dec 2004 14:49:57 -0000 1.30
@@ -114,6 +114,6 @@
<resource id="bugsfixedforthisrelease"
title="XalanC bugs fixed for this release"
-
location="http://nagoya.apache.org/bugzilla/buglist.cgi?resolution=FIXED&bugidtype=include&bug_id=&changedin=&chfield=resolution&chfieldfrom=07%2F20%2F2003&chfieldto=12%2F31%2F2003&chfieldvalue=FIXED&product=XalanC&short_desc=&short_desc_type=allwordssubstr"/>
+
location="http://nagoya.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10582&statusIds=1"/>
</resources>
1.19 +4 -2 xml-xalan/c/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/STATUS,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- STATUS 3 Nov 2004 16:54:09 -0000 1.18
+++ STATUS 17 Dec 2004 14:49:57 -0000 1.19
@@ -1,12 +1,14 @@
<s3 title="Version of &xml4c; to use">
<p>&xslt4c-current; has been tested with &xml4c-used;.</p>
-<p>For information about including the Xerces-C++ libraries on the path, see
<link idref="getstarted" anchor="path">Setting up the system path</link>.</p>
+<p>For information about including the Xerces-C++ libraries on the path, see
<link idref="install" anchor="path">Setting up the system path</link>.</p>
<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">
<ul>
- <li>Support for XSLT 2.0 and XPath 2.0<br/><br/></li>
+ <li>XML 1.1 and Namespaces in XML 1.1 Support</li>
+ <li>Performance improvements</li>
<li>Add support for extension elements<br/><br/></li>
+ <li>Support for XSLT 2.0 and XPath 2.0<br/><br/></li>
<li>Fix any conformance bugs we or our users find<br/><br/></li>
</ul>
<p>Watch the <human-resource-ref idref="xalandev"/> for more information
and for ideas about how you can get involved.</p>
1.49 +1 -1 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.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- usagepatterns.xml 3 Nov 2004 16:54:09 -0000 1.48
+++ usagepatterns.xml 17 Dec 2004 14:49:57 -0000 1.49
@@ -84,7 +84,7 @@
<p>These macros can be used immediately after the included header files (for
global applicability in a given source file) or within
functions and methods for local applicability.</p>
<note>Whilst you can use the standard C++ namespace syntax directly, the
&xml4c; and &xslt4c; namespaces are linked to the version
- number. For example, the Xalan namespace is currently
<em>xalanc_1_8</em>. The macros will automatically take care of this
+ number. For example, the Xalan namespace is currently
<em>xalanc_1_9</em>. The macros will automatically take care of this
when code is re-compiled against a new version of the libraries.
Using the namespaces directly will require each namespace
related statement be updated by hand.</note>
</s3>
1.6 +23 -7 xml-xalan/c/xdocs/sources/xalan/whatsnew.xml
Index: whatsnew.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/whatsnew.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- whatsnew.xml 16 Dec 2004 20:53:55 -0000 1.5
+++ whatsnew.xml 17 Dec 2004 14:49:58 -0000 1.6
@@ -41,11 +41,12 @@
<ul>
<li>Pluggable Memory Management. This feature allows applications to
maintain precise control over memory allocations. This
will allow users, with knowledge of their application's
characteristics, to provide a more efficient allocation method
- than the general purpose procedures provided by the system.</li>
- <li>Improved performance on stylesheet execution. Because the current
implementation relies on function recursion, certain
- stylesheets/input documents may cause the program stack to overflow
and cause the application to fail. It also may
- inhibit executing stylesheets that are heavily dependent on recursive
functions. This feature will prevent these types
- of failure. </li>
+ than the general purpose procedures provided by the system. for more
information on how to use this feature, please see
+ the <link idref="programming" anchor="memory">Pluggable Memory
Management</link> section of the Programming page.</li>
+ <li>Improved stability on the execution of large stylesheets and XML
documents. Because the current implementation relies on
+ function recursion, certain stylesheets/input documents may cause the
program stack to overflow and cause the application
+ to fail. It also may inhibit executing stylesheets that are heavily
dependent on recursive functions. This feature will
+ prevent these types of failure. </li>
<li>Provided a global option to pool all text node strings. This feature
allows developers to set a flag to determine if a
parsed source tree will pool the values of all of the text nodes in
the XML document. By doing so, this can result in a
significant reduction in memory usage, particularly if there are a lot
of repeated values in text nodes. Please see
@@ -53,7 +54,9 @@
<jump
href="apiDocs/classXalanDefaultParsedSource.html">XalanDefaultParsedSource</jump>,
and
<jump
href="apiDocs/classXalanTransformer.html">XalanTransformer</jump> in the <jump
href="apiDocs/index.html">
API Reference</jump> section for more information.</li>
- <li>Upgrade from Xerces-C 2.5 to Xerces-C 2.6. </li>
+ <li>Added support for Microsoft Studio .NET V7.1. Project files for
Microsoft Studio .NET V7.1 have been provided under the
+ directory xml-xalan\c\Projects\Win32\VC7.1.</li>
+ <li>Upgrade from Xerces-C 2.5 to Xerces-C 2.6. </li>
<li><link anchor="bugfixes">Bugs fixed in this release</link>.</li>
</ul>
</s3>
@@ -136,7 +139,20 @@
</s3>
<anchor name="xml4c"/>
-&status-c;
+&status-c;
+
+<anchor name="contact"/>
+<s3 title="Getting in Touch">
+<p>Your feedback is more than welcome. Offers of help are even more so!
Perhaps you would like to contribute to the ongoing development, testing, or
documentation of &xslt4c;.</p>
+<p>Please email your comments, questions, suggestions, bug reports, and
offers to help to <human-resource-ref idref="xalandev"/>.</p>
+</s3>
+
+<anchor name="history"/>
+<s3 title="Cumulative history of software changes">
+<p>The following sections list the changes in each release since &xslt4c;
version 0.40.0.</p>
+&history-c;
+</s3>
+
</s2>
</s1>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
