You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by sh...@apache.org on 2012/11/19 00:53:43 UTC
svn commit: r1411029 [2/2] - in /xalan/c/branches/GSoC-2012: ./
Projects/Win32/VC10/ Projects/Win32/VC10/AllInOne/ scripts/
src/xalanc/PlatformSupport/ xdocs/ xdocs/sources/
xdocs/sources/xalan-graphic/ xdocs/sources/xalan/
xdocs/sources/xslt-resources/
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/buildlibs.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/buildlibs.xml?rev=1411029&r1=1411028&r2=1411029&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/buildlibs.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/buildlibs.xml Sun Nov 18 23:53:39 2012
@@ -20,34 +20,124 @@
<s1 title="Building Xalan-C/C++">
<ul>
+<li><link anchor="SourceTools">The Distribution Source Tools</link></li>
+ <ul>
+ <li><link anchor="WinBldScripts">Prepare Windows Build Scripts"</link></li>
+ <li><link anchor="PrepUnixBld">Prepare Unix Build Scripts</link></li>
+ </ul>
<li><link anchor="winbldenv">Windows Build Environment</link></li>
-<ul>
-<li><link anchor="winbld">Windows Basic Build Instruction</link></li>
-<li><link anchor="winbldcmd">Sample Windows Build Command File</link></li>
-<li><link anchor="winbldinst">Installing the Xalan Library on Windows</link></li>
-</ul>
+ <ul>
+ <li><link anchor="winbld">Windows Basic Build Instruction</link></li>
+ <li><link anchor="winbldcmd">Sample Windows Build Command File</link></li>
+ <li><link anchor="winbldinst">Installing the Xalan Library on Windows</link></li>
+ </ul>
<li><link anchor="unixbldenv">UNIX Build Environment</link></li>
-<ul>
-<li><link anchor="unixlibpath">Finding Runtime Libraries</link></li>
-<li><link anchor="unixbldxalan">Building the Xalan-C/C++ XSLT Libraries for UNIX</link></li>
-</ul>
+ <ul>
+ <li><link anchor="unixlibpath">Finding Runtime Libraries</link></li>
+ <li><link anchor="unixbldxalan">Building the Xalan-C/C++ XSLT Libraries for UNIX</link></li>
+ </ul>
<li><link anchor="unixcompileref">Reference on Unix Platforms and C++ Compilers</link></li>
<li><link anchor="xercesmodules">Xerces-C/C++ Transcoders and Plug-in Modules</link></li>
<!-- <li><link anchor=""></link></li> -->
</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>
-<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>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>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>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 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
+ <jump href="http://xerces.apache.org/xerces-c">http://xerces.apache.org/xerces-c</jump> web site.
+</p>
+
+<anchor name="SourceTools"/>
+<s2 title="The Distribution Source Tools">
+<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><em><code>(src)/scripts/xalan-ms-scripts.zip</code></em> For Windows Packages</li>
+<li><em><code>(src)/scripts/xalan-unix-scripts.tar</code></em> For Unix/Linux Packages</li>
+</ul>
+
+<p>The following discussions in this chapter describe the rules by which these
+ scripts were written.</p>
+<anchor name="WinBldScripts"/>
+<s3 title="Prepare Windows Build Scripts">
+<p>I use the <code><em>C:\Apache\xalan-builds\</em></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><em>xalan-ms-scripts.zip</em></code> into your package building directory.</li>
+<li>Copy the Xerces-C sources into a builds subdirectory <code><em>xerces-src-31</em></code>.</li>
+<li>Copy the Xalan-C sources into a builds subdirectory <code><em>xalan-src-11</em></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><em>xerces-build-31-*.bat</em></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><em>xerces-inst-31-*.bat</em></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><em>xalan-build-11-31-*.bat</em></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><em>xalan-inst-11-31-*.bat</em></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>
+</s3>
+<anchor name="PrepUnixBld"/>
+<s3 title="Prepare Unix Build Scripts">
+<p>I use my <code><em>$HOME</em></code> directory as the path into which
+ <code><em>xalan-unix-scripts.tar</em></code> is extracted.
+ I create subdirectory <code><em>xerces-src</em></code> for the Xerces-C sources and
+ another subdirectory <code><em>xalan-src</em></code> for the Xalan-C sources.
+ I then create separate directories into which the actual build process
+ takes place.</p>
+<p>Directory <code><em>Xerces-Build</em></code> is where I make the Xerces-C binaries.</p>
+<p>Directory <code><em>Xalan-Build</em></code> is where I make the Xalan-C binaries.</p>
+<p>The following scripts are used to make and install the <em>release</em> build
+ of binary products to the <code><em>/opt/apache/</em></code> target directory path.
+ Connect to the appropriate build directory and execute the appropriate script.
</p>
-<p>You can get more information on the Xerces-C/C++ distributions at the <jump href="http://xml.apache.org/xerces-c">http://xml.apache.org/xerces-c</jump> web site.
+<ul>
+ <li>xerces-build.sh</li>
+ <li>xalan-build.sh</li>
+</ul>
+<p>The following scripts are used to make and install the <em>debug</em> build
+ of binary products to the <code><em>/opt/apache/debug/</em></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>
+</s3>
+</s2>
<anchor name="winbldenv"/>
<s2 title="Windows Build Environment">
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/download.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/download.xml?rev=1411029&r1=1411028&r2=1411029&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/download.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/download.xml Sun Nov 18 23:53:39 2012
@@ -18,47 +18,49 @@
-->
<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd">
<s1 title="Downloading &xslt4c;">
-<anchor name="download"/>
-<p>This section is being rewritten for Xalan-C/C++ Version 1.11. You
-can find the old
-<jump href="../old/xalan-c">Version 1.10</jump> here.
-</p>
-
-<p>We are providing a source package, a documentation package, and
-some compiled binary packages.
-</p>
-
-<p>The binary packages are currently for Windows systems. We can
-use your help <jump href="buildlibs.html">creating binary packages</jump> for
-UNIX and Linux systems.
-</p>
-
-<p><em>THIS IS STILL A PRE-RELEASE PRODUCT</em></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/>
-<jump href="http://svn.apache.org/repos/asf/xalan/c/trunk">
-http://svn.apache.org/repos/asf/xalan/c/trunk</jump>
-</p>
+<ul>
+ <li><link anchor="DownloadWhat">Downloading What You Need</link></li>
+ <li><link anchor="DownloadNotes">Downloading Notes</link></li>
+<!-- <li><link anchor="SelectMirror">Select Another Mirror</link></li> -->
+ <li><link anchor="SourcePkgs">Source Packages</link></li>
+ <li><link anchor="DocPkgs">Documentation Packages</link></li>
+ <li><link anchor="BinaryPkgs">Binary Packages</link></li>
+ <li><link anchor="VerifyPkgs">Verify Downloaded Packages</link></li>
+ <li><link anchor="PlatformComp">Platform Compatibility</link></li>
+</ul>
-<s2 title="Downloading what you need">
+<anchor name="DownloadWhat"/>
+<s2 title="Downloading What You Need">
-<p>The Xalan-C/C++ library requires the
-<jump href="http://www.apache.org/dyn/closer.cgi/xerces/c">Xerces-C/C++ XML</jump> 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><em>Download Xalan-C/C++ Distributions from Apache Mirrors</em></p>
+<table>
+ <tr><td><jump href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c">
+ The Xalan-C/C++ Distribution Tree</jump></td></tr>
+ <tr><td><jump href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/sources">
+ The Xalan-C/C++ Source Packages</jump></td></tr>
+ <tr><td><jump href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/docs">
+ The Xalan-C/C++ Documentation Packages</jump></td></tr>
+ <tr><td><jump href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/binaries">
+ The Xalan-C/C++ Binary Packages</jump></td></tr>
+</table>
+
+<p><em>Download Xerces-C/C++ XML Parser Library</em></p>
+<p>The Xalan-C/C++ 1.11 library requires the
+<jump href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xerces/c">Xerces-C/C++ XML</jump>
+Parser 3.0 or newer, version 3.1.1 is preferred.
</p>
+<p><em>Our Xalan Packages</em></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
@@ -68,64 +70,204 @@ We have not tried building the API Refer
A usable API Reference is included with the documentation package.
</p>
-<s3 title="Source Packages">
-<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>
+</s2>
+<anchor name="DownloadNotes"/>
+<s2 title="Downloading Notes">
+
+<p>Apache package 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>
+
+<note>You must <link anchor="VerifyPkgs">verify the integrity</link> of the downloaded files
+using signatures downloaded from the Apache master distribution directory.</note>
+
+<p>Access to the latest (and possibly unstable) source can be accessed via
+<jump href="http://svn.apache.org/repos/asf/xalan/c/trunk">SVN</jump></p>
+
+<p>Archives of old Xalan-C/C++ releases can be found at the
+<jump href="http:archive.apache.org/dist/xalan/xalan-c">Apache Xalan Archives</jump>
+and the
+<jump href="http:archive.apache.org/dist/xml/xalan-c">Old Apache XML Archives</jump>.</p>
+
+<p>Archives of old Xerces-C/C++ parser distributions can be found at the
+<jump href="http:archive.apache.org/dist/xerces/c">Apache Xerces Archives</jump>
+and the
+<jump href="http:archive.apache.org/dist/xml/xalan-c">Old Apache XML Archives</jump>.</p>
+
+
+<!--
+ Special use of < > are required here to get the <form>,,,</form> to pass through
+ StyleBook stylesheet transformation. (I hope to add the <form> capability to StyleBook.)
+ You should then edit the product html, converting the form for use as a cgi template.
+ -->
+<!-- Include the "altmirror" file when ready for this capability
+ &altmirror;
+-->
+<anchor name="SourcePkgs"/>
+<s3 title="Source Packages">
+<p><em>Xalan-C/C++ <jump href="http://www.apache.org/dist/xalan/xalan-c/KEYS">KEYS</jump></em></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
+ <jump href="http:///www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/sources">
+ Apache Mirrors</jump>.</p>
+<p>You should <link anchor="VerifyPkgs">verify</link> your packages against
+ the trusted signatures posted on the Apache master distribution site</p>
</s3>
+<anchor name="DocPkgs"/>
<s3 title="Documentation Packages">
-<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++
+<link anchor="SourcePkgs">source distributions</link> 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 <em>html-full</em> is a very large package (355+ MB). It contains the
+ interactive graphics images that map the include file relationships and
+ class relationships. The <em>html-nograf</em> (42 MB) just contains tabular
+ relationships without the large volume of generated graphics.
</p>
-
+<p><em>Xalan-C/C++ <jump href="http://www.apache.org/dist/xalan/xalan-c/KEYS">KEYS</jump></em></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
+ <jump href="http:///www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/docs">
+ Apache Mirrors</jump>.</p>
+<p>You should <link anchor="VerifyPkgs">verify</link> your packages against
+ the trusted signatures posted on the Apache master distribution site</p>
</s3>
+<anchor name="BinaryPkgs"/>
<s3 title="Binary Packages">
<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.
-</p>
-
-<p>The following binary packages are being prepared for distribution.</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>
+platforms. The Xalan-C/C++ <link anchor="DocPkgs">documentation</link>
+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 <em>xalan_combined</em> have compiled
+libraries for both Xalan-C/C++ and Xerces-C/C++. All binary
+packages include the <em>Xalan</em> or <em>xalan.exe</em>
+command line styleshet transformation processor.
+</p>
+
+<note>The development cycles for Xerces-C/C++ and Xalan-C/C++ are
+separately managed. There is no synchronization of product distribution.</note>
+
+<p><em>Windows Packages - 32 BIT</em></p>
+<ul>
+ <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_comb-1.11-x86-windows-vc71.zip for MS VS 2003</li>
+ <li>xalan_comb-1.11-x86-windows-vc8.zip for MS VS 2005 </li>
+ <li>xalan_comb-1.11-x86-windows-vc9.zip for MS VS 2008</li>
+ <li>xalan_comb-1.11-x86-windows-vc10.zip for MS VS 2010</li>
+</ul>
+<p><em>Windows Packages - 64 BIT</em></p>
+<ul>
+ <li>xalan_c-1.11-amd64-windows-vc8.zip for MS VS 2005</li>
+ <li>xalan_c-1.11-amd64-windows-vc9.zip for MS VS 2008</li>
+ <li>xalan_c-1.11-amd64-windows-vc10.zip for MS VS 2010</li>
+</ul>
+<p>Combined with Xerces Parser</p>
+<ul>
+ <li>xalan_comb-1.11-amd64-windows-vc8.zip for MS VS 2005</li>
+ <li>xalan_comb-1.11-amd64-windows-vc9.zip for MS VS 2008</li>
+ <li>xalan_comb-1.11-amd64-windows-vc10.zip for MS VS 2010</li>
</ul>
+<p><em>BSD Packages - 64 BIT</em></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><em>Linux Packages</em></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
+ <jump href="http:///www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/binaries">
+ Apache Mirrors</jump>.</p>
+<p>You should <link anchor="VerifyPkgs">verify</link> your packages against
+ the trusted signatures posted on the Apache master distribution site</p>
+</s3>
+</s2>
+<anchor name="VerifyPkgs"/>
+<s2 title="Verify The Integrity of the Files">
+
+<p>It is essential that you verify the integrity of the downloaded
+ files using the PGP or MD5 signatures. You should only download the
+ <jump href="http://www.apache.org/dist/xalan/xalan-c/KEYS">KEYS</jump>
+ 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><jump href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/sources">
+ Apache Mirror Xalan-C Sources</jump></li>
+ <li><jump href="http://www.apache.org/dist/xalan/xalan-c/sources">
+ Apache Master Xalan-C Sources - for Signature Files</jump></li>
+ <li><jump href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/docs">
+ Apache Mirror Xalan-C Documentation</jump></li>
+ <li><jump href="http://www.apache.org/dist/xalan/xalan-c/docs">
+ Apache Master Xalan-C Documentation - for Signature Files</jump></li>
+ <li><jump href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/binaries">
+ Apache Mirror Xalan-C Binary Packages</jump></li>
+ <li><jump href="http://www.apache.org/dist/xalan/xalan-c/binaries">
+ Apache Master Xalan-C Binary Packages - for Signature Files</jump></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>
+<source>
+ % pgpk -a KEYS
+ % pgpv <archive-name>.tar.gz.asc
+</source>
+<em>or</em>
+<source>
+ % pgp -ka KEYS
+ % pgp <archive-name>.tar.gz.asc
+</source>
+<em>or</em>
+<source>
+ % gpg --import KEYS
+ % gpg --verify <archive-name>.tar.gz.asc
+</source>
+<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
+<jump href="http://www.gnu.org/directory/text/wordproc/textutils.html">GNU Textutils</jump>.
+ Windows users can get binary md5 programs from
+<jump href="http://www.fourmilab.ch/md5/">here</jump>,
+<jump href="http://www.pc-tools.net/win32/freeware/console/">here</jump>, or
+<jump href="http://www.slavasoft.com/fsum/">here</jump>.</p>
+</s2>
+<anchor name="PlatformComp"/>
+<s2 title="Platform Compatibility">
<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
-<jump href="mailto:dev@xalan.apache.org">xalan-dev</jump> mailing list.
-</p>
-</s3>
-<!-- PLATFORM COMPATIBILITY TABLE GOES HERE
--->
-<s3 title="Platform Compatibility">
+<jump href="mailto:dev@xalan.apache.org">xalan-dev</jump> mailing list.</p>
+
<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>
@@ -192,19 +334,23 @@ a build of the Xerces-C/C++ XML Parser l
Use of Xalan and Xerces libraries compiled with different versions
of compilers may cause problems</p>
-<note>Use GNU tar to untar the Solaris distribution file; see <link idref="faq" anchor="faq-11">A tar checksum error on Solaris
- </link>.
+<note>Use GNU tar to untar the Solaris distribution file; see
+ <link idref="faq" anchor="faq-11">A tar checksum error on Solaris</link>.
</note>
-<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 <resource-ref idref="icu"/>; see <link idref="usagepatterns" anchor="icu">Using the ICU</link>,</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 <resource-ref idref="icu"/>; see
+ <link idref="usagepatterns" anchor="icu">Using the ICU</link>.
+</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>
-<note>To access previous releases of &xslt4c;, visit the <jump href="http://archive.apache.org/dist/xml/xalan-c/">Xalan-C archive
- directory</jump>.
+<note>To access previous releases of &xslt4c;, visit the
+ <jump href="http://archive.apache.org/dist/xml/xalan-c/">Xalan-C archive directory</jump>
</note>
-</s3>
</s2>
</s1>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/faq.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/faq.xml?rev=1411029&r1=1411028&r2=1411029&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/faq.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/faq.xml Sun Nov 18 23:53:39 2012
@@ -270,10 +270,16 @@
<faq title="Problems Using Sun's Forte/Workshop Compiler with code containing std::istrstream">
<q>Why won't XSLTInputSource work with std::istrstream on Sun Solaris using Forte/Sun Workshop compiler?</q>
-<a><p>There is a bug in Sun's C++ standard library implementation; see
- <jump href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14176">this bug</jump>. The short answer is that you need to
- get a patch. The bug report includes the code for a simple program which you can use to see if your environment has the bug.
- There is also a link to the patch.</p>
+<!-- first answer -->
+<a><p>There is a bug in Sun's C++ standard library implementation
+ for the Forte/Workshop compiler.
+ The short answer is that you need to get a patch.
+ The bugzilla subsystem for Xalan issue tracking is no longer available. The ticket recorded
+ here included a patch.</p>
+</a>
+<!-- second answer -->
+<a><p>The issue is resolved if you use the SunStudio platform for your code development.
+ The Solaris SunStudio is now available from Oracle.</p>
</a>
</faq>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/history.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/history.xml?rev=1411029&r1=1411028&r2=1411029&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/history.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/history.xml Sun Nov 18 23:53:39 2012
@@ -17,17 +17,22 @@
-->
<s3 title="Changes for &xslt4c; version 1.11">
-<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><link anchor="bugfix11">Bugs fixed in this release</link>.</li>
</ul>
</s3>
@@ -62,7 +67,7 @@
<jump href="apiDocs/classXalanTransformer.html">XalanTransformer</jump> in the <jump href="apiDocs/index.html">
API Reference</jump> 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>
</s3>
@@ -75,14 +80,13 @@
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 <link idref="build_instruct" anchor="dotNet">"Step for doing a Windows Build with Visual Studio .NET"</link>
+ on this platform. Please see <link idref="buildlibs" anchor="winbldenv">"Step for doing a Windows Build with Visual Studio .NET"</link>
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 <link anchor="xercesdepdom">"Steps for doing a Build with Xerces Deprecated DOM Support"
- </link></li>
+ changes to your build environment.</li>
<!--
- <li>Porting of conf utility to the UNIX platform. The conf utility is a test harness designed to run the conformance tests located under the xml-xalan/test/tests directory. After the tests have been run, a results report is generated in HTML format for easy viewing. For more information on how to use this tool, please see <link idref="commandline" anchor="confexe">"Using the command line utility"</link>.</li>
+ <li>Porting of conf utility to the UNIX platform. The conf utility is a test harness designed to run the conformance tests located under the xalan/test/tests directory. After the tests have been run, a results report is generated in HTML format for easy viewing. For more information on how to use this tool, please see <link idref="commandline" anchor="confexe">"Using the command line utility"</link>.</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>
@@ -98,14 +102,13 @@
<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
- their language of choice. For more information on how to exploit this feature, please see
- <link anchor="locale">Steps for doing a Build with Message Localization Support</link>.</li>
+ their language of choice.</li>
<li>Build, packaging, and installation improvements. Changes to the &xslt4c; 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 &xslt4c;, please see <link anchor="unix">Steps for doing a Unix build
- </link>.</li>
+ information on building &xslt4c;, please see
+ <link idref="buildlibs" anchor="unixbldenv">Steps for doing a Unix build</link>.</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
@@ -130,7 +133,10 @@
<code>#include <XPath/XObject.hpp></code><br/><br/>
will need to be changed to <br/><br/>
<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 <link anchor="unix">Steps for doing a UNIX build</link> for migration considerations.</li>
+ For Windows users, all project files have been modified to reflect this change.
+ For UNIX users, please see
+ <link idref="buildlibs" anchor="unixbldenv">Steps for doing a UNIX build</link>
+ for migration considerations.</li>
</ul>
</s3>
@@ -146,8 +152,10 @@
<s3 title="Changes for &xslt4c; version 1.4">
<p>Major updates since version 1.3 include:</p>
<ul>
- <li>The &xslt4c; distributions no longer include the &xml4c; headers and libraries. Accordingly, you must download the appropriate &xml4c; distribution (see <link idref="getstarted" anchor="download">Downloading what you need</link>.</li>
- <li>64-bit build for HP-11; <link anchor="64">untested 64-bit support</link> for Solaris and AIX.</li>
+ <li>The &xslt4c; distributions no longer include the &xml4c; headers and libraries.
+ Accordingly, you must download the appropriate &xml4c; distribution
+ (see <link idref="download">Downloading what you need</link>.</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><resource-ref idref="stlport"/> is no longer required on any of our supported platforms.</li>
<li><link idref="extensionslib" anchor="exslt">Alpha support for a number of EXSLT functions</link>.</li>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/index.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/index.xml?rev=1411029&r1=1411028&r2=1411029&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/index.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/index.xml Sun Nov 18 23:53:39 2012
@@ -98,17 +98,17 @@ Some lists require a subscription in ord
<p>The <jump href="mailto:dev@xalan.apache.org">xalan-dev</jump> mailing list
is used to communicate product development issues with the software development team.
The xalan-dev messages are
-<jump href="http://mail-archives.apache.org/mod_mbox/xml-xalan-dev">archived here</jump>
+<jump href="http://mail-archives.apache.org/mod_mbox/xalan-dev">archived here</jump>
and on <jump href="http://marc.info/?l=xalan-dev">Marc.info</jump>.
</p>
<p>The <jump href="mailto:c-users@xalan.apache.org">xalan-c-users</jump> mailing list
is used to discuss issues regarding the use of the Xalan-C/C++ software and libraries.
The xalan-c-users messages are
-<jump href="http://mail-archives.apache.org/mod_mbox/xml-xalan-c-users">archived here</jump>
+<jump href="http://mail-archives.apache.org/mod_mbox/xalan-c-users">archived here</jump>
and on <jump href="http://marc.info/?l=xalan-c-users">Marc.info</jump>.
</p>
-<p>The subversion repository changes are logged on the xalan-cvs mailing list and are
-<jump href="http://mail-archives.apache.org/mod_mbox/xml-xalan-cvs">archived here</jump>
+<p>The subversion repository changes are logged on the xalan-commits mailing list and are
+<jump href="http://mail-archives.apache.org/mod_mbox/xalan-commits">archived here</jump>
and on <jump href="http://marc.info/?l=xalan-cvs">Marc.info</jump>.
</p>
<p>You can review the project sources and change history in the subversion repository at
@@ -291,9 +291,9 @@ and let us know of your building issues.
</p>
<table>
<tr><td>Xalan-C Version 1.10</td><td><jump
-href="http://www.apache.org/dyn/closer.cgi/xml/xalan-c/">Xalan Package Downloads</jump></td></tr>
+href="http://archive.apache.org/dist/xml/xalan-c/">Xalan Package Downloads</jump></td></tr>
<tr><td>Xerces-C Version 2.7</td><td><jump
-href="http://www.apache.org/dyn/closer.cgi/xml/xerces-c/">Xerces Package Downloads</jump></td></tr>
+href="http://archive.apache.org/dist/xml/xerces-c/">Xerces Package Downloads</jump></td></tr>
</table>
</s2>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/install.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/install.xml?rev=1411029&r1=1411028&r2=1411029&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/install.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/install.xml Sun Nov 18 23:53:39 2012
@@ -18,173 +18,218 @@
* limitations under the License.
-->
<s1 title="Installing &xslt4c;">
+<!--
+File: Xalan-Install-Chapter.rtf
+-->
<ul>
- <li><link anchor="SourcePkgs">Install Source Packages</link></li>
- <li><link anchor="BinaryPkgs">Install Binary Packages</link></li>
- <ul>
- <li><link anchor="InsWin">Install Windows Packages</link></li>
- <li><link anchor="InsUnx">InstallUNIX Packages</link></li>
- <li><link anchor="InsPkgs">Other Packages</link></li>
- </ul>
- <li><link anchor="XalanDocPkg">Install Documentation Packages</link></li>
+<li><link anchor="InstSrcPkgs">Install Source Packages</link></li>
+<li><link anchor="InstBinPkgs">Install Binary Packages</link></li>
<ul>
- <li><link href="DocWebPkg">Xalan-C User Guide</link></li>
- <li><link href="DocApiPkg">Xalan-C API Reference</link></li>
+ <li><link anchor="InstUnixBinPkgs">Install UNIX Binary Packages</link></li>
+ <ul>
+ <li><link anchor="ConfigUnixSys">Configure UNIX and Linux Systems</link></li>
+ </ul>
+ <li><link anchor="InstWinBinPkgs">Install Windows Binary Packages</link></li>
+ <ul>
+ <li><link anchor="ConfWinPath">Configure Windows PATH</link></li>
+ </ul>
</ul>
+<li><link anchor="InstDocPkgs">Install Documentation Package</link></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>
-
-<anchor name="SourcePkgs"/>
+<anchor name="InstSrcPkgs"/>
<s2 title="Install Source Packages">
-<p>We have no package managers for source packages. You just extract
- the contents of the distribution <ref>zip</ref> file or <ref>tar</ref> 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
- <link idref="builddocs" anchor="buildweb">User Guide</link>
- from sources requires a working Xalan command line program.
-</p>
-<p>Building the interactive
- <link idref="builddocs" anchor="buildapi">API Reference</link>
- 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.
- <link idref="buildlibs" anchor="unixbldenv">UNIX and Linux builds</link>
- are automatically targeted to an install destination.
- <link idref="buildlibs" anchor="winbldinst">Installing a Windows build</link>
- 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 <em>zip</em> or <em>tar</em> 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><em>xalan-src</em></code>.
+The Xerces-C sources are expected to be found in a directory named <code><em>xerces-src</em></code>.</p>
+
+<p>The supplemental package building scripts for Windows look for the Xalan-C
+sources to be found in a directory named <code><em>xalan-src-11</em></code>
+and the Xerces-C sources to be found in a directory named <code><em>xerces-src-31</em></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>
</s2>
-<anchor name="BinaryPkgs"/>
+<anchor name="InstBinPkgs"/>
<s2 title="Install Binary Packages">
-<p>The binary packages distributed by <ref>zip</ref> files
- and <ref>tar</ref> 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>
-
-<anchor name="InsWin"/>
-<s3 title="Install Windows Packages">
-<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.
-</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>
-<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>
-</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>
-<source>set PATH=%PATH%;{target}\bin</source>
+<p>The binary packages distributed by <em>zip</em> and <em>tar</em> 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>
+
+<anchor name="InstUnixBinPkgs"/>
+<s3 title="Install UNIX Binary Packages">
+
+<p>Binary packages for Linux and UNIX systems only distribute a <em>release</em> 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>
+<tr><td>./bin/</td><td>Contains the Xalan.exe command line and DLLs</td></tr>
+<tr><td>./lib/</td><td>Contains the linker libraries</td></tr>
+<tr><td>./include/xalanc/</td><td>Contains the Xalan-C header files</td></tr>
+<tr><td>./doc/xalanc-1.11/</td><td>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>
+
+<anchor name="ConfigUnixSys"/>
+<s4 title="Configure UNIX and Linux Systems">
+
+<p>The Xalan command line executable should be in a directory
+accessible by the PATH environment.</p>
+
+<p>The lib directories containing the <code><em>libxalan-c.so</em></code> and
+<code><em>libxerces-c.so</em></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>
+<tr><th>Operating System</th><th>Library Path Environment</th></tr>
+<tr><td>Solaris and Linux</td><td>LD_LIBRARY_PATH</td></tr>
+<tr><td>BSD/GNU</td><td>LD_LIBRARY_PATH</td></tr>
+<tr><td>HP-UX</td><td>SHLIB_PATH</td></tr>
+<tr><td>AIX and BSD</td><td>LIBPATH</td></tr>
+<tr><td>MacOSX</td><td>DYLD_LIBRARY_PATH</td></tr>
+<tr><td>Cygwin and MinGW</td><td>PATH</td></tr>
+</table>
+
+<p>The library search path order is significant.
+In many cases, the <code><em>/usr/lib</em></code>, <code><em>/lib</em></code>,
+and <code><em>/usr/local/lib</em></code> paths are already cached
+in <code><em>/etc/ld.so.cache</em></code> or included by <code><em>/etc/ld.so.conf</em></code>.</p>
+
+</s4>
</s3>
-<anchor name="InsUnx"/>
-<s3 title="Install UNIX Packages">
- <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
- <link idref="buildlibs" anchor="unixlibpath">UNIX Runtime</link> configuration.
-</p>
-</s3>
-<anchor name="InsPkgs"/>
-<s3 title="Install Other Packages">
-<p>These packages are usually installed and configured by a package manager.
- You should refer to the documentation provided by the package maintainer.
-</p>
+<anchor name="InstWinBinPkgs"/>
+<s3 title="Install Windows Binary Packages">
+
+<p>Binary packages for Windows systems include a directory name
+related to the Windows Studio platform used to build the product.
+The <code>{<em>bin</em>, <em>lib</em>, <em>include</em>, <em>doc</em>}</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>
+<tr><td>XALANCPKG-11-31-VC71</td><td>for Visual Studio 2003 (Win32)</td></tr>
+<tr><td>XALANCPKG-11-31-VC80</td><td>for Visual Studio 2005 (Win32)</td></tr>
+<tr><td>XALANCPKG-11-31-VC90</td><td>for Visual Studio 2008 (Win32)</td></tr>
+<tr><td>XALANCPKG-11-31-VC100</td><td>for Visual Studio 2010 (Win32)</td></tr>
+<tr><td>XALANCPKG-11-31-X64-VC80</td><td>for Visual Studio 2005 (amd64)</td></tr>
+<tr><td>XALANCPKG-11-31-X64-VC90</td><td>for Visual Studio 2008 (amd64)</td></tr>
+<tr><td>XALANCPKG-11-31-X64-VC100</td><td>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>
+<tr><td>XERCESCPKG-31-VC71</td><td>for Visual Studio 2003 (Win32)</td></tr>
+<tr><td>XERCESCPKG-31-VC80</td><td>for Visual Studio 2005 (Win32)</td></tr>
+<tr><td>XERCESCPKG-31-VC90</td><td>for Visual Studio 2008 (Win32)</td></tr>
+<tr><td>XERCESCPKG-31-VC100</td><td>for Visual Studio 2010 (Win32)</td></tr>
+<tr><td>XERCESCPKG-31-X64-VC80</td><td>for Visual Studio 2005 (amd64)</td></tr>
+<tr><td>XERCESCPKG-31-X64-VC90</td><td>for Visual Studio 2008 (amd64)</td></tr>
+<tr><td>XERCESCPKG-31-X64-VC100</td><td>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>
+
+<note>You MUST NOT merge the <em>bin</em> and <em>lib</em> directories from packages
+compiled with different compilers or different target (Win32 or amd64) platforms.</note>
+
+<p>It is safe to merge the <em>bin</em> directories of compatible Xalan-C and Xerces-C
+distributions into a common directory known by the system PATH environment.
+You can safely merge the <em>lib</em> directories of Xalan-C and Xerces-C into a common directory.
+ You can safely merge the <em>include</em> directories of both Xalan-C and Xerces-C
+as long as the subdirectories of <em>xalanc</em> and <em>xercesc</em> remain intact.</p>
+
+<anchor name="ConfWinPath"/>
+<s4 title="Configure Windows PATH">
+
+<p>Windows systems require that the bin directories be added to the
+PATH environment so the library DLL files can be found.
+The <em>Xalan.exe</em> 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>SelectEnvironment Variables.</li>
+<li>Add the bin directory to the system PATH environment.</li>
+</ol>
+<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 <em>bin</em> 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}/<em>bin</em></code> directory
+to the PATH environment.</p>
+<source>
+set PATH=%PATH%;{target}/bin
+</source>
+</s4>
</s3>
</s2>
-<anchor name="XalanDocPkg"/>
+<anchor name="InstDocPkgs"/>
<s2 title="Install Documentation Packages">
-<p>The documentation packages are distributed as <ref>tar</ref> files
- and <ref>zip</ref> 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 <link idref="index">
- <code>{docs}/xalan-c</code></link> directory.
-</p>
-<p><em>TO DO:</em></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 <link idref="builddocs">Build Documents</link> pages.
-</p>
-
-<anchor name="DocWebPkg"/>
-<s3 title="Install Xalan-C User Guide">
-<p>Extract the distributed <ref>tar</ref> file or <ref>zip</ref>
- 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>
-</s3>
-<anchor name="DocApiPkg"/>
-<s3 title="Install Xalan-C API Reference">
-<p>Extract the distributed <ref>tar</ref> file or <ref>zip</ref>
- 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>
-</s3>
+<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 <em>tar</em> and <em>zip</em> files.
+You just extract the contents into a directory that is reachable by your favorite web browser.
+The documentation tree starts with the <em>./xalan-c/</em> directory.
+The top documentation page is the <em>./xalan-c/index.html</em> file.</p>
+
+<p>The documentation is initially a snapshot of the
+<jump href="http://xalan.apache.org/xalan-c/index.html">Apache Xalan-C/C++ website</jump>
+at the time the product was released.</p>
</s2>
</s1>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/releasenotes.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/releasenotes.xml?rev=1411029&r1=1411028&r2=1411029&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/releasenotes.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/releasenotes.xml Sun Nov 18 23:53:39 2012
@@ -48,9 +48,17 @@
<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 <link anchor="dotNet">"Step for doing a Windows Build with Visual Studio .NET"</link> 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 <link anchor="xercesdepdom">"Steps for doing a Build with Xerces Deprecated DOM Support"</link></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
+ <link anchor="xercesdepdom">"Steps for doing a Build with Xerces Deprecated DOM Support"</link></li>
<!--
- <li>Porting of conf utility to the UNIX platform. The conf utility is a test harness designed to run the conformance tests located under the xml-xalan/test/tests directory. After the tests have been run, a results report is generated in HTML format for easy viewing. For more information on how to use this tool, please see <link idref="commandline" anchor="confexe">"Using the command line utility"</link>.</li>
+ <li>Porting of conf utility to the UNIX platform.
+ The conf utility is a test harness designed to run the conformance tests located under
+ the xml-xalan/test/tests directory. After the tests have been run, a results
+ report is generated in HTML format for easy viewing. For more information on how to use
+ this tool, please see <link idref="commandline" anchor="confexe">"Using the
+ command line utility"</link>.</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". See bugzilla <jump href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24304">24304</jump> and <jump href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28386">28386</jump>.</li>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/resources.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/resources.xml?rev=1411029&r1=1411028&r2=1411029&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/resources.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/resources.xml Sun Nov 18 23:53:39 2012
@@ -62,13 +62,13 @@
<resource id="icu"
title="International Components for Unicode (ICU)"
- location="http://oss.software.ibm.com/icu/index.html"/>
+ location="http://icu-project.org"/>
<resource id="icu-download"
title="&icu-used;"
- location="http://oss.software.ibm.com/icu/download/index.html"/>
+ location="http://icu-project.org/download"/>
<resource id="xerces-build-icu"
title="Building ICU for &xml4c;"
- location="http://xml.apache.org/xerces-c/build.html#BuildICU"/>
+ location="http://xerces.apache.org/xerces-c/build-3.html"/>
<resource id="stlport"
title="STLport"
location="http://www.stlport.org/"/>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/usagepatterns.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/usagepatterns.xml?rev=1411029&r1=1411028&r2=1411029&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/usagepatterns.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/usagepatterns.xml Sun Nov 18 23:53:39 2012
@@ -451,7 +451,7 @@ void parseWithXerces(XalanTransformer &a
<li>Define the XALAN_USE_ICU environment variable.<br/><br/></li>
<li>Set the XALANROOT environment variable to the path to to the ICU root (unless you have copied the ICU library to
/usr/lib).<br/><br/></li>
- <li><link idref="build_instruct" anchor="unix">Rebuild the Xalan library</link> (&xslt4c-linuxlib; for Linux, &xslt4c-aixlib; for AIX,
+ <li><link idref="buildlibs" anchor="unixbldenv">Rebuild the Xalan library</link> (&xslt4c-linuxlib; for Linux, &xslt4c-aixlib; for AIX,
&xslt4c-hplib; for HP-UX 11, and &xslt4c-solarislib; for Solaris).<br/><br/></li>
<li>Be sure the Xalan library is on the library path (LD_LIBRARY_PATH for Red Hat Linux, LIBPATH for AIX, SHLIB_PATH for
HP-UX 11, LD_LIBRARY_PATH for Solaris).</li>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/whatsnew.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/whatsnew.xml?rev=1411029&r1=1411028&r2=1411029&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/whatsnew.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/whatsnew.xml Sun Nov 18 23:53:39 2012
@@ -40,20 +40,15 @@
<p><em>Release notes for Xalan-C/C++ Version 1.11</em>
</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
-<jump href="mailto:dev@xalan.apache.org">xalan-dev</jump> 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 <jump href="mailto:dev@xalan.apache.org">xalan-dev</jump> mail list.
+You may also wish to check our <link idref="download">download</link> 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
@@ -87,12 +82,17 @@ and offers to help to <human-resource-re
<s2 title="Bug Fixes in Release 1.11">
<p>The bugs fixed in &xslt4c-current; 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>
@@ -270,7 +270,9 @@ and offers to help to <human-resource-re
<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>
</s2>
</s1>
Added: xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/Xalan-Logo-tm.png
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/Xalan-Logo-tm.png?rev=1411029&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/Xalan-Logo-tm.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/Xalan-Trademark.txt
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/Xalan-Trademark.txt?rev=1411029&view=auto
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/Xalan-Trademark.txt (added)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/Xalan-Trademark.txt Sun Nov 18 23:53:39 2012
@@ -0,0 +1,106 @@
+
+The XALAN Logo - Trademark Description
+--------------------------------------
+
+Prepared By:
+
+ Steven J. Hathaway
+
+ (shathaway@apache.org)
+
+ September 3, 2011
+
+
+
+Prepared for:
+
+ The Apache Software Foundation
+
+--------------------------------------
+
+Graphic: A stylized version of the African Xalam instrument.
+
+Note: the difference in spelling.
+
+ Xalam is the African Musical Instrument
+ Xalan is the Apache Xalan Software Project
+
+
+TEXT FONTS SIZE AND STYLE:
+
+TM (trademark symbol)
+
+ Font: Arial
+ Size: 14pt
+ Style: Bold)
+
+XSLT
+
+ Font: Arial
+ Size: 22pt
+ Style: Bold
+
+Apache Software Foundation (trademark name)
+
+ Font: Arial
+ Size: 18pt
+ Style: Bold
+ Note: 2 space characters between words
+
+Xalan (trademark name)
+
+ Font: Segoe Print
+ Size: 48pt
+ Style: Bold
+
+Xalan-C (trademark name)
+
+ Font: Segoe Print
+ Size: 48pt
+ Style: Bold
+
+Xalan-J (trademark name)
+
+ Font: Segoe Print
+ Size: 48pt
+ Style: Bold
+
+
+INSTRUMENT GRAPHIC (vector equations)
+
+ Vertical Width: 0.75 inch (3/4)
+ HorizontalLength: 3.667 inch (3 2/3)
+
+ Oval on the left,
+ neck and butt on the right.
+
+ Oval Width: 0.75 inch (3/4)
+ Oval Length: 1.583 inch (1 7/12)
+
+ Neck Width: 0.167 inch (1/6)
+
+ Butt Width: 0.25 inch (1/4)
+ Butt Length: 0.417 inch (5/12)
+
+
+Description of instrument logo
+
+ Oval: simulation of a gourd sound chamber
+ With orange gradation hues
+
+ Neck: rectangle simulating a round fingerboard
+ With yellow-green gradation hues
+
+ Butt: rounded rectangle simulating end of neck
+ With olive-green hue
+
+ String Anchor: rounded rectangle on the gourd
+ With olive-green hue
+
+ 2 strings: the full length from Anchor to Butt
+
+ 2 strings: tied to neck, at 1/2 length from Anchor to Butt
+
+ 3 Loose Tie Strings on the Butt, simulating tuning anchors
+
+
\ No newline at end of file
Added: xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/XalanC-Logo-tm.png
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/XalanC-Logo-tm.png?rev=1411029&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/XalanC-Logo-tm.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/apache-xalan.css
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/apache-xalan.css?rev=1411029&view=auto
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/apache-xalan.css (added)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/apache-xalan.css Sun Nov 18 23:53:39 2012
@@ -0,0 +1,414 @@
+/* Xalan-C/C++ Project Web Pages (css) Stylesheet */
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+*/
+
+/* This (css) stylesheet renders the xhtml web pages that were generated
+ * from StyleBook XML markup using the "xalan-book.xslt" transformation.
+*/
+
+html > bod {left:0;}
+body {
+/* background-color: white; */
+ background-color: #f8f8f0;
+ color: black;
+ padding: 0;
+ margin: 0;
+ font-family: arial, "lucida console", san-serif;
+}
+
+/* Emulate table align=center */
+div.centered, td.centered {
+ text-align: center;
+}
+
+div.centered table {
+ margin: 0 auto;
+ text-align: left;
+}
+
+/*
+ * ID Sections
+ */
+
+#content {
+ width: 80%;
+ float: left;
+ font-size: 12pt;
+ padding-top: 1em;
+ padding-left: 5px;
+ margin-left: 10px;
+ border-left: 1px solid #aaa;
+}
+
+#navLeft {
+ clear: left;
+ width: 15%;
+ float: left;
+ padding: 2px;
+ margin-left: 1%;
+ color: red;
+ position: relative;
+ left: 1px;
+ background-color: #eee;
+}
+
+.navGroup {
+ color: Black;
+ font-size: 14pt;
+}
+
+
+#title {
+ color: black;
+ background-color: #eee;
+ text-align: center;
+ border-bottom: 1px solid #aaa;
+ padding: 0;
+ vertical-align: middle;
+}
+
+table.HdrTitle {
+ font-size: 18pt;
+}
+
+table.HdrButtons {
+ font-size: 8pt;
+ background-color: #ccf;
+ align: "center";
+ border: "1";
+
+}
+
+#footer {
+ clear: both;
+ margin: 0 2em;
+ color: #444;
+ background-color: #ddd;
+ text-align: center;
+ padding: .5em 0;
+ font-size: 75%;
+ border-top: 1px solid #aaa;
+}
+
+/*
+ * Anchors
+ */
+
+a {
+ color: blue;
+ text-decoration: undedrline;
+}
+
+a img {
+ border: 0;
+}
+
+a:hover {
+ text-decoration: none;
+ background-color: #d7c9c9;
+}
+
+/*
+ * Headers
+ */
+
+h1 {}
+
+#title h1 {
+ padding: 1px 0;
+ margin: 0;
+ float: right;
+ width: 60%;
+ font-size: 20pt;
+ text-align: center;
+}
+
+#content h1 { background-color: #8af }
+
+h2 {}
+
+#title h2 {
+ font-size: 14pt;
+ width: 60%;
+ text-alignment: center;
+ padding: 1px 0;
+ margin: 0;
+}
+
+#content h2 { background-color: #9bf }
+
+#content h2.year {
+ background-color: #ddd;
+ text-align: center;
+}
+
+h3 {}
+
+#content h3.monthName {
+ background-color: #333;
+ text-align: center;
+}
+
+#content h3 { background-color: #acf }
+
+h4{}
+
+#content h4.eventTitle {
+ margin-left: 1%;
+ border-bottom: 1px solid blue;
+}
+
+#content h4 { background-color: #cdf }
+
+/*
+ * Tables
+ */
+
+th {}
+
+td {}
+
+th.content {background-color: #4BD }
+td.content {background-color: #AEF }
+
+/*
+ * Lists and navLeft
+ */
+
+ul {}
+
+#navLeft ul {
+ list-style-type: none;
+ margin: 0;
+ padding: 0;
+}
+
+#navLeft ul li {
+ margin: 0;
+}
+
+#navLeft ul li p {
+ margin: 0;
+}
+
+#navLeft ul li ul {
+ list-style-type: none;
+ font-size: 90%;
+ margin: 0 2em;
+}
+
+#navLeft ul li ul li {
+ margin: 0;
+}
+
+/*
+ * Paragraphs
+ */
+
+p {}
+
+#navLeft p {
+ text-align: center;
+ padding: 0 auto;
+ margin: 0;
+}
+
+#footer p {
+ padding: 0;
+}
+
+#content p.topalign {
+ vertical-align: middle;
+ height: 2em;
+ text-align: center;
+ width: 100%;
+ padding: .5em;
+ border: 1px solid #ddd;
+}
+
+#content p.topalign img {
+ vertical-align: middle;
+ text-align: text-middle;
+}
+
+#content p.quote {
+ color:black;
+ font-style: italic;
+ font-size: 110%;
+ margin-left: 10%;
+ margin-right: 10%;
+ padding 1em;
+ border: 1px solid #ddd;
+ text-align: center;
+}
+
+#content p.navbar {
+ font-size: 90%;
+ text-align: center;
+ border-top: 1px solid #ddd;
+ border-bottom: 1px solid #ddd;
+}
+
+blockquote {}
+
+blockquote.note {
+ font-size: 80%;
+ border: 1px solid #ddd;
+ background-color: #eee;
+}
+
+td.noteImg {
+ background-color: white;
+ border: 0;
+}
+
+td.noteTxt {
+ background-color: white;
+ font-size: 120%;
+ border: 2px solid #ddd;
+ background-color: #eee;
+}
+
+/**
+ ** UNSPECIFIED IN APACHE STYLEBOOK DTD
+ ** <caution>..</caution> and <warning>..</warning>
+ **
+ *
+ * td.cautionImg {
+ * background-color: white;
+ * border: 0;
+ * }
+ *
+ * td.cautionTxt {
+ * background-color: white;
+ * font-size: 120%;
+ * border: 2px solid #ddd;
+ * background-color: #eee;
+ * }
+ *
+ *
+ * td.warningImg {
+ * background-color: white;
+ * border: 0;
+ * }
+ *
+ * td.warningTxt {
+ * background-color: white;
+ * font-size: 120%;
+ * border: 2px solid #ddd;
+ * background-color: #eee;
+ * }
+ *
+**/
+
+
+blockquote.source {
+ font-size: 75%;
+}
+
+code {
+ font-size: 75%;
+}
+
+
+/*
+ * Special Table (note)
+ */
+
+#notediv div { background-color: white }
+
+table.note {
+ width: 90%;
+}
+
+td.noteImg {
+ background-color: white;
+ vertical-align: top;
+ border: 0;
+ width: 24;
+}
+
+td.noteTxt {
+ color: black;
+ background-color: #eee;
+ font-size: 90%;
+ border: 2px solid;
+ border-color: #ccc;
+}
+
+
+/*
+ * Images
+ */
+
+img {}
+
+
+#footer img {
+ border: 0;
+}
+
+
+/*
+ * Document Divisions
+ */
+
+div {}
+
+/*
+ * Pre
+ */
+
+pre {}
+
+
+/*
+ * Generic Classes
+ */
+
+.indented {
+ margin-left: 3%;
+}
+
+.topBanner {
+ float: right;
+ margin: 0;
+ border: 0;
+ vertical-align: middle;
+}
+
+.noborder {
+ border: 0;
+ margin: 0;
+}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Added: xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/asf_logo.png
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/asf_logo.png?rev=1411029&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/asf_logo.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/note.gif
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/note.gif?rev=1411029&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/c/branches/GSoC-2012/xdocs/sources/xslt-resources/note.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xalan.apache.org
For additional commands, e-mail: commits-help@xalan.apache.org