Significant edits for Xalan-C 1.11 pre-release
diff --git a/docs/xalan/xalan-c/builddocs.html b/docs/xalan/xalan-c/builddocs.html
index 5e6d60f..83a7fce 100644
--- a/docs/xalan/xalan-c/builddocs.html
+++ b/docs/xalan/xalan-c/builddocs.html
@@ -355,7 +355,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Thu 2012-10-04</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/buildlibs.html b/docs/xalan/xalan-c/buildlibs.html
index b5f2e99..7629b81 100644
--- a/docs/xalan/xalan-c/buildlibs.html
+++ b/docs/xalan/xalan-c/buildlibs.html
@@ -139,30 +139,41 @@
<h2>Building Xalan-C/C++</h2>
<ul>
<li>
+<a href="#SourceTools">The Distribution Source Tools</a>
+</li>
+ <ul>
+ <li>
+<a href="#WinBldScripts">Prepare Windows Build Scripts"</a>
+</li>
+ <li>
+<a href="#PrepUnixBld">Prepare Unix Build Scripts</a>
+</li>
+ </ul>
+<li>
<a href="#winbldenv">Windows Build Environment</a>
</li>
-<ul>
-<li>
+ <ul>
+ <li>
<a href="#winbld">Windows Basic Build Instruction</a>
</li>
-<li>
+ <li>
<a href="#winbldcmd">Sample Windows Build Command File</a>
</li>
-<li>
+ <li>
<a href="#winbldinst">Installing the Xalan Library on Windows</a>
</li>
-</ul>
+ </ul>
<li>
<a href="#unixbldenv">UNIX Build Environment</a>
</li>
-<ul>
-<li>
+ <ul>
+ <li>
<a href="#unixlibpath">Finding Runtime Libraries</a>
</li>
-<li>
+ <li>
<a href="#unixbldxalan">Building the Xalan-C/C++ XSLT Libraries for UNIX</a>
</li>
-</ul>
+ </ul>
<li>
<a href="#unixcompileref">Reference on Unix Platforms and C++ Compilers</a>
</li>
@@ -173,18 +184,149 @@
</ul>
<br />
-<p>The Xalan-C/C++ XSLT library is built upon the Xerces-C/C++ XML Parser library. Before compiling the Xalan-C/C++ XSLT library, you must have a usable Xerces-C/C++ library.
+<p>The Xalan-C/C++ XSLT library is built upon the Xerces-C/C++ XML Parser library.
+ Before compiling the Xalan-C/C++ XSLT library, you must have a usable Xerces-C/C++ library.
</p>
-<p>You can either install a compatible binary distribution of Xerces-C/C++ or build your own from a source distribution of Xerces-C/C++. You can gain additional capability if you build the Xerces-C/C++ XML Parser library from sources. The Xerces-C/C++ binary distribution is not built for the IBM-ICU libraries. The IBM-ICU libraries provide additional transcoding services.
+<p>You can either install a compatible binary distribution of Xerces-C/C++ or
+ build your own from a source distribution of Xerces-C/C++. You can gain additional
+ capability if you build the Xerces-C/C++ XML Parser library from sources.
+ The Xerces-C/C++ binary distribution is not built for the IBM-ICU libraries.
+ The IBM-ICU libraries provide additional transcoding services.
</p>
-<p>Building the source code packages ensures that the resulting packages are proper for your system. There are various binary distributions available, but incompatibilities between C++ compilers (even between compiler versions) are known to cause issues with sharing of libraries.
-</p>
-<p>We don't have persons yet committed to build binary distribution releases.
+<p>Building from the source code packages for Xerces and Xalan libraries ensures that the
+ resulting packages are proper for your system. There are various binary distributions
+ available, but incompatibilities between C++ compilers (even between compiler versions)
+ are known to cause issues with sharing of libraries.
</p>
<p>You can get more information on the Xerces-C/C++ distributions at the
<a href="http://xerces.apache.org/xerces-c">http://xerces.apache.org/xerces-c</a> web site.
</p>
+<a name="SourceTools"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>The Distribution Source Tools</h3>
+<p>We are including in the distribution some script files that can help with
+ build environment setup and distribution package creation. These script
+ packages are working examples that developers can use for their own work.</p>
+
+<ul>
+<li>
+<b>
+<code>(src)/scripts/xalan-ms-scripts.zip</code>
+</b> For Windows Packages</li>
+<li>
+<b>
+<code>(src)/scripts/xalan-unix-scripts.tar</code>
+</b> For Unix/Linux Packages</li>
+</ul>
+
+<p>The following discussions in this chapter describe the rules by which these
+ scripts were written.</p>
+<a name="WinBldScripts"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Prepare Windows Build Scripts</h4>
+<p>I use the <code>
+<b>C:\Apache\xalan-builds\</b>
+</code> directory as the home path
+ for building Windows packages. You may need to edit the scripts for your own
+ package build location.</p>
+<p>You will need a copy of Microsoft Visual Studio .NET installed on your development computer.</p>
+<ol>
+<li>Create your package building directory.</li>
+<li>Unzip the <code>
+<b>xalan-ms-scripts.zip</b>
+</code> into your package building directory.</li>
+<li>Copy the Xerces-C sources into a builds subdirectory <code>
+<b>xerces-src-31</b>
+</code>.</li>
+<li>Copy the Xalan-C sources into a builds subdirectory <code>
+<b>xalan-src-11</b>
+</code>.</li>
+<li>You need the Xerces-C binaries available before building the Xalan-C sources.</li>
+ <ul>
+ <li>Build the Xerces-C sources using an appropriate
+ <code>
+<b>xerces-build-31-*.bat</b>
+</code> script.
+ This script launches Microsoft Visual Studio with an appropriate environment set.</li>
+ <li>Construct the Xerces-C binary package using the appropriate
+ <code>
+<b>xerces-inst-31-*.bat</b>
+</code> script. This binary package is later
+ used for the XERCESCPKG environment variable.</li>
+ </ul>
+<li>You can now create the Xalan-C binary package.</li>
+ <ul>
+ <li>Build the Xalan-C sources using an appropriate
+ <code>
+<b>xalan-build-11-31-*.bat</b>
+</code> script.
+ This script launches Microsoft Visual Studio with an appropriate environment set.</li>
+ <li>Construct the Xalan-C binary package using the apppropriate
+ <code>
+<b>xalan-inst-11-31-*.bat</b>
+</code> script. This binary package can later
+ be used for the XALANCPKG environment variable.</li>
+ </ul>
+<li>You can now copy the (XERCESCPKG-31)/bin to your Windows installation directory.</li>
+<li>You can now copy the (XALANCPKG-11-31)/bin to your Windows installation directory.</li>
+<li>You can also merge the (XERCESCPKG-31)/include and (XALANCPKG-11-31)/include to your
+ Windows installation directory.</li>
+<li>You can also merge the (XERCESCPKG-31)/lib and (XALANCPKG-11-31)/lib to your
+ Windows installation directory.</li>
+</ol>
+
+<a name="PrepUnixBld"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Prepare Unix Build Scripts</h4>
+<p>I use my <code>
+<b>$HOME</b>
+</code> directory as the path into which
+ <code>
+<b>xalan-unix-scripts.tar</b>
+</code> is extracted.
+ I create subdirectory <code>
+<b>xerces-src</b>
+</code> for the Xerces-C sources and
+ another subdirectory <code>
+<b>xalan-src</b>
+</code> for the Xalan-C sources.
+ I then create separate directories into which the actual build process
+ takes place.</p>
+<p>Directory <code>
+<b>Xerces-Build</b>
+</code> is where I make the Xerces-C binaries.</p>
+<p>Directory <code>
+<b>Xalan-Build</b>
+</code> is where I make the Xalan-C binaries.</p>
+<p>The following scripts are used to make and install the <b>release</b> build
+ of binary products to the <code>
+<b>/opt/apache/</b>
+</code> target directory path.
+ Connect to the appropriate build directory and execute the appropriate script.
+</p>
+<ul>
+ <li>xerces-build.sh</li>
+ <li>xalan-build.sh</li>
+</ul>
+<p>The following scripts are used to make and install the <b>debug</b> build
+ of binary products to the <code>
+<b>/opt/apache/debug/</b>
+</code> target directory path.
+ Connect to the appropriate build directory and execute the appropriate script.
+</p>
+<ul>
+ <li>xerces-build-debug.sh</li>
+ <li>xalan-build-debug.sh</li>
+</ul>
+
+
<a name="winbldenv"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
@@ -896,7 +1038,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Thu 2012-10-04</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/charter.html b/docs/xalan/xalan-c/charter.html
index 3999ca9..e77847a 100644
--- a/docs/xalan/xalan-c/charter.html
+++ b/docs/xalan/xalan-c/charter.html
@@ -482,7 +482,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/commandline.html b/docs/xalan/xalan-c/commandline.html
index 2461545..f2f7f9c 100644
--- a/docs/xalan/xalan-c/commandline.html
+++ b/docs/xalan/xalan-c/commandline.html
@@ -249,7 +249,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/download.html b/docs/xalan/xalan-c/download.html
index 08f435c..1455360 100644
--- a/docs/xalan/xalan-c/download.html
+++ b/docs/xalan/xalan-c/download.html
@@ -137,49 +137,52 @@
</div>
<div id="content">
<h2>Downloading Xalan-C++</h2>
-<a name="download"></a>
-<p>The downloads for Xalan-C/C++ for Version 1.11 will be available here when published
- (<a href="http://www.apache.org/dyn/closer.cgi/xalan/xalan-c">xalan-c distribution</a>).</p>
-<p>You can find the old
-<a href="../old/xalan-c/index.html">version 1.10 release</a> here.
-</p>
+<ul>
+ <li>
+<a href="#DownloadWhat">Downloading What You Need</a>
+</li>
+ <li>
+<a href="#DownloadNotes">Downloading Notes</a>
+</li>
-<p>We are providing a source package, a documentation package, and
-some compiled binary packages.
-</p>
+ <li>
+<a href="#SourcePkgs">Source Packages</a>
+</li>
+ <li>
+<a href="#DocPkgs">Documentation Packages</a>
+</li>
+ <li>
+<a href="#BinaryPkgs">Binary Packages</a>
+</li>
+ <li>
+<a href="#VerifyPkgs">Verify Downloaded Packages</a>
+</li>
+ <li>
+<a href="#PlatformComp">Platform Compatibility</a>
+</li>
+</ul>
-<p>The binary packages are currently for Windows systems. We can
-use your help <a href="buildlibs.html">creating binary packages</a> for
-UNIX and Linux systems.
-</p>
-
-<p>A distribution will be mirrored and these pages updated when the packages
-become available to the general public. The current packages for download
-are in a temporary repository for developers.
-</p>
-
-<p>The subversion sources are current for Xalan-C/C++ Version 1.11 and are
-available for download using your favorite subversion <code>svn</code> program.</p>
-
-<p>Apache Xalan-C/C++ Subversion Repository is accessed here.<br />
-<a href="http://svn.apache.org/repos/asf/xalan/c/trunk">
-http://svn.apache.org/repos/asf/xalan/c/trunk</a>
-</p>
-
+<a name="DownloadWhat"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
-<h3>Downloading what you need</h3>
+<h3>Downloading What You Need</h3>
-<p>The Xalan-C/C++ library requires the
-<a href="http://www.apache.org/dyn/closer.cgi/xerces/c">Xerces-C/C++ XML</a> Parser 3.0
-or newer, version 3.1.1 is preferred.
+<p>We are distributing the source package for the Xalan-C/C++
+library, sample programs, and documentation. We are also
+distributing assembled documentation packages for your
+browser. Some selected platforms also have binary packages.
+</p>
+
+<p>The Xalan-C/C++ 1.11 library requires the
+<a href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xerces/c">Xerces-C/C++ XML</a>
+Parser 3.0 or newer, version 3.1.1 is preferred.
</p>
<p>The source package contains all the scripts needed to build the
library, sample programs, and documentation for a wide variety
of Windows and UNIX platforms. The documentation package provides
-usable html documentation for your web browsers.
+usable html documentation that is already assembled for your web browsers.
</p>
<p>Building the API Reference documents requires a current version of the
@@ -189,75 +192,263 @@
A usable API Reference is included with the documentation package.
</p>
+
+<a name="DownloadNotes"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Downloading Notes</h3>
+
+<p>Releases are distributed via various mirror sites around the world,
+and the links below will direct you to a mirror near you.
+Alternative mirror locations are also provided.</p>
+
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">You must <a href="#VerifyPkgs">verify the integrity</a> of the downloaded files
+using signatures downloaded from the Apache master distribution directory.</td>
+</tr>
+</table>
+
+<p>Access to the latest (and possibly unstable) source can be accessed via
+<a href="http://svn.apache.org/repos/asf/xalan/xalan-c/trunk">SVN</a>
+</p>
+
+<p>Archives of old Xalan-C/C++ releases can be found at the
+<a href="http:archive.apache.org/dist/xalan/xalan-c">Apache Xalan Archives</a>
+and the
+<a href="http:archive.apache.org/dist/xml/xalan-c">Old Apache XML Archives</a>.</p>
+
+<p>Archives of old Xerces-C/C++ parser distributions can be found at the
+<a href="http:archive.apache.org/dist/xerces/c">Apache Xerces Archives</a>
+and the
+<a href="http:archive.apache.org/dist/xml/xalan-c">Old Apache XML Archives</a>.</p>
+
+
+
+
+
+<a name="SourcePkgs"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h4>Source Packages</h4>
-<p>We are distributing the source package for the Xalan-C/C++
-library, sample programs, and documentation. The source package
-has the StyleBook XML sources for the web pages and a Doxygen
-configuration file to construct the API Reference.
+<p>
+<b>Xalan-C/C++ <a href="http://www.apache.org/dist/xalan/xalan-c/KEYS">KEYS</a>
+</b>
</p>
-
<ul>
- <li>Xalan-C-1.11.source.tar.gz</li>
- <li>Xalan-C-1.11.source.zip</li>
+ <li>xalan-c-1.11-src.tar.gz</li>
+ <li>xalan-c-1.11-src.zip</li>
</ul>
+<p>You can download the Xalan-C/C++ source packages from the
+ <a href="http:///www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/sources">
+ Apache Mirrors</a>.</p>
+<p>You should <a href="#VerifyPkgs">verify</a> your packages against
+ the trusted signatures posted on the Apache master distribution site</p>
+<a name="DocPkgs"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h4>Documentation Packages</h4>
-<p>We are distributing a package of html web pages for the User
-Guide and interactive API Reference. The documentation package
-describes how to build and use the library for Windows and UNIX
-platforms.
+<p>These documentation packages can be built from the Xalan-C/C++
+<a href="#SourcePkgs">source distributions</a> on Linux or UNIX systems.
+Windows systems can only build the basic webpages without the apiDocs
+interactive API (Application Program Interface) pages.
</p>
-
+<p>The <b>html-full</b> is a very large package (355+ MB). It contains the
+ interactive graphics images that map the include file relationships and
+ class relationships. The <b>html-nograf</b> (42 MB) just contains tabular
+ relationships without the large volume of generated graphics.
+</p>
+<p>
+<b>Xalan-C/C++ <a href="http://www.apache.org/dist/xalan/xalan-c/KEYS">KEYS</a>
+</b>
+</p>
<ul>
- <li>Xalan-C-1.11.docs-html.tar.gz</li>
- <li>Xalan-C-1.11.docs-html.zip</li>
- <li>Xalan-C-1.11.docs-api.tar.gz</li>
- <li>Xalan-C-1.11.docs-api.zip</li>
+ <li>xalan-c-1.11-docs-html-full.tar.gz</li>
+ <li>xalan-c-1.11-docs-html-full.zip</li>
+ <li>xalan-c-1.11-docs-html-nograf.tar.gz</li>
+ <li>xalan-c-1.11-docs-html-nograf.zip</li>
</ul>
+<p>You can download the Xalan-C/C++ documentation packages from the
+ <a href="http:///www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/docs">
+ Apache Mirrors</a>.</p>
+<p>You should <a href="#VerifyPkgs">verify</a> your packages against
+ the trusted signatures posted on the Apache master distribution site</p>
+<a name="BinaryPkgs"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h4>Binary Packages</h4>
<p>We are distributing compiled binary packages for several
-platforms. The Xalan-C/C++ documentation is provided as a
-separate package. We would like to distribute
-binary packages for platforms that have compiled Xerces-C/C++
-distribution support.
+platforms. The Xalan-C/C++ <a href="#DocPkgs">documentation</a>
+is provided as a separate package. We would like to distribute binary packages
+for platforms on which Xerces-C/C++ has binary packages distributed.
+</p>
+<p>Both the Xalan (XSLT) and Xerces (XML Parser) libraries should
+both be compiled with the same version of C++ compiler. A mismatch
+of compiler versions is known to create runtime library reference
+errors. If you cannot find a compatible Xerces library, you should
+obtain the Xerces sources and compile both libraries.
+</p>
+<p>Binary packages labeled <b>xalan_combined</b> have compiled
+libraries for both Xalan-C/C++ and Xerces-C/C++. All binary
+packages include the <b>Xalan</b> or <b>xalan.exe</b>
+command line styleshet transformation processor.
</p>
-<p>The following binary packages are being prepared for distribution.</p>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">The development cycles for Xerces-C/C++ and Xalan-C/C++ are
+separately managed. There is no synchronization of product distribution.</td>
+</tr>
+</table>
+<p>
+<b>Windows Packages - 32 BIT</b>
+</p>
<ul>
- <li>Xalan-C-1.11.windows-x86-vc71.zip</li>
- <li>Xalan-C-1.11.windows-x86-vc8.zip</li>
- <li>Xalan-C-1.11.windows-x86-vc9.zip</li>
- <li>Xalan-C-1.11.windows-x86-vc10.zip</li>
- <li>Xalan-C-1.11.windows-x86_64-vc8.zip</li>
- <li>Xalan-C-1.11.windows-x86_64-vc9.zip</li>
- <li>Xalan-C-1.11.windows-x86_64-vc10.zip</li>
+ <li>xalan-c-1.11-x86-windows-vc71.zip for MS VS 2003</li>
+ <li>xalan-c-1.11-x86-windows-vc8.zip for MS VS 2005 </li>
+ <li>xalan-c-1.11-x86-windows-vc9.zip for MS VS 2008</li>
+ <li>xalan-c-1.11-x86-windows-vc10.zip for MS VS 2010</li>
</ul>
+<p>Combined with Xerces Parser</p>
+<ul>
+ <li>xalan_combined-c-1.11-x86-windows-vc71.zip for MS VS 2003</li>
+ <li>xalan_combined-c-1.11-x86-windows-vc8.zip for MS VS 2005 </li>
+ <li>xalan_combined-c-1.11-x86-windows-vc9.zip for MS VS 2008</li>
+ <li>xalan_combined-c-1.11-x86-windows-vc10.zip for MS VS 2010</li>
+</ul>
+<p>
+<b>Windows Packages - 64 BIT</b>
+</p>
+<ul>
+ <li>xalan-c-1.11-x86_64-windows-vc8.zip for MS VS 2005</li>
+ <li>xalan-c-1.11-x86_64-windows-vc9.zip for MS VS 2008</li>
+ <li>xalan-c-1.11-x86_64-windows-vc10.zip for MS VS 2010</li>
+</ul>
+<p>Combined with Xerces Parser</p>
+<ul>
+ <li>xalan_combined-c-1.11-x86_64-windows-vc8.zip for MS VS 2005</li>
+ <li>xalan_combined-c-1.11-x86_64-windows-vc9.zip for MS VS 2008</li>
+ <li>xalan_combined-c-1.11-x86_64-windows-vc10.zip for MS VS 2010</li>
+</ul>
+<p>
+<b>BSD Packages - 64 BIT</b>
+</p>
+<ul>
+ <li>xalan-c-1.11-x86_64-freebsd_9-gcc_4_2.tar.gz</li>
+ <li>xalan_combined-c-1.11-x86_64-freebsd_9-gcc_4_2.tar.gz</li>
+</ul>
+<p>
+<b>Linux Packages</b>
+</p>
+<ul>
+ <li>xalan-c-1.11-x86_64-linux_2_6_32-gcc_4_4.tar.gz</li>
+ <li>xalan_combined-c-1.11-x86_64-linux_2_6_32-gcc_4_4.tar.gz</li>
+</ul>
+<p>You can download the Xalan-C/C++ compiled binary packages from the
+ <a href="http:///www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/binaries">
+ Apache Mirrors</a>.</p>
+<p>You should <a href="#VerifyPkgs">verify</a> your packages against
+ the trusted signatures posted on the Apache master distribution site</p>
+
+
+<a name="VerifyPkgs"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Verify The Integrity of the Files</h3>
+
+<p>It is essential that you verify the integrity of the downloaded
+ files using the PGP or MD5 signatures. You should only download the
+ <a href="http://www.apache.org/dist/xalan/xalan-c/KEYS">KEYS</a>
+ and the (asc/md5) signature files from the Apache Master Distribution.
+ The Apache Mirrors of previous sections should be used to download
+ the products.</p>
+<ul>
+ <li>
+<a href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/sources">
+ Apache Mirror Xalan-C Sources</a>
+</li>
+ <li>
+<a href="http://www.apache.org/dist/xalan/xalan-c/source">
+ Apache Master Xalan-C Sources - for Signature Files</a>
+</li>
+ <li>
+<a href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/docs">
+ Apache Mirror Xalan-C Documentation</a>
+</li>
+ <li>
+<a href="http://www.apache.org/dist/xalan/xalan-c/docs">
+ Apache Master Xalan-C Documentation - for Signature Files</a>
+</li>
+ <li>
+<a href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/binaries">
+ Apache Mirror Xalan-C Binary Packages</a>
+</li>
+ <li>
+<a href="http://www.apache.org/dist/xalan/xalan-c/binaries">
+ Apache Master Xalan-C Binary Packages - for Signature Files</a>
+</li>
+</ul>
+
+<p>Make sure you get the signature file for the particular distribution from the master directory,
+ rather than from a mirror.
+ Then verify the signatures using:</p>
+<blockquote class="source">
+<pre>
+ % pgpk -a KEYS
+ % pgpv <archive-name>.tar.gz.asc
+</pre>
+</blockquote>
+<b>or</b>
+<blockquote class="source">
+<pre>
+ % pgp -ka KEYS
+ % pgp <archive-name>.tar.gz.asc
+</pre>
+</blockquote>
+<b>or</b>
+<blockquote class="source">
+<pre>
+ % gpg --import KEYS
+ % gpg --verify <archive-name>.tar.gz.asc
+</pre>
+</blockquote>
+<p>Alternatively, you can verify the MD5 signature on the files.
+A unix program called md5 or md5sum is included in many unix distributions.
+It is also available as part of
+<a href="http://www.gnu.org/directory/text/wordproc/textutils.html">GNU Textutils</a>.
+ Windows users can get binary md5 programs from
+<a href="http://www.fourmilab.ch/md5/">here</a>,
+<a href="http://www.pc-tools.net/win32/freeware/console/">here</a>, or
+<a href="http://www.slavasoft.com/fsum/">here</a>.</p>
+
+<a name="PlatformComp"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Platform Compatibility</h3>
<p>We currently have no one committed to release UNIX and Linux
binary packages. If you have scripts to build these packages,
your help would be appreciated.
You can contribute by posting your comments to the
-<a href="mailto:dev@xalan.apache.org">xalan-dev</a> mailing list.
-</p>
+<a href="mailto:dev@xalan.apache.org">xalan-dev</a> mailing list.</p>
-
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Platform Compatibility</h4>
<p>The compiler version used for each platform is listed in the table below.
The build platforms shown here have Xerces-C/C++ binary package support.
<table border="1">
@@ -329,16 +520,21 @@
<td class="noteImg">
<img src="resources/note.gif" alt="note" />
</td>
-<td class="noteTxt">Use GNU tar to untar the Solaris distribution file; see <a href="faq.html#faq-11">A tar checksum error on Solaris
- </a>.
+<td class="noteTxt">Use GNU tar to untar the Solaris distribution file; see
+ <a href="faq.html#faq-11">A tar checksum error on Solaris</a>.
</td>
</tr>
</table>
-<p>If you want to take advantage of the support for number formatting, sorting, and encoding the ICU provides, you should also download
- and install the <a href="http://oss.software.ibm.com/icu/index.html">International Components for Unicode (ICU)</a>; see <a href="usagepatterns.html#icu">Using the ICU</a>,</p>
+<p>If you want to take advantage of the support for number formatting, sorting,
+ and encoding the ICU provides, you should also download
+ and install the <a href="http://oss.software.ibm.com/icu/index.html">International Components for Unicode (ICU)</a>; see
+ <a href="usagepatterns.html#icu">Using the ICU</a>.
+</p>
-<p>The IBM ICU is supported with Xerces-C version 2.8. Xerces-C version 3 has introduced transcoding support modules, currently being evaluated for Xalan XSLT transcoders.
+<p>The IBM ICU is supported with Xerces-C version 2.8. Xerces-C version 3 has
+ introduced transcoding support modules, currently being evaluated
+ for Xalan XSLT transcoders.
</p>
<table class="note">
@@ -346,18 +542,17 @@
<td class="noteImg">
<img src="resources/note.gif" alt="note" />
</td>
-<td class="noteTxt">To access previous releases of Xalan-C++, visit the <a href="http://archive.apache.org/dist/xml/xalan-c/">Xalan-C archive
- directory</a>.
+<td class="noteTxt">To access previous releases of Xalan-C++, visit the
+ <a href="http://archive.apache.org/dist/xml/xalan-c/">Xalan-C archive directory</a>
</td>
</tr>
</table>
-
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/30/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Tue 2012-10-09</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/extensions.html b/docs/xalan/xalan-c/extensions.html
index 87d751b..5775176 100644
--- a/docs/xalan/xalan-c/extensions.html
+++ b/docs/xalan/xalan-c/extensions.html
@@ -434,7 +434,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/extensionslib.html b/docs/xalan/xalan-c/extensionslib.html
index bb96dd8..167a8e5 100644
--- a/docs/xalan/xalan-c/extensionslib.html
+++ b/docs/xalan/xalan-c/extensionslib.html
@@ -362,7 +362,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/faq.html b/docs/xalan/xalan-c/faq.html
index 1e6cde1..939e4a8 100644
--- a/docs/xalan/xalan-c/faq.html
+++ b/docs/xalan/xalan-c/faq.html
@@ -726,7 +726,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/30/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/getstarted.html b/docs/xalan/xalan-c/getstarted.html
index dcc8fd8..7f6e629 100644
--- a/docs/xalan/xalan-c/getstarted.html
+++ b/docs/xalan/xalan-c/getstarted.html
@@ -443,7 +443,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/index.html b/docs/xalan/xalan-c/index.html
index ec4ec4c..852065a 100644
--- a/docs/xalan/xalan-c/index.html
+++ b/docs/xalan/xalan-c/index.html
@@ -515,13 +515,13 @@
<tr>
<td class="content" rowspan="1" colspan="1">Xalan-C Version 1.10</td>
<td class="content" rowspan="1" colspan="1">
-<a href="http://www.apache.org/dyn/closer.cgi/xml/xalan-c/">Xalan Package Downloads</a>
+<a href="http://archive.apache.org/dist/xml/xalan-c/">Xalan Package Downloads</a>
</td>
</tr>
<tr>
<td class="content" rowspan="1" colspan="1">Xerces-C Version 2.7</td>
<td class="content" rowspan="1" colspan="1">
-<a href="http://www.apache.org/dyn/closer.cgi/xml/xerces-c/">Xerces Package Downloads</a>
+<a href="http://archive.apache.org/dist/xml/xerces-c/">Xerces Package Downloads</a>
</td>
</tr>
</table>
@@ -531,7 +531,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/30/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/install.html b/docs/xalan/xalan-c/install.html
index cd1a81c..9ca564e 100644
--- a/docs/xalan/xalan-c/install.html
+++ b/docs/xalan/xalan-c/install.html
@@ -138,244 +138,358 @@
<div id="content">
<h2>Installing Xalan-C++</h2>
+
<ul>
- <li>
-<a href="#SourcePkgs">Install Source Packages</a>
+<li>
+<a href="#InstSrcPkgs">Install Source Packages</a>
</li>
- <li>
-<a href="#BinaryPkgs">Install Binary Packages</a>
+<li>
+<a href="#InstBinPkgs">Install Binary Packages</a>
</li>
<ul>
- <li>
-<a href="#InsWin">Install Windows Packages</a>
-</li>
- <li>
-<a href="#InsUnx">InstallUNIX Packages</a>
-</li>
- <li>
-<a href="#InsPkgs">Other Packages</a>
-</li>
- </ul>
<li>
-<a href="#XalanDocPkg">Install Documentation Packages</a>
+<a href="#InstUnixBinPkgs">Install UNIX Binary Packages</a>
</li>
- <ul>
+ <ul>
<li>
-<a href="">Xalan-C User Guide</a>
+<a href="#ConfigUnixSys">Configure UNIX and Linux Systems</a>
</li>
+ </ul>
+ <li>
+<a href="#InstWinBinPkgs">Install Windows Binary Packages</a>
+</li>
+ <ul>
<li>
-<a href="">Xalan-C API Reference</a>
+<a href="#ConfWinPath">Configure Windows PATH</a>
</li>
+ </ul>
</ul>
+<li>
+<a href="#InstDocPkgs">Install Documentation Package</a>
+</li>
</ul>
-<p>A pre-requisite for using the Xalan-C/C++ XSLT library is to
- have a working Xerces-C/C++ XML Parser library. Xerces-C/C++
- must be of version 3.0 or newer. Xerces-C/C++ Version 3.1.1 is preferred.
-</p>
-<p>The Xalan-C/C++ project is providing several types of packages.
-</p>
-<p>Source packages contain all of the source code to build the
- Xalan-C/C++ library, the sample programs, and the documentation.
- There are UNIX scripts and Windows project files by which the
- library and sample programs can be built.
- There are also scripts for building the User Guide web pages and
- a Doxygen configuration for building the interactive API Reference.
-</p>
-<p>Binary packages contain compiled libraries and the Xalan
- command line program. The binary packages also contain C/C++
- header files for basic software development.
-</p>
-<p>Documentation packages contain pre-built directories of web
- page html files for the Xalan-C/C++ User Guide and the interactive
- API Reference for programmers.
-</p>
-
-<a name="SourcePkgs"></a>
+<a name="InstSrcPkgs"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>Install Source Packages</h3>
-<p>We have no package managers for source packages. You just extract
- the contents of the distribution <b>
-<i>zip</i>
-</b> file or <b>
-<i>tar</i>
-</b> file
- into a source directory of your choosing.
-</p>
-<p>You also need to have the necessary C/C++ compiler tools installed
- and a working copy of the Xerces-C/C++ XML parser library.
-</p>
-<p>Building the
- <a href="builddocs.html#buildweb">User Guide</a>
- from sources requires a working Xalan command line program.
-</p>
-<p>Building the interactive
- <a href="builddocs.html#buildapi">API Reference</a>
- requires a UNIX or Linux system with a current copy of
- Doxygen and GraphViz installed.
-</p>
-<p>The building of a library from sources results in a directory from which
- a binary package can be made.
- <a href="buildlibs.html#unixbldenv">UNIX and Linux builds</a>
- are automatically targeted to an install destination.
- <a href="buildlibs.html#winbldinst">Installing a Windows build</a>
- requires that the specific compiled products be copied to a usable
- destination directory.
-</p>
+<p>We have no package managers for source packages.
+You just extract the contents of the distribution <b>zip</b> or <b>tar</b> file
+into a source directory of your choosing.</p>
+
+<p>The supplemental package building scripts for Linux and UNIX look for the
+Xalan-C sources to be found in a directory named <code>
+<b>xalan-src</b>
+</code>.
+The Xerces-C sources are expected to be found in a directory named <code>
+<b>xerces-src</b>
+</code>.</p>
+
+<p>The supplemental package building scripts for Windows look for the Xalan-C
+sources to be found in a directory named <code>
+<b>xalan-src-11</b>
+</code>
+and the Xerces-C sources to be found in a directory named <code>
+<b>xerces-src-31</b>
+</code>.</p>
+
+<p>When building the Xalan-C library and sample programs,
+you also need the necessary C/C++ compiler tools installed.
+A working copy of the Xerces-C XML parser library must be available
+before you can build the Xalan-C library.
+You may build the Xerces-C XML parser library from a source distribution
+or use a compatible Xerces-C binary distribution.</p>
+
+<p>Building the User Guide web pages from sources requires a
+working Xalan command line program. The Xalan command-line program must support
+top-level parameters as strings.</p>
+
+<p>Building the interactive API Reference pages requires a UNIX or Linux
+system with a current copy of Doxygen and GraphViz software installed.</p>
-<a name="BinaryPkgs"></a>
+<a name="InstBinPkgs"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>Install Binary Packages</h3>
-<p>The binary packages distributed by <b>
-<i>zip</i>
-</b> files
- and <b>
-<i>tar</i>
-</b> files are usually extracted to the install
- <code>{target}</code> directory.
- After extracting the contents, you then need to manually perform
- some minor system configuration.
-</p>
-<p>Packages that are handled by a package manager are usually
- installed and configured according to package maintainer.</p>
-<a name="InsWin"></a>
+<p>The binary packages distributed by <b>zip</b> and <b>tar</b> files are
+usually extracted to an install directory of your choosing.
+After extracting the contents, and possibly relocating some items,
+you may then need to manually perform some minor system configuration.</p>
+
+<a name="InstUnixBinPkgs"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
-<h4>Install Windows Packages</h4>
-<p>The Xalan-C and Xerces-C packages can be installed to the same
- <code>{target}</code>
- directory tree. The debug and release builds have different names
- for the shared <code>*.DLL</code> files.
+<h4>Install UNIX Binary Packages</h4>
+
+<p>Binary packages for Linux and UNIX systems only distribute a <b>release</b> build of binaries.
+A debug build of binaries requires you to compile from the sources.
+Binary packages for Linux and UNIX systems have the following directory structure.</p>
+
+<table border="1">
+<tr>
+<td class="content" rowspan="1" colspan="1">./bin/</td>
+<td class="content" rowspan="1" colspan="1">Contains the Xalan.exe command line and DLLs</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">./lib/</td>
+<td class="content" rowspan="1" colspan="1">Contains the linker libraries</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">./include/xalanc/</td>
+<td class="content" rowspan="1" colspan="1">Contains the Xalan-C header files</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">./doc/xalanc-1.11/</td>
+<td class="content" rowspan="1" colspan="1">Contains license and other information</td>
+</tr>
+</table>
+
+<p>Supplemental scripts for Linux and UNIX builds are available in the
+source distribution by which binary packages can be made.
+The release builds are targeted to <code>${prefix} = /opt/apache/</code>.
+The debug buids are targeted to <code>${prefix} = /opt/apache/debug/</code>.</p>
+
+<p>Packages that are released by a UNIX or Linux package manager are
+usually installed and configured by the package manager.</p>
+
+<a name="ConfigUnixSys"></a>
+<h5>Configure UNIX and Linux Systems</h5>
+
+<p>The Xalan command line executable should be in a directory
+accessible by the PATH environment.</p>
+
+<p>The lib directories containing the <code>
+<b>libxalan-c.so</b>
+</code> and
+<code>
+<b>libxerces-c.so</b>
+</code> objects must be known to the shared object loader.
+The system loader environment variable usually takes precedence
+over the shared object cache.
+I use the shared object cache for installed applications and reserve
+the overriding environment for prototype builds and debugging purposes.</p>
+
+<table border="1">
+<tr>
+<th class="content" rowspan="1" colspan="1">Operating System</th>
+<th class="content" rowspan="1" colspan="1">Library Path Environment</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">Solaris and Linux</td>
+<td class="content" rowspan="1" colspan="1">LD_LIBRARY_PATH</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">BSD/GNU</td>
+<td class="content" rowspan="1" colspan="1">LD_LIBRARY_PATH</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">HP-UX</td>
+<td class="content" rowspan="1" colspan="1">SHLIB_PATH</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">AIX and BSD</td>
+<td class="content" rowspan="1" colspan="1">LIBPATH</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">MacOSX</td>
+<td class="content" rowspan="1" colspan="1">DYLD_LIBRARY_PATH</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">Cygwin and MinGW</td>
+<td class="content" rowspan="1" colspan="1">PATH</td>
+</tr>
+</table>
+
+<p>The library search path order is significant.
+In many cases, the <code>
+<b>/usr/lib</b>
+</code>, <code>
+<b>/lib</b>
+</code>,
+and <code>
+<b>/usr/local/lib</b>
+</code> paths are already cached
+in <code>
+<b>/etc/ld.so.cache</b>
+</code> or included by <code>
+<b>/etc/ld.so.conf</b>
+</code>.</p>
+
+
+
+<a name="InstWinBinPkgs"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
</p>
-<p>Windows operating systems require that the <code>{target}\bin</code>
- directory be added to the PATH environment. You can make the path
- a permanent part of the SYSTEM or user login DESKTOP environment.
- The PATH environment variable should contain an entry
- where the <code>{target}\bin\*.DLL</code> files are found.
-</p>
+<h4>Install Windows Binary Packages</h4>
+
+<p>Binary packages for Windows systems include a directory name
+related to the Windows Studio platform used to build the product.
+The <code>{<b>bin</b>, <b>lib</b>, <b>include</b>, <b>doc</b>}</code> directories
+are subdirectories of the platform directory.
+Libraries for several Visual Studio development systems
+can be installed on the same Windows computer.</p>
+<table border="1">
+<tr>
+<td class="content" rowspan="1" colspan="1">XALANCPKG-11-31-VC71</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2003 (Win32)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">XALANCPKG-11-31-VC80</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2005 (Win32)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">XALANCPKG-11-31-VC90</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2008 (Win32)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">XALANCPKG-11-31-VC100</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2010 (Win32)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">XALANCPKG-11-31-X64-VC80</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2005 (amd64)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">XALANCPKG-11-31-X64-VC90</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2008 (amd64)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">XALANCPKG-11-31-X64-VC100</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2010 (amd64)</td>
+</tr>
+</table>
+
+<p>Supplemental scripts for Windows builds are available in the source distribution
+by which these above binary packages can be made.
+Also included are scripts for building the Xerces-C sources
+to the following binary package directories.
+These directories are mostly compatible with the required
+XALANCROOT and XERCESCROOT environment variables when building your own applications.</p>
+
+<table border="1">
+<tr>
+<td class="content" rowspan="1" colspan="1">XERCESCPKG-31-VC71</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2003 (Win32)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">XERCESCPKG-31-VC80</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2005 (Win32)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">XERCESCPKG-31-VC90</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2008 (Win32)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">XERCESCPKG-31-VC100</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2010 (Win32)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">XERCESCPKG-31-X64-VC80</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2005 (amd64)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">XERCESCPKG-31-X64-VC90</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2008 (amd64)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">XERCESCPKG-31-X64-VC100</td>
+<td class="content" rowspan="1" colspan="1">for Visual Studio 2010 (amd64)</td>
+</tr>
+</table>
+
+<p>Supplemental scripts for Windows builds will also handle the packaging of older
+Xalan-C and Xerces-C releases. A similar naming of package directories and
+source directories is supported for these older releases.</p>
+
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">You MUST NOT merge the <b>bin</b> and <b>lib</b> directories from packages
+compiled with different compilers or different target (Win32 or amd64) platforms.</td>
+</tr>
+</table>
+
+<p>It is safe to merge the <b>bin</b> directories of compatible Xalan-C and Xerces-C
+distributions into a common directory known by the system PATH environment.
+You can safely merge the <b>lib</b> directories of Xalan-C and Xerces-C into a common directory.
+ You can safely merge the <b>include</b> directories of both Xalan-C and Xerces-C
+as long as the subdirectories of <b>xalanc</b> and <b>xercesc</b> remain intact.</p>
+
+<a name="ConfWinPath"></a>
+<h5>Configure Windows PATH</h5>
+
+<p>Windows systems require that the bin directories be added to the
+PATH environment so the library DLL files can be found.
+The <b>Xalan.exe</b> program is dynamically linked to these libraries.</p>
+
+<p>You can make the PATH environment a permanent part of the SYSTEM or user login DESKTOP environment.
+Any PATH you add to the user login DESKTOP environment gets automatically prepended to the
+SYSTEM PATH environment and is effective upon successful user DESKTOP login. If your
+computer also starts Windows Services that run on behalf of a user, the user environment
+is assumed.</p>
+
<ol>
- <li>Right-Click on the computer icon.</li>
- <li>Select Properties.</li>
- <li>Select Advanced System Settings.</li>
- <li>Select Environment Variables.</li>
- <li>Add the <code>{target}\bin</code> directory to the
- system PATH environment variable.</li>
+<li>Right-Click on the computer icon.</li>
+<li>Select Properties</li>
+<li>Select Advanced System Settings.</li>
+<li>SelectEnvironment Variables.</li>
+<li>Add the bin directory to the system PATH environment.</li>
</ol>
-<p>The XP, NT, 2000 and 2003 systems allow environment variables to be
- set explicitly to individual user accounts.
- The Vista, Win-7, and 2008 systems have security administration that
- gets in the way of updating individual user environments.
-</p>
-<p>In a command window or a command environment, you can add the following
- shell command to set a temporary path to the XALAN <code>{target}\bin</code>
- directory.
-</p>
+
+<p>The XP, NT, 2000, and 3000 systems allow environment variables to be
+set explicitly to individual user accounts.
+The Vista, Win-7, and 2008 systems have security administration
+that gets in the way of updating individual user environments.</p>
+
+<p>Or you can add the <b>bin</b> directories temporarily to your environment by program control
+or invoking a shell command script, or using a command window.
+The following command line will append your <code>{target}/<b>bin</b>
+</code> directory
+to the PATH environment.</p>
<blockquote class="source">
-<pre>set PATH=%PATH%;{target}\bin</pre>
+<pre>
+set PATH=%PATH%;{target}/bin
+</pre>
</blockquote>
-<a name="InsUnx"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Install UNIX Packages</h4>
- <p>The path to the <code>Xalan</code> command line executable program should be added
- to the PATH environment variable.</p>
- <p>The path to the shared objects should be added to the system
- configuration or overridden by specific entry in an environment
- by which shared objects can be found.</p>
-<p>Here is some more detailed information on
- <a href="buildlibs.html#unixlibpath">UNIX Runtime</a> configuration.
-</p>
-<a name="InsPkgs"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Install Other Packages</h4>
-<p>These packages are usually installed and configured by a package manager.
- You should refer to the documentation provided by the package maintainer.
-</p>
-
-
-
-<a name="XalanDocPkg"></a>
+<a name="InstDocPkgs"></a>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
<h3>Install Documentation Packages</h3>
-<p>The documentation packages are distributed as <b>
-<i>tar</i>
-</b> files
- and <b>
-<i>zip</i>
-</b> files. You just extract the files into a directory
- that is reachable by your favorite web browser. The head of the
- documentation tree starts at the <a href="index.html">
- <code>{docs}/xalan-c</code>
-</a> directory.
-</p>
-<p>
-<b>TO DO:</b>
-</p>
-<p>Rework the xalan/c/trunk/xdocs/sources/ scripts so that the
- source documentation builds are
- targeted to the xalan/c/trunk/build/docs/xalan-c/ directory path.
-</p>
-<p>Add a documentation script that performs a post-processing
- operation when building the API Reference from Doxygen to relocate
- the constructed products to the xalan/c/trunk/build/docs/xalan-c/apiDocs/
- directory path.
-</p>
-<p>Details are found in our <a href="builddocs.html">Build Documents</a> pages.
-</p>
-<a name="DocWebPkg"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Install Xalan-C User Guide</h4>
-<p>Extract the distributed <b>
-<i>tar</i>
-</b> file or <b>
-<i>zip</i>
-</b>
- file to the <code>{docs}</code> directory. The package populates
- the <code>{docs}/xalan-c/*</code> directory containing the Xalan-C
- User Guide web pages.
-</p>
+<p>There are actually two distributed documentation packages.
+One contains the website pages and full interactive apiDoc images (355+ megabytes).
+The other contains the website pages and the apiDoc descriptions (47 megabytes)
+without the apiDoc images.
+Except for the absence of interactive apiDoc images,
+the documentation packages are identical.</p>
+<p>The documentation packages are distributed as <b>tar</b> and <b>zip</b> files.
+You just extract the contents into a directory that is reachable by your favorite web browser.
+The documentation tree starts with the <b>./xalan-c/</b> directory.
+The top documentation page is the <b>./xalan-c/index.html</b> file.</p>
-<a name="DocApiPkg"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Install Xalan-C API Reference</h4>
-<p>Extract the distributed <b>
-<i>tar</i>
-</b> file or <b>
-<i>zip</i>
-</b>
- file to the <code>{docs}</code> directory. The package populates
- the <code>{docs}/xalan-c/apiDocs/*</code> directory containing the
- Xalan-C API Reference for programmers.
-</p>
-
+<p>The documentation is initially a snapshot of the
+<a href="http://xalan.apache.org/xalan-c/index.html">Apache Xalan-C/C++ website</a>
+at the time the product was released.</p>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Tue 2012-10-09</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/license.html b/docs/xalan/xalan-c/license.html
index 52cf18e..e27db6e 100644
--- a/docs/xalan/xalan-c/license.html
+++ b/docs/xalan/xalan-c/license.html
@@ -387,7 +387,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/overview.html b/docs/xalan/xalan-c/overview.html
index 4653841..2721d8c 100644
--- a/docs/xalan/xalan-c/overview.html
+++ b/docs/xalan/xalan-c/overview.html
@@ -378,7 +378,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/programming.html b/docs/xalan/xalan-c/programming.html
index b1792a1..8a16bf0 100644
--- a/docs/xalan/xalan-c/programming.html
+++ b/docs/xalan/xalan-c/programming.html
@@ -241,7 +241,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/readme.html b/docs/xalan/xalan-c/readme.html
index 71f5f4f..8b6f8d4 100644
--- a/docs/xalan/xalan-c/readme.html
+++ b/docs/xalan/xalan-c/readme.html
@@ -221,10 +221,14 @@
</p>
<h4>Version of Xerces-C++ to use</h4>
<p>Xalan-C++ Version 1.11 has been tested with Xerces-C++ version 3.1.1.</p>
-<p>For information about including the Xerces-C++ libraries on the path, see <a href="install.html#path">Setting up the system path</a>.</p>
+<p>For information about including the Xerces-C++ libraries on the path,
+ see <a href="install.html#path">Setting up the system path</a>.</p>
<p>
-<b>Important:</b> 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>
-<p>If you compile both Xalan-C++ and Xerces-C++ from distribution sources using the same platform and compiler, you will avoid most of the compatibility issues.</p>
+<b>Important:</b> 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>
+<p>If you compile both Xalan-C++ and Xerces-C++ from distribution sources using the same
+ platform and compiler, you will avoid most of the compatibility issues.</p>
<a name="to-do"></a>
<p align="right" size="2">
@@ -240,7 +244,8 @@
<li>Fix compiler and platform support issues</li>
<li>Add XPath2 support into Xalan-C++</li>
</ul>
- <p>Watch the <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a> for more information and for ideas about how you can get involved.
+ <p>Watch the <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a> for more information and for
+ ideas about how you can get involved.
</p>
@@ -824,17 +829,22 @@
<a href="#content">(top)</a>
</p>
<h4>Changes for Xalan-C++ version 1.11</h4>
-<p>This is a general bug fix release with added stability features.</p>
+<p>This is a general bug fix release with added stability features.
+ Many null pointer references have been fixed.</p>
<p>Major updates since version 1.10 include:</p>
<ul>
<li>Add support for Xerces-C 3.0 and newer</li>
<li>Drop support for Microsoft Studio (VC6)</li>
<li>Fix support issues for AIX 5.3</li>
<li>Fix support issues for Solaris 2.8</li>
+ <li>Fix support issues for Solaris 2.10</li>
<li>Fix support issues for GCC-4.3</li>
<li>Add support for Microsoft .NET 2008 (VC9) </li>
<li>Add support for Microsoft .NET 2010 (VC10)</li>
<li>Add number and nodeset types as top-level stylesheet parameters</li>
+ <li>Allow separation of compiler CFLAGS and CXXFLAGS for UNIX builds</li>
+ <li>Xalan-C documentation rewrite and reorganize</li>
+ <li>Parent Apache XML Project has been retired</li>
<li>
<a href="#bugfix11">Bugs fixed in this release</a>.</li>
</ul>
@@ -876,7 +886,7 @@
<a href="apiDocs/classXalanTransformer.html">XalanTransformer</a> in the <a href="apiDocs/index.html">
API Reference</a> section for more information.</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>
+ directory xalan\c\Projects\Win32\VC7.1.</li>
<li>Upgrade from Xerces-C 2.5 to Xerces-C 2.6. </li>
</ul>
@@ -892,13 +902,11 @@
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>
<li>Project files for supporting Microsoft Visual Studio .NET. Although a binary distribution for the Microsoft Visual Studio .NET
is not provided in this release, Visual Studio solution files are provided in the Windows source distribution for those who choose to build
- on this platform. Please see <a href="build_instruct.html#dotNet">"Step for doing a Windows Build with Visual Studio .NET"</a>
+ on this platform. Please see <a href="buildlibs.html#winbldenv">"Step for doing a Windows Build with Visual Studio .NET"</a>
for details.</li>
<li>Additional changes to Xerces Deprecated DOM support. This is another step towards phasing out the support for Xerces Deprecated DOM. Users
are encouraged to modify their applications to interface with the new Xerces DOM support. For more information on the effects of these
- changes to your build environment, please see <a href="#xercesdepdom">"Steps for doing a Build with Xerces Deprecated DOM Support"
- </a>
-</li>
+ changes to your build environment.</li>
<li>Implemented optimizations to significantly improve the throughput of the ICU-enabled "format-number" function.</li>
<li>Changes in the XML Serializer. The serializer will no longer put a newline after the xml header tag unless indent="yes".</li>
@@ -914,14 +922,13 @@
<li>Message Localization Support. This feature enables Xalan-C++ 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 Xalan-C++ message catalog that has been translated in
- their language of choice. For more information on how to exploit this feature, please see
- <a href="#locale">Steps for doing a Build with Message Localization Support</a>.</li>
+ their language of choice.</li>
<li>Build, packaging, and installation improvements. Changes to the Xalan-C++ makefiles now
allow for a more flexible build, packaging, and install process. Each step in a typical
build process can be invoked by specifying the appropriate target, for example to build the
executable, and/or samples, or install the build at user-specified location. For more
- information on building Xalan-C++, please see <a href="#unix">Steps for doing a Unix build
- </a>.</li>
+ information on building Xalan-C++, please see
+ <a href="buildlibs.html#unixbldenv">Steps for doing a Unix build</a>.</li>
<li>Deprecated DOM Support. The XercesBridge classes have been marked deprecated and moved
into an exclusive directory within the xalanc/XercesParserLiaison directory called
'Deprecated'. If your application is dependent on these classes to interface with the
@@ -962,7 +969,10 @@
<code>#include <xalanc/XPath/XObject.hpp></code>
<br />
<br />
- For Windows users, all project files have been modified to reflect this change. For UNIX users, please see <a href="#unix">Steps for doing a UNIX build</a> for migration considerations.</li>
+ For Windows users, all project files have been modified to reflect this change.
+ For UNIX users, please see
+ <a href="buildlibs.html#unixbldenv">Steps for doing a UNIX build</a>
+ for migration considerations.</li>
</ul>
@@ -984,8 +994,10 @@
<h4>Changes for Xalan-C++ version 1.4</h4>
<p>Major updates since version 1.3 include:</p>
<ul>
- <li>The Xalan-C++ distributions no longer include the Xerces-C++ headers and libraries. Accordingly, you must download the appropriate Xerces-C++ distribution (see <a href="getstarted.html#download">Downloading what you need</a>.</li>
- <li>64-bit build for HP-11; <a href="#64">untested 64-bit support</a> for Solaris and AIX.</li>
+ <li>The Xalan-C++ distributions no longer include the Xerces-C++ headers and libraries.
+ Accordingly, you must download the appropriate Xerces-C++ distribution
+ (see <a href="download.html">Downloading what you need</a>.</li>
+ <li>64-bit build for HP-11; untested 64-bit support for Solaris and AIX.</li>
<li>New Linux platform and compiler: Redhat 7.2 with gcc 3.1.</li>
<li>
<a href="http://www.stlport.org/">STLport</a> is no longer required on any of our supported platforms.</li>
@@ -1102,7 +1114,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/releasenotes.html b/docs/xalan/xalan-c/releasenotes.html
index 71f5f4f..78a5f7e 100644
--- a/docs/xalan/xalan-c/releasenotes.html
+++ b/docs/xalan/xalan-c/releasenotes.html
@@ -187,7 +187,10 @@
<li>Project files for supporting Microsoft Visual Studio .NET. Although a binary distribution for the Microsoft Visual Studio .NET
is not provided in this release, Visual Studio solution files are provided in the Windows source distribution for those who choose to build
on this platform. Please see <a href="#dotNet">"Step for doing a Windows Build with Visual Studio .NET"</a> for details.</li>
- <li>Additional changes to Xerces Deprecated DOM support. This is another step towards phasing out the support for Xerces Deprecated DOM. Users are encouraged to modify their applications to interface with the new Xerces DOM support. For more information on the effects of these changes to your build environment, please see <a href="#xercesdepdom">"Steps for doing a Build with Xerces Deprecated DOM Support"</a>
+ <li>Additional changes to Xerces Deprecated DOM support. This is another step towards phasing out the support for Xerces Deprecated DOM.
+ Users are encouraged to modify their applications to interface with the new Xerces DOM support.
+ For more information on the effects of these changes to your build environment, please see
+ <a href="#xercesdepdom">"Steps for doing a Build with Xerces Deprecated DOM Support"</a>
</li>
<li>Implemented optimizations to significantly improve the throughput of the ICU-enabled "format-number" function.</li>
@@ -221,10 +224,14 @@
</p>
<h4>Version of Xerces-C++ to use</h4>
<p>Xalan-C++ Version 1.11 has been tested with Xerces-C++ version 3.1.1.</p>
-<p>For information about including the Xerces-C++ libraries on the path, see <a href="install.html#path">Setting up the system path</a>.</p>
+<p>For information about including the Xerces-C++ libraries on the path,
+ see <a href="install.html#path">Setting up the system path</a>.</p>
<p>
-<b>Important:</b> 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>
-<p>If you compile both Xalan-C++ and Xerces-C++ from distribution sources using the same platform and compiler, you will avoid most of the compatibility issues.</p>
+<b>Important:</b> 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>
+<p>If you compile both Xalan-C++ and Xerces-C++ from distribution sources using the same
+ platform and compiler, you will avoid most of the compatibility issues.</p>
<a name="to-do"></a>
<p align="right" size="2">
@@ -240,7 +247,8 @@
<li>Fix compiler and platform support issues</li>
<li>Add XPath2 support into Xalan-C++</li>
</ul>
- <p>Watch the <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a> for more information and for ideas about how you can get involved.
+ <p>Watch the <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a> for more information and for
+ ideas about how you can get involved.
</p>
@@ -824,17 +832,22 @@
<a href="#content">(top)</a>
</p>
<h4>Changes for Xalan-C++ version 1.11</h4>
-<p>This is a general bug fix release with added stability features.</p>
+<p>This is a general bug fix release with added stability features.
+ Many null pointer references have been fixed.</p>
<p>Major updates since version 1.10 include:</p>
<ul>
<li>Add support for Xerces-C 3.0 and newer</li>
<li>Drop support for Microsoft Studio (VC6)</li>
<li>Fix support issues for AIX 5.3</li>
<li>Fix support issues for Solaris 2.8</li>
+ <li>Fix support issues for Solaris 2.10</li>
<li>Fix support issues for GCC-4.3</li>
<li>Add support for Microsoft .NET 2008 (VC9) </li>
<li>Add support for Microsoft .NET 2010 (VC10)</li>
<li>Add number and nodeset types as top-level stylesheet parameters</li>
+ <li>Allow separation of compiler CFLAGS and CXXFLAGS for UNIX builds</li>
+ <li>Xalan-C documentation rewrite and reorganize</li>
+ <li>Parent Apache XML Project has been retired</li>
<li>
<a href="#bugfix11">Bugs fixed in this release</a>.</li>
</ul>
@@ -876,7 +889,7 @@
<a href="apiDocs/classXalanTransformer.html">XalanTransformer</a> in the <a href="apiDocs/index.html">
API Reference</a> section for more information.</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>
+ directory xalan\c\Projects\Win32\VC7.1.</li>
<li>Upgrade from Xerces-C 2.5 to Xerces-C 2.6. </li>
</ul>
@@ -892,13 +905,11 @@
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>
<li>Project files for supporting Microsoft Visual Studio .NET. Although a binary distribution for the Microsoft Visual Studio .NET
is not provided in this release, Visual Studio solution files are provided in the Windows source distribution for those who choose to build
- on this platform. Please see <a href="build_instruct.html#dotNet">"Step for doing a Windows Build with Visual Studio .NET"</a>
+ on this platform. Please see <a href="buildlibs.html#winbldenv">"Step for doing a Windows Build with Visual Studio .NET"</a>
for details.</li>
<li>Additional changes to Xerces Deprecated DOM support. This is another step towards phasing out the support for Xerces Deprecated DOM. Users
are encouraged to modify their applications to interface with the new Xerces DOM support. For more information on the effects of these
- changes to your build environment, please see <a href="#xercesdepdom">"Steps for doing a Build with Xerces Deprecated DOM Support"
- </a>
-</li>
+ changes to your build environment.</li>
<li>Implemented optimizations to significantly improve the throughput of the ICU-enabled "format-number" function.</li>
<li>Changes in the XML Serializer. The serializer will no longer put a newline after the xml header tag unless indent="yes".</li>
@@ -914,14 +925,13 @@
<li>Message Localization Support. This feature enables Xalan-C++ 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 Xalan-C++ message catalog that has been translated in
- their language of choice. For more information on how to exploit this feature, please see
- <a href="#locale">Steps for doing a Build with Message Localization Support</a>.</li>
+ their language of choice.</li>
<li>Build, packaging, and installation improvements. Changes to the Xalan-C++ makefiles now
allow for a more flexible build, packaging, and install process. Each step in a typical
build process can be invoked by specifying the appropriate target, for example to build the
executable, and/or samples, or install the build at user-specified location. For more
- information on building Xalan-C++, please see <a href="#unix">Steps for doing a Unix build
- </a>.</li>
+ information on building Xalan-C++, please see
+ <a href="buildlibs.html#unixbldenv">Steps for doing a Unix build</a>.</li>
<li>Deprecated DOM Support. The XercesBridge classes have been marked deprecated and moved
into an exclusive directory within the xalanc/XercesParserLiaison directory called
'Deprecated'. If your application is dependent on these classes to interface with the
@@ -962,7 +972,10 @@
<code>#include <xalanc/XPath/XObject.hpp></code>
<br />
<br />
- For Windows users, all project files have been modified to reflect this change. For UNIX users, please see <a href="#unix">Steps for doing a UNIX build</a> for migration considerations.</li>
+ For Windows users, all project files have been modified to reflect this change.
+ For UNIX users, please see
+ <a href="buildlibs.html#unixbldenv">Steps for doing a UNIX build</a>
+ for migration considerations.</li>
</ul>
@@ -984,8 +997,10 @@
<h4>Changes for Xalan-C++ version 1.4</h4>
<p>Major updates since version 1.3 include:</p>
<ul>
- <li>The Xalan-C++ distributions no longer include the Xerces-C++ headers and libraries. Accordingly, you must download the appropriate Xerces-C++ distribution (see <a href="getstarted.html#download">Downloading what you need</a>.</li>
- <li>64-bit build for HP-11; <a href="#64">untested 64-bit support</a> for Solaris and AIX.</li>
+ <li>The Xalan-C++ distributions no longer include the Xerces-C++ headers and libraries.
+ Accordingly, you must download the appropriate Xerces-C++ distribution
+ (see <a href="download.html">Downloading what you need</a>.</li>
+ <li>64-bit build for HP-11; untested 64-bit support for Solaris and AIX.</li>
<li>New Linux platform and compiler: Redhat 7.2 with gcc 3.1.</li>
<li>
<a href="http://www.stlport.org/">STLport</a> is no longer required on any of our supported platforms.</li>
@@ -1102,7 +1117,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/resources.html b/docs/xalan/xalan-c/resources.html
index 387ddc9..ebd85a8 100644
--- a/docs/xalan/xalan-c/resources.html
+++ b/docs/xalan/xalan-c/resources.html
@@ -318,7 +318,7 @@
<br />
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/30/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/samples.html b/docs/xalan/xalan-c/samples.html
index 6e89dba..d57e1c5 100644
--- a/docs/xalan/xalan-c/samples.html
+++ b/docs/xalan/xalan-c/samples.html
@@ -879,7 +879,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/secureweb.html b/docs/xalan/xalan-c/secureweb.html
index 677b304..b43abf1 100644
--- a/docs/xalan/xalan-c/secureweb.html
+++ b/docs/xalan/xalan-c/secureweb.html
@@ -580,7 +580,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/09/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/usagepatterns.html b/docs/xalan/xalan-c/usagepatterns.html
index 419ac74..5e5ec1d 100644
--- a/docs/xalan/xalan-c/usagepatterns.html
+++ b/docs/xalan/xalan-c/usagepatterns.html
@@ -939,7 +939,7 @@
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/30/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
diff --git a/docs/xalan/xalan-c/whatsnew.html b/docs/xalan/xalan-c/whatsnew.html
index 16c6563..ccc026d 100644
--- a/docs/xalan/xalan-c/whatsnew.html
+++ b/docs/xalan/xalan-c/whatsnew.html
@@ -172,20 +172,15 @@
<b>Release notes for Xalan-C/C++ Version 1.11</b>
</p>
<p>This is primarily a bug-fix release of version 1.10. Support for number and
-nodeset types for stylesheet top-level parameters has been added. Xerces-C/C++
+nodeset types for stylesheet top-level parameters have been added. Xerces-C/C++
versions 3.0 and newer are now supported. Xerces-C/C++ Version 3.1.1 is the
preferred stable release.
</p>
-<p>At present, the Xalan-C/C++ Version 1.11 has no binary releases.
-When building Xalan-C/C++ from sources,
-you should use the same platform that was used to
-compile the companion Xerces-C/C++ library.
-</p>
-<p>Binary package releases for Microsoft Windows are being planned.
-</p>
-<p>If you are able to successfully create a new binary package and wish it
-to be included, then we welcome your participation on the
-<a href="mailto:dev@xalan.apache.org">xalan-dev</a> mail list.
+<p>There are few binary releases for Xalan-C/C++. The current binary releases
+are primarily for Windows platforms. If you are able to successfully create a
+new binary package and wish it to be included, then we welcome your participation
+on the <a href="mailto:dev@xalan.apache.org">xalan-dev</a> mail list.
+You may also wish to check our <a href="download.html">download</a> page.
</p>
<p>Xalan-C/C++ no longer supports Microsoft Studio (VC6). The Microsoft Visual
Studio .NET platforms (2003, 2005, 2008, and 2010) are supported. This equates
@@ -223,17 +218,22 @@
<a href="#content">(top)</a>
</p>
<h4>Changes for Xalan-C++ version 1.11</h4>
-<p>This is a general bug fix release with added stability features.</p>
+<p>This is a general bug fix release with added stability features.
+ Many null pointer references have been fixed.</p>
<p>Major updates since version 1.10 include:</p>
<ul>
<li>Add support for Xerces-C 3.0 and newer</li>
<li>Drop support for Microsoft Studio (VC6)</li>
<li>Fix support issues for AIX 5.3</li>
<li>Fix support issues for Solaris 2.8</li>
+ <li>Fix support issues for Solaris 2.10</li>
<li>Fix support issues for GCC-4.3</li>
<li>Add support for Microsoft .NET 2008 (VC9) </li>
<li>Add support for Microsoft .NET 2010 (VC10)</li>
<li>Add number and nodeset types as top-level stylesheet parameters</li>
+ <li>Allow separation of compiler CFLAGS and CXXFLAGS for UNIX builds</li>
+ <li>Xalan-C documentation rewrite and reorganize</li>
+ <li>Parent Apache XML Project has been retired</li>
<li>
<a href="#bugfix11">Bugs fixed in this release</a>.</li>
</ul>
@@ -508,12 +508,17 @@
<h3>Bug Fixes in Release 1.11</h3>
<p>The bugs fixed in Xalan-C++ Version 1.11 include:</p>
<ul>
-<li>XALANC-723 Add Top-Level parameter support for XalanCAPI and UseStylesheetParams sample</li>
+<li>XALANC-734: Allow runConfigure CFLAGS and CXXFLAGS to inherit environment</li>
+<li>XALANC-732: Fix makefile errors for AIX builds</li>
+<li>XALANC-730: Fixed XalanTransformer memory leaks</li>
+<li>XALANC-723: Add Top-Level parameter support for XalanCAPI and UseStylesheetParams samples</li>
+<li>XALANC-723: The XalanTransformer Top-Level parameters now include nodeset and number types</li>
<li>XALANC-721: Upgrade support for MS VS 2010 (VC10)</li>
<li>XALANC-719: Xerces Parser Liaison - errors on elements with no attributes</li>
<li>XALANC-716: incorrect buffer-size calculation in XalanUTF16Writer.hpp</li>
<li>XALANC-715: NULL pointer access crash</li>
<li>XALANC-713: Build Xalan-C/C++ API Reference Manual using Doxygen 1.7 or newer</li>
+<li>XALANC-712: Rewrite of Xalan-C++ V1.11 User Guide Web Pages</li>
<li>XALANC-710: MS-Studio 2008 Debug Build sends Xalan-C_1D.lib to wrong directory</li>
<li>XALANC-709: Doxygen bug in XalanQName.hpp</li>
<li>XALANC-708: Including XalanCAPI.hpp does not import Xerces typedef XMLch</li>
@@ -707,14 +712,16 @@
<li>Add more EXSLT extension functions</li>
<li>Add the EXSLT document extension function</li>
<li>Add support for user-defined extension modules</li>
-<li>Add support for node-set to be declared as top-level XSLT parameter</li>
+<li>Retire runConfigure script, use GNU AutoTools for platform maintenance</li>
+<li>Add number and nodeset top-level parameters to the Xalan command-line</li>
+<li>Add noNamespace file schema capability to the Xalan command-line</li>
</ul>
<p align="right" size="2">
<a href="#content">(top)</a>
</p>
</div>
-<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 09/30/2012</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Sun 2012-10-07</div>
</div>
</body>
</html>
