You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by gg...@apache.org on 2019/04/21 22:41:19 UTC
[xalan-site] 28/36: Update Xalan-C Links, Including Mirror Download
This is an automated email from the ASF dual-hosted git repository.
ggregory pushed a commit to branch git-svn
in repository https://gitbox.apache.org/repos/asf/xalan-site.git
commit 2f7e81dec0054ec20be4dadadaf2d0dd8800d854
Author: Steven J. Hathaway <sh...@apache.org>
AuthorDate: Mon Oct 22 19:23:03 2012 +0000
Update Xalan-C Links, Including Mirror Download
---
docs/xalan/xalan-c/builddocs.html | 722 +++++------
docs/xalan/xalan-c/buildlibs.html | 2088 +++++++++++++++---------------
docs/xalan/xalan-c/charter.html | 976 +++++++-------
docs/xalan/xalan-c/commandline.html | 510 ++++----
docs/xalan/xalan-c/download.html | 1152 +++++++++--------
docs/xalan/xalan-c/extensions.html | 880 ++++++-------
docs/xalan/xalan-c/extensionslib.html | 736 +++++------
docs/xalan/xalan-c/faq.html | 1464 ++++++++++-----------
docs/xalan/xalan-c/getstarted.html | 898 ++++++-------
docs/xalan/xalan-c/index.html | 1074 ++++++++--------
docs/xalan/xalan-c/install.html | 990 +++++++--------
docs/xalan/xalan-c/license.html | 786 ++++++------
docs/xalan/xalan-c/overview.html | 768 +++++------
docs/xalan/xalan-c/programming.html | 494 ++++----
docs/xalan/xalan-c/readme.html | 2240 ++++++++++++++++----------------
docs/xalan/xalan-c/releasenotes.html | 2246 ++++++++++++++++-----------------
docs/xalan/xalan-c/resources.html | 648 +++++-----
docs/xalan/xalan-c/samples.html | 1770 +++++++++++++-------------
docs/xalan/xalan-c/secureweb.html | 1172 ++++++++---------
docs/xalan/xalan-c/usagepatterns.html | 1890 +++++++++++++--------------
docs/xalan/xalan-c/whatsnew.html | 1454 ++++++++++-----------
21 files changed, 12497 insertions(+), 12461 deletions(-)
diff --git a/docs/xalan/xalan-c/builddocs.html b/docs/xalan/xalan-c/builddocs.html
index 83a7fce..6e3e1e2 100644
--- a/docs/xalan/xalan-c/builddocs.html
+++ b/docs/xalan/xalan-c/builddocs.html
@@ -1,361 +1,361 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html>
-<head>
-<title>ASF: Building The Documents</title>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
-</head>
-<!--
- * 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.
- -->
-<body>
-<div id="title">
-<table class="HdrTitle">
-<tbody>
-<tr>
-<th rowspan="2">
-<a href="../index.html">
-<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
-</a>
-</th>
-<th text-align="center" width="75%">
-<a href="index.html">Xalan-C/C++ Version 1.11</a>
-</th>
-</tr>
-<tr>
-<td valign="middle">Building The Documents</td>
-</tr>
-</tbody>
-</table>
-<table class="HdrButtons" align="center" border="1">
-<tbody>
-<tr>
-<td>
-<a href="http://www.apache.org">Apache Foundation</a>
-</td>
-<td>
-<a href="http://xalan.apache.org">Xalan Project</a>
-</td>
-<td>
-<a href="http://xerces.apache.org">Xerces Project</a>
-</td>
-<td>
-<a href="http://www.w3.org/TR">Web Consortium</a>
-</td>
-<td>
-<a href="http://www.oasis-open.org/standards">Oasis Open</a>
-</td>
-</tr>
-</tbody>
-</table>
-</div>
-<div id="navLeft">
-<ul>
-<li>
-<a href="resources.html">Resources</a>
-<br />
-</li>
-<li>
-<a href="../index.html">Home</a>
-</li></ul><hr /><ul>
-<li>
-<a href="index.html">Xalan-C++ 1.11</a>
-</li>
-<li>
-<a href="whatsnew.html">What's New</a>
-</li>
-<li>
-<a href="license.html">Licenses</a>
-</li></ul><hr /><ul>
-<li>
-<a href="overview.html">Overview</a>
-</li>
-<li>
-<a href="charter.html">Charter</a>
-</li></ul><hr /><ul>
-<li>
-<a href="download.html">Download</a>
-</li>
-<li>
-<a href="buildlibs.html">Build Libraries</a>
-</li>
-<li>
-<a href="install.html">Installation</a>
-</li>
-<li>Build Documents<br />
-</li></ul><hr /><ul>
-<li>
-<a href="samples.html">Sample Apps</a>
-</li>
-<li>
-<a href="commandline.html">Command Line</a>
-</li>
-<li>
-<a href="usagepatterns.html">Usage Patterns</a>
-</li></ul><hr /><ul>
-<li>
-<a href="programming.html">Programming</a>
-</li>
-<li>
-<a href="extensions.html">Extensions</a>
-</li>
-<li>
-<a href="extensionslib.html">Extensions Library</a>
-</li>
-<li>
-<a href="apiDocs/index.html">API Reference</a>
-</li></ul><hr /><ul>
-<li>
-<a href="faq.html">Xalan-C FAQs</a>
-</li></ul><hr /><ul>
-<li>
-<a href="whatsnew.html#bugs">Bugs</a>
-</li>
-<li>
-<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
-</li>
-<li>
-<a href="secureweb.html">Web Security</a>
-</li>
-</ul>
-</div>
-<div id="content">
-<h2>Building The Documents</h2>
-<ul>
-<li>
-<a href="#thedocs">The Xalan-C/C++ HTML Documentation</a>
-</li>
-<li>
-<a href="#unixsetup">Setup UNIX for Building the Documents</a>
-</li>
- <ul>
- <li>
-<a href="#unixdocbld">Build the Documentation on UNIX</a>
-</li>
- </ul>
-<li>
-<a href="#winsetup">Setup WINDOWS for Building the Documents</a>
-</li>
-<li>
-<a href="#aboutstylebook">About the StyleBook XML Markup</a>
-</li>
- <ul>
- <li>
-<a href="#sb_dirlayout">Source Directory Layout</a>
-</li>
- <li>
-<a href="#sb_scripts">Document Building Scripts</a>
-</li>
- </ul>
-</ul>
-<p>Our HTML web page construction does not use or require
-any Java installed or the use of JavaScript.</p>
-
-<a name="thedocs"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>The Xalan-C/C++ HTML Documentation</h3>
-<p>The current Xalan-C/C++ HTML documentation pages are available on our website
- <a href="http://xalan.apache.org/xalan-c/index.html">
- http://xalan.apache.org/xalan-c</a>.</p>
-<p>The HTML documentation pages can be built from the Xalan-C
-source distribution. Let <code>${XALANC}</code> indicate the top directory
-of the source distribution.</p>
-<blockquote class="source">
-<pre>
- ${XALANC}/src/ = the program library source files
- ${XALANC}/xdocs/ = the program documentation source files
- ${XALANC}/build/docs/ = the directory created for documentation builds
- ${XALANC}/build/docs/apiDocs/html/ = apiDocs created here, then moved
- ${XALANC}/build/docs/xalan-c/ = the HTML documentation tree
-</pre>
-</blockquote>
-<p>UNIX platforms can build the complete documentation package (web pages plus
-interactive api reference).</p>
-<p> Windows platforms an only build the basic web pages.</p>
-
-<a name="unixsetup"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Setup UNIX for Building the Documents</h3>
-<ol>
-<li>Requires the <code>
-<b>Xalan</b>
-</code> executable in the <code>${PATH}</code> environment.</li>
-<li>Requires the <code>
-<b>libxerces-c.so</b>
-</code> and
- <code>
-<b>libxalan-c.so</b>
-</code> libraries in a path
- that is accessible to the <code>
-<b>Xalan</b>
-</code> executable.</li>
-<li>Requires a current installation of the
- <a href="http://www.doxygen.org">Doxygen</a> package.</li>
-<li>The interactive graphics for apiDocs require the
- <a href="http://www.graphviz.org">GraphViz</a> (dot) package.</li>
-</ol>
-<a name="unixdocbld"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Build the Documentation on UNIX</h4>
-<ol>
-<li>Connect to the <code>${XALANC}/xdocs/</code> directory.</li>
-<li>Run the <code>
-<b>make-apiDocs.sh</b>
-</code> (full graphics) or
- <code>
-<b>make-apiDocs-nograf.sh</b>
-</code> (no graphics).</li>
-<li>The script automatically chains to <code>
-<b>sources/make-book.sh</b>
-</code>
- for building the remainder of the documentation.</li>
-<li>You can now relocate and package the documentation at
- <code>${XALANC}/build/docs/xalan-c/</code>
- to your final destination of choice.</li>
-</ol>
-
-
-<a name="winsetup"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Setup WINDOWS for Building the Documents</h3>
-<ol>
-<li>Create a <code>%XALANC%\bin\</code> directory. Then copy the
- <code>
-<b>xalan.exe</b>
-</code> and the DLL
- libraries for xerces-c and xalan-c into that directory. This is where
- the <code>
-<b>make-xalan.bat</b>
-</code> file expects to find the
- <code>
-<b>xalan.exe</b>
-</code> executable.</li>
-
-<li>Connect to the <code>%XALANC%\xdocs\sources\</code> directory.</li>
-
-<li>Run the <code>
-<b>make-book.bat</b>
-</code> script to create
- the <code>%XALANC%\build\docs\xalan-c\</code> documentation.</li>
-
-<li>You can now relocate and package the documentation at
- <code>%XALANC%\build\docs\xalan-c\</code> to your final destination of choice.</li>
-</ol>
-<table class="note">
-<tr>
-<td class="noteImg">
-<img src="resources/note.gif" alt="note" />
-</td>
-<td class="noteTxt">WINDOWS has no Doxygen program for building the apiDocs.
-Building apiDocs requires a Linux or UNIX platform. You might
-be able to use WINDOWS JavaDocs to get an interactive apiDocs reference.
-The JavaDocs program is part of the Java Developer's platform.</td>
-</tr>
-</table>
-<p>Our documentation does not rely on any Java installation.</p>
-
-<a name="aboutstylebook"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>About the StyleBook XML Markup</h3>
-<p>The obsolete Apache Java Stylebook program is no longer being used.
-The StyleBook XML markup has been slightly modified to accommodate
-standard XSLT stylesheet transformations.</p>
-<p>A standard <code>
-<b>stylebook.xslt</b>
-</code> XML transform stylesheet now
-allows any standard compliant XSLT processor to prepare the
-basic webpage documents. The resulting documents are in strict
-XHTML. The source pages have been adjusted so that
-compliant XML output mode is used and that transitional web
-browsers are accommodated.</p>
-<p>We also include a DTD library so that the markup source pages
-can be processed with a validating XML parser. The parser used
-with the <code>
-<b>stylebook.xslt</b>
-</code> stylesheet
-must accommodate top-level string parameters and the ability to
-process DTD definitions.</p>
-<p>Our stylebook processing scripts currently expect to use the
-Apache Xalan-C/C++ command-line executable program.</p>
-
-<a name="sb_dirlayout"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Source Directory Layout</h4>
-<blockquote class="source">
-<pre>
- ${XALAN}/xdocs/style/dtd/* -- the validation DTD definitions
- ${XALAN}/xdocs/sources/stylebook.xslt -- the XML StyleBook transform
- ${XALAN}/xdocs/sources/xalan/* -- the StyleBook XML page content
- ${XALAN}/xdocs/sources/xalan-graphic/* -- page specific graphics
- ${XALAN}/xdocs/sources/xslt-resources/* -- logos and css stylesheets
- ${XALAN}/xdocs/sources/xalan.xml -- the book navigation panel
- ${XALAN}/xdocs/sources/entities.ent -- book XML general entity definitions
- ${XALAN}/xdocs/sources/xalan/resources.xml -- general resource links
- ${XALAN}/build/docs/xalan-c/* -- the StyleBook html transformed pages
-</pre>
-</blockquote>
-<p>The resulting document from <code>
-<b>stylebook.xslt</b>
-</code> is strict XHTML with
-markup rules that can also be supported on transitional browsers.
-To guard against XML element collapse, we use the Unicode
-zero-width-non-joining character to provide non-empty content.
-Element collapse prevention is not handled by the "stylebook.xslt" transform.
-The Apache <code>Xalan</code> or <code>xalan.exe</code> programs do not
-should guard against unwanted element collapse.</p>
-
-<a name="sb_scripts"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Document Building Scripts</h4>
-<blockquote class="source">
-<pre>
- ${XALAN}/xdocs/sources/make-xalan.sh {pagename} -- transform a single page
- ${XALAN}/xdocs/sources/make-xalan.bat {pagename} -- transform a single page
-</pre>
-</blockquote>
-<blockquote class="source">
-<pre>
- ${XALAN}/xdocs/sources/make-book.sh -- transform an entire book
- ${XALAN}/xdocs/sources/make-book.bat -- transform an entire book
-</pre>
-</blockquote>
-
-
-<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 2012-10-07</div>
-</div>
-</body>
-</html>
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Building The Documents</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * 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.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan-C/C++ Version 1.11</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Building The Documents</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="../index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-C++ 1.11</a>
+</li>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="license.html">Licenses</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>
+<a href="charter.html">Charter</a>
+</li></ul><hr /><ul>
+<li>
+<a href="download.html">Download</a>
+</li>
+<li>
+<a href="buildlibs.html">Build Libraries</a>
+</li>
+<li>
+<a href="install.html">Installation</a>
+</li>
+<li>Build Documents<br />
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>
+<a href="commandline.html">Command Line</a>
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="programming.html">Programming</a>
+</li>
+<li>
+<a href="extensions.html">Extensions</a>
+</li>
+<li>
+<a href="extensionslib.html">Extensions Library</a>
+</li>
+<li>
+<a href="apiDocs/index.html">API Reference</a>
+</li></ul><hr /><ul>
+<li>
+<a href="faq.html">Xalan-C FAQs</a>
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html#bugs">Bugs</a>
+</li>
+<li>
+<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
+</li>
+<li>
+<a href="secureweb.html">Web Security</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<h2>Building The Documents</h2>
+<ul>
+<li>
+<a href="#thedocs">The Xalan-C/C++ HTML Documentation</a>
+</li>
+<li>
+<a href="#unixsetup">Setup UNIX for Building the Documents</a>
+</li>
+ <ul>
+ <li>
+<a href="#unixdocbld">Build the Documentation on UNIX</a>
+</li>
+ </ul>
+<li>
+<a href="#winsetup">Setup WINDOWS for Building the Documents</a>
+</li>
+<li>
+<a href="#aboutstylebook">About the StyleBook XML Markup</a>
+</li>
+ <ul>
+ <li>
+<a href="#sb_dirlayout">Source Directory Layout</a>
+</li>
+ <li>
+<a href="#sb_scripts">Document Building Scripts</a>
+</li>
+ </ul>
+</ul>
+<p>Our HTML web page construction does not use or require
+any Java installed or the use of JavaScript.</p>
+
+<a name="thedocs"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>The Xalan-C/C++ HTML Documentation</h3>
+<p>The current Xalan-C/C++ HTML documentation pages are available on our website
+ <a href="http://xalan.apache.org/xalan-c/index.html">
+ http://xalan.apache.org/xalan-c</a>.</p>
+<p>The HTML documentation pages can be built from the Xalan-C
+source distribution. Let <code>${XALANC}</code> indicate the top directory
+of the source distribution.</p>
+<blockquote class="source">
+<pre>
+ ${XALANC}/src/ = the program library source files
+ ${XALANC}/xdocs/ = the program documentation source files
+ ${XALANC}/build/docs/ = the directory created for documentation builds
+ ${XALANC}/build/docs/apiDocs/html/ = apiDocs created here, then moved
+ ${XALANC}/build/docs/xalan-c/ = the HTML documentation tree
+</pre>
+</blockquote>
+<p>UNIX platforms can build the complete documentation package (web pages plus
+interactive api reference).</p>
+<p> Windows platforms an only build the basic web pages.</p>
+
+<a name="unixsetup"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Setup UNIX for Building the Documents</h3>
+<ol>
+<li>Requires the <code>
+<b>Xalan</b>
+</code> executable in the <code>${PATH}</code> environment.</li>
+<li>Requires the <code>
+<b>libxerces-c.so</b>
+</code> and
+ <code>
+<b>libxalan-c.so</b>
+</code> libraries in a path
+ that is accessible to the <code>
+<b>Xalan</b>
+</code> executable.</li>
+<li>Requires a current installation of the
+ <a href="http://www.doxygen.org">Doxygen</a> package.</li>
+<li>The interactive graphics for apiDocs require the
+ <a href="http://www.graphviz.org">GraphViz</a> (dot) package.</li>
+</ol>
+<a name="unixdocbld"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Build the Documentation on UNIX</h4>
+<ol>
+<li>Connect to the <code>${XALANC}/xdocs/</code> directory.</li>
+<li>Run the <code>
+<b>make-apiDocs.sh</b>
+</code> (full graphics) or
+ <code>
+<b>make-apiDocs-nograf.sh</b>
+</code> (no graphics).</li>
+<li>The script automatically chains to <code>
+<b>sources/make-book.sh</b>
+</code>
+ for building the remainder of the documentation.</li>
+<li>You can now relocate and package the documentation at
+ <code>${XALANC}/build/docs/xalan-c/</code>
+ to your final destination of choice.</li>
+</ol>
+
+
+<a name="winsetup"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Setup WINDOWS for Building the Documents</h3>
+<ol>
+<li>Create a <code>%XALANC%\bin\</code> directory. Then copy the
+ <code>
+<b>xalan.exe</b>
+</code> and the DLL
+ libraries for xerces-c and xalan-c into that directory. This is where
+ the <code>
+<b>make-xalan.bat</b>
+</code> file expects to find the
+ <code>
+<b>xalan.exe</b>
+</code> executable.</li>
+
+<li>Connect to the <code>%XALANC%\xdocs\sources\</code> directory.</li>
+
+<li>Run the <code>
+<b>make-book.bat</b>
+</code> script to create
+ the <code>%XALANC%\build\docs\xalan-c\</code> documentation.</li>
+
+<li>You can now relocate and package the documentation at
+ <code>%XALANC%\build\docs\xalan-c\</code> to your final destination of choice.</li>
+</ol>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">WINDOWS has no Doxygen program for building the apiDocs.
+Building apiDocs requires a Linux or UNIX platform. You might
+be able to use WINDOWS JavaDocs to get an interactive apiDocs reference.
+The JavaDocs program is part of the Java Developer's platform.</td>
+</tr>
+</table>
+<p>Our documentation does not rely on any Java installation.</p>
+
+<a name="aboutstylebook"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>About the StyleBook XML Markup</h3>
+<p>The obsolete Apache Java Stylebook program is no longer being used.
+The StyleBook XML markup has been slightly modified to accommodate
+standard XSLT stylesheet transformations.</p>
+<p>A standard <code>
+<b>stylebook.xslt</b>
+</code> XML transform stylesheet now
+allows any standard compliant XSLT processor to prepare the
+basic webpage documents. The resulting documents are in strict
+XHTML. The source pages have been adjusted so that
+compliant XML output mode is used and that transitional web
+browsers are accommodated.</p>
+<p>We also include a DTD library so that the markup source pages
+can be processed with a validating XML parser. The parser used
+with the <code>
+<b>stylebook.xslt</b>
+</code> stylesheet
+must accommodate top-level string parameters and the ability to
+process DTD definitions.</p>
+<p>Our stylebook processing scripts currently expect to use the
+Apache Xalan-C/C++ command-line executable program.</p>
+
+<a name="sb_dirlayout"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Source Directory Layout</h4>
+<blockquote class="source">
+<pre>
+ ${XALAN}/xdocs/style/dtd/* -- the validation DTD definitions
+ ${XALAN}/xdocs/sources/stylebook.xslt -- the XML StyleBook transform
+ ${XALAN}/xdocs/sources/xalan/* -- the StyleBook XML page content
+ ${XALAN}/xdocs/sources/xalan-graphic/* -- page specific graphics
+ ${XALAN}/xdocs/sources/xslt-resources/* -- logos and css stylesheets
+ ${XALAN}/xdocs/sources/xalan.xml -- the book navigation panel
+ ${XALAN}/xdocs/sources/entities.ent -- book XML general entity definitions
+ ${XALAN}/xdocs/sources/xalan/resources.xml -- general resource links
+ ${XALAN}/build/docs/xalan-c/* -- the StyleBook html transformed pages
+</pre>
+</blockquote>
+<p>The resulting document from <code>
+<b>stylebook.xslt</b>
+</code> is strict XHTML with
+markup rules that can also be supported on transitional browsers.
+To guard against XML element collapse, we use the Unicode
+zero-width-non-joining character to provide non-empty content.
+Element collapse prevention is not handled by the "stylebook.xslt" transform.
+The Apache <code>Xalan</code> or <code>xalan.exe</code> programs do not
+should guard against unwanted element collapse.</p>
+
+<a name="sb_scripts"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Document Building Scripts</h4>
+<blockquote class="source">
+<pre>
+ ${XALAN}/xdocs/sources/make-xalan.sh {pagename} -- transform a single page
+ ${XALAN}/xdocs/sources/make-xalan.bat {pagename} -- transform a single page
+</pre>
+</blockquote>
+<blockquote class="source">
+<pre>
+ ${XALAN}/xdocs/sources/make-book.sh -- transform an entire book
+ ${XALAN}/xdocs/sources/make-book.bat -- transform an entire book
+</pre>
+</blockquote>
+
+
+<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 - Tue 2012-10-09</div>
+</div>
+</body>
+</html>
diff --git a/docs/xalan/xalan-c/buildlibs.html b/docs/xalan/xalan-c/buildlibs.html
index 7629b81..fcc1997 100644
--- a/docs/xalan/xalan-c/buildlibs.html
+++ b/docs/xalan/xalan-c/buildlibs.html
@@ -1,1044 +1,1044 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html>
-<head>
-<title>ASF: Building Xalan-C/C++</title>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
-</head>
-<!--
- * 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.
- -->
-<body>
-<div id="title">
-<table class="HdrTitle">
-<tbody>
-<tr>
-<th rowspan="2">
-<a href="../index.html">
-<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
-</a>
-</th>
-<th text-align="center" width="75%">
-<a href="index.html">Xalan-C/C++ Version 1.11</a>
-</th>
-</tr>
-<tr>
-<td valign="middle">Building Xalan-C/C++</td>
-</tr>
-</tbody>
-</table>
-<table class="HdrButtons" align="center" border="1">
-<tbody>
-<tr>
-<td>
-<a href="http://www.apache.org">Apache Foundation</a>
-</td>
-<td>
-<a href="http://xalan.apache.org">Xalan Project</a>
-</td>
-<td>
-<a href="http://xerces.apache.org">Xerces Project</a>
-</td>
-<td>
-<a href="http://www.w3.org/TR">Web Consortium</a>
-</td>
-<td>
-<a href="http://www.oasis-open.org/standards">Oasis Open</a>
-</td>
-</tr>
-</tbody>
-</table>
-</div>
-<div id="navLeft">
-<ul>
-<li>
-<a href="resources.html">Resources</a>
-<br />
-</li>
-<li>
-<a href="../index.html">Home</a>
-</li></ul><hr /><ul>
-<li>
-<a href="index.html">Xalan-C++ 1.11</a>
-</li>
-<li>
-<a href="whatsnew.html">What's New</a>
-</li>
-<li>
-<a href="license.html">Licenses</a>
-</li></ul><hr /><ul>
-<li>
-<a href="overview.html">Overview</a>
-</li>
-<li>
-<a href="charter.html">Charter</a>
-</li></ul><hr /><ul>
-<li>
-<a href="download.html">Download</a>
-</li>
-<li>Build Libraries<br />
-</li>
-<li>
-<a href="install.html">Installation</a>
-</li>
-<li>
-<a href="builddocs.html">Build Documents</a>
-</li></ul><hr /><ul>
-<li>
-<a href="samples.html">Sample Apps</a>
-</li>
-<li>
-<a href="commandline.html">Command Line</a>
-</li>
-<li>
-<a href="usagepatterns.html">Usage Patterns</a>
-</li></ul><hr /><ul>
-<li>
-<a href="programming.html">Programming</a>
-</li>
-<li>
-<a href="extensions.html">Extensions</a>
-</li>
-<li>
-<a href="extensionslib.html">Extensions Library</a>
-</li>
-<li>
-<a href="apiDocs/index.html">API Reference</a>
-</li></ul><hr /><ul>
-<li>
-<a href="faq.html">Xalan-C FAQs</a>
-</li></ul><hr /><ul>
-<li>
-<a href="whatsnew.html#bugs">Bugs</a>
-</li>
-<li>
-<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
-</li>
-<li>
-<a href="secureweb.html">Web Security</a>
-</li>
-</ul>
-</div>
-<div id="content">
-<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>
-<a href="#winbld">Windows Basic Build Instruction</a>
-</li>
- <li>
-<a href="#winbldcmd">Sample Windows Build Command File</a>
-</li>
- <li>
-<a href="#winbldinst">Installing the Xalan Library on Windows</a>
-</li>
- </ul>
-<li>
-<a href="#unixbldenv">UNIX Build Environment</a>
-</li>
- <ul>
- <li>
-<a href="#unixlibpath">Finding Runtime Libraries</a>
-</li>
- <li>
-<a href="#unixbldxalan">Building the Xalan-C/C++ XSLT Libraries for UNIX</a>
-</li>
- </ul>
-<li>
-<a href="#unixcompileref">Reference on Unix Platforms and C++ Compilers</a>
-</li>
-<li>
-<a href="#xercesmodules">Xerces-C/C++ Transcoders and Plug-in Modules</a>
-</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>
-<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>
-</p>
-<h3>Windows Build Environment</h3>
-
-<p>Build support for Microsoft Visual Studio (VC6) is deprecated.
-</p>
-<p>Building Xalan-C/C++ with Microsoft Visual Studio (VC6) requires the Xerces-C/C++ version 2.8 or older releases. Microsoft VC6 is removed from the Xerces-C/C++ Version 3.x releases.
-</p>
-<p>Building Xalan-C/C++ with Microsoft Visual Studio .NET 2008 (VC9) requires Xerces-C/C++ version 3.1 or newer. Building with Microsoft Visual Studio .NET 2010 (VC10) requires Xerces-C/C++ version 3.1.1 or newer.
-</p>
-<p>Environment variables XERCESCROOT and XALANCROOT are required. Environment ICUROOT is used only if building Xalan-C/C++ with IBM-ICU library support.
-</p>
-<table border="1">
-<tr>
- <td class="content" rowspan="1" colspan="1">XERCESCROOT</td>
-<td class="content" rowspan="1" colspan="1">The Xerces-C/C++ installation directory</td>
-</tr>
-<tr>
- <td class="content" rowspan="1" colspan="1">XALANCROOT</td>
-<td class="content" rowspan="1" colspan="1">The Xalan-C/C++ source directory</td>
-</tr>
-<tr>
- <td class="content" rowspan="1" colspan="1">ICUROOT</td>
-<td class="content" rowspan="1" colspan="1">The IBM-ICU installation directory (only if building with ICU support)</td>
-</tr>
-</table>
-
-<p>I like to create command or batch files to setup the build environment variables and start the Visual Studio .NET development system using the custom build environment. I find this much easier than navigating the graphical interface to add custom build environments. The Microsoft *.vsprops custom property files are not available in the early versions of Visual Studio .NET platforms.
-</p>
-<a name="winbld"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Windows Basic Build Instruction</h4>
-<p>If you want to create binary packages from the sources, you may wish to look
-at the <a href="#winbldcmd">Windows Build Command File</a> in the next section.
-</p>
-<p>A quick experiment in building for Windows is documented in the remainder of this section.
-</p>
-<p>I have Visual Studio 2005, 2008, 2010 on one computer and VC6 and Visual Studio 2003
-installed on another computer.
-</p>
-<p>Microsoft Visual Studio .NET products will usually install
-a Visual Studio Command Prompt icon in the Visual Studio Tools subfolder
-for each version of Visual Studio installed on your computer.
-The Visual Studio Command Prompt automatically sets a basic development environment
-using a "vsvars32.bat" or "vcvarsall.bat" script
-for 32-bit or 64-bit platform builds, and leaves you at the command line for
-customizing your environment.
-</p>
-<p>You then define the XERCESCROOT, XALANCROOT, and ICUROOT environment variables.
-</p>
-<p>If the Xerces-C DLL files are not in directory %XERCESCROOT%\bin, you must add
-a directory to the PATH environment variable so the Xerces-C DLL files can be
-found.
-</p>
-<p>You then launch the Visual Studio .NET by calling <code>devenv</code> with a
-path to the <code>Xalan.sln</code> file as a parameter.
-</p>
-<p>The following section describes how you can build your own scripts to create
-binary packages from Xalan-C compiled sources for the various versions of
-Microsoft Visual Studio products.
-</p>
-
-<a name="winbldcmd"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Sample Windows Build Command File</h4>
-
-<p>I like to use this template for both Xerces-C and Xalan-C builds from sources. The sample shown here is for Xalan-C/C++ because the installation of Xerces-C/C++ should already have been done.
-</p>
-<blockquote class="source">
-<pre>
-SET XERCESCROOT="path to xerces-c installation"
-SET XALANCROOT="sources\xalan\c\"
-</pre>
-</blockquote>
-<p>Set the xalan project path for your version of Microsoft Visual Studio .NET.
-</p>
-<blockquote class="source">
-<pre>
-:: VS 2003 (VC7.1)
-SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC7.1
-
-:: VS 2005 (VC8)
-SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC8
-
-:: VS 2008 (VC9)
-SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC9
-
-:: VS 2010 (VC10)
-SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC10
-</pre>
-</blockquote>
-<p>Set some environment variables so we can easily copy or install the products after they have been built.
-</p>
-<blockquote class="source">
-<pre>
-:: VS 2003 (VC7.1)
-SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC7.1
-
-:: VS 2005 (VC8)
-SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC8
-
-:: VS 2008 (VC9)
-SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC9
-
-:: VS 2010 (VC10)
-SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC10
-</pre>
-</blockquote>
-<p>We use this Visual Studio .NET solution file.
-</p>
-<blockquote class="source">
-<pre>
-SET XALANCBUILDSLN=%XALANCPROJDIR%\xalan.sln
-</pre>
-</blockquote>
-<p>The <code>$(variable)</code> is expanded inside Visual Studio.<br />
-The <code>%variable%</code> is expanded by the cmd utility before launching the Visual Studio.
-</p>
-<blockquote class="source">
-<pre>
-SET PATH=%WINDIR%\system32;%WINDIR%;%WINDIR%\system32\Wbem
-SET INCLUDE=
-SET LIB=
-SET LIBPATH=
-SET SOURCE=
-</pre>
-</blockquote>
-<p>Set the default environment variables for your version of Microsoft Visual Studio .NET.
-</p>
-<blockquote class="source">
-<pre>
-:: VS 2000 (VC7) - obsolete
-call "%VS70COMNTOOLS%vsvars32.bat"
-
-:: VS 2003 (VC7.1) 32-bit platform
-call "%VS71COMNTOOLS%vsvars32.bat"
-
-:: VS 2005 (VC8) 32-bit platform
-call "%VS80COMNTOOLS%vsvars32.bat"
-
-:: VS 2005 (VC8) 64-bit platform
-call "%VS80COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
-
-:: VS 2008 (VC9) 32-bit platform
-call "%VS90COMNTOOLS%vsvars32.bat"
-
-:: VS 2008 (VC9) 64-bit platform
-call "%VS90COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
-
-:: VS 2010 (VC10) 32-bit platform
-call "%VS100COMNTOOLS%vsvars32.bat"
-
-:: VS 2010 (VC10) 64-bit platform
-call "%VS100COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
-</pre>
-</blockquote>
-<p>The LIBPATH and SOURCE environment variables may not be properly
-set by the vsvars32.bat command file. You may wish to start your
-Visual Studio .NET application without any custom environment
-and examine the Tools -> C/C++ project defaults for the various libraries.
-Then specifically set the paths in the build command file for your project.
-</p>
-<p>The Xalan-C and Xerces-C libraries do not use the Microsoft Framework,
-the "mfc" and the "atl" directives. Microsoft is deprecating their "mfc"
-Microsoft Foundation Classes.
-</p>
-<p>Define the necessary environment variables for building the Xalan-C/C++ libraries and sample programs.
-</p>
-<blockquote class="source">
-<pre>
-SET PATH=%PATH%;%XERCESCROOT%\bin
-
-SET INCLUDE=%INCLUDE%;%XERCESCROOT%\include;%XERCESCROOT%\src
-SET INCLUDE=%INCLUDE%;%XALANCROOT%\src
-
-SET LIB=%LIB%;%XERCESCROOT%\lib
-</pre>
-</blockquote>
-<p>If you are going to build for IBM-ICU support, then add the following environments.
-</p>
-<blockquote class="source">
-<pre>
-SET ICUROOT="path to ibm-icu installation"
-
-SET PATH=%PATH%;%ICUROOT%\bin
-SET INCLUDE=%INCLUDE%;%ICUROOT%\include
-SET LIB=%LIB%;%ICUROOT%\lib;%ICUROOT%\data
-</pre>
-</blockquote>
-<p>Now we should be ready to start the Microsoft Visual Studio .NET using our custom environment using the <code>%XALANCBUILDSLN%</code> solution.
-</p>
-<blockquote class="source">
-<pre>
-devenv.exe "%XALANCBUILDSLN%" /useenv
-</pre>
-</blockquote>
-
-<a name="winbldinst"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Installing the Xalan Library on Windows</h4>
-
-<p>The following command script will install the binary and header files to a target directory that is compatible with the XALANCROOT environment variable for creating applications. Environment variables other than XALANCTARGET are defined in the previous section, the <a href="#winbldcmd">Visual Studio .NET build example</a>.
-</p>
-<blockquote class="source">
-<pre>
-SET XALANCTARGET="path-to-target-directory"
-
-MKDIR "%XALANCTARGET%\bin"
-MKDIR "%XALANCTARGET%\include"
-MKDIR "%XALANCTARGET%\lib"
-
-CD "%XALANCBUILDDIR%\Release\Nls"
-COPY *.hpp "%XALANCTARGET%"\include
-
-CD "%XALANCBUILDDIR%\Release"
-COPY *.DLL "%XALANCTARGET%\bin"
-COPY *.LIB "%XALANCTARGET%\lib"
-COPY *.EXP "%XALANCTARGET%\lib"
-
-CD "%XALANCBUILDDIR%\Debug"
-COPY *.DLL "%XALANCTARGET%\bin"
-COPY *.PDB "%XALANCTARGET%\bin"
-COPY *.LIB "%XALANCTARGET%\lib"
-COPY *.EXP "%XALANCTARGET%\lib"
-
-CD "%XALANCROOT%\src
-XCOPY xalanc\*.hpp "%XALANCTARGET%\include\xalanc" /E /C /I /R /Y
-XCOPY xalanc\*.h "%XALANCTARGET%\include\xalanc" /E /C /I /R /Y
-</pre>
-</blockquote>
-
-<a name="unixbldenv"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>UNIX Build Environment</h3>
-
-<p>I don't like building sources using root or superuser login. I like to do builds in a directory separated from the source tree. A debug build and release build will create shared objects of the same name. I like to target these builds to separate directory trees.
-</p>
-<p>Release builds are targeted at the <code>/usr/local</code> file system.
-</p>
-<p>Debug builds are targeted at the <code>/opt/apache/debug</code> file system.
-</p>
-<p>Source trees are referenced wherever convenient. Using the (<code>--srcdir</code>) configuration parameter allows the source tree to be separate from the build tree. The source tree can even reside on read-only media.
-</p>
-<p>Product builds are done in a build directory path separate from the source tree. This is the working directory from where you perform your builds and installs.
-</p>
-<p>
-<b>Source Trees:</b> (<code>--srcdir</code>) configuration parameter
-</p>
-<p>
- <code>/opt/xerces/c/<trunk>/</code><the Xerces-C/C++ XML parser library source distribution>
-<br />
- <code>/opt/xalan/c/<trunk></code>/<the Xalan-C/C++ XSLT library source distribution>
-</p>
-<p>If the source distribution is well-constructed, the source directory trees can be read-only.
-</p>
-<p>
-<b>Binary Installation Trees:</b> (<code>--prefix</code>) configuration parameter
-</p>
-<p>
- <code>/usr/local/</code> <the target for the
-release binary installation>
-<br />
- <code>./bin</code> The sample programs
-<br />
- <code>./lib</code> The shared and static library files
-<br />
- <code>./include</code> The library header files
-<br />
-<br />
- <code>/opt/apache/debug/</code> <the target for the
-debug binary installation>
-<br />
- <code>./bin</code> The sample programs
-<br />
- <code>./lib</code> The shared and static library files
-<br />
- <code>./include</code> The library header files
-</p>
-
-<p>The default (<code>--prefix</code>) value is <code>/usr/local</code> which I use for release builds.
-</p>
-<p>I choose (<code>--prefix</code>) value of <code>/opt/apache/debug</code> for debug builds.
-</p>
-
-<p>
-<b>Build Tree:</b> The build working directory tree
-</p>
-<p> <code>/<user-directory>/Build/</code>
-</p>
-
-<p>You can use any empty file system or directory path with write access. Starting with an empty directory is a quick way to do a clean build. Make this empty directory to be your current working directory.
-</p>
-<p>I also like to make some shell scripts so that the build process can be automated. I locate these scripts outside of the Build directory so they don't get lost when I purge directory content.
-</p>
-<p>
- <code>../build-xerces-lib.sh</code>
-</p>
-<p>
- <code>../build-xalan-lib.sh</code>
-</p>
-<p>
- <code>../build-xalan-app.sh</code>
-</p>
-<p>I generate these shell scripts with a text editor and use them to minimize keyboard typing errors.
-</p>
-<a name="unixlibpath"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Finding Runtime Libraries</h4>
-
-<p>The various types of UNIX operating systems have differing requirements for finding libraries at runtime.
-</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">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">Mac OS X</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 Xalan-C/C++ and Xerces-C/C++ shared library objects must be installed in a reachable library path for your platform. The <code>make</code> step creates the libraries in the <code>lib</code> subdirectory of your working directory. The <code>make install</code> step installs these shared objects to the designated <code>{prefix}/lib</code> directory or another directory defined by the <code>--libdir</code> configuration parameter.
-</p>
-<p>In many cases, the <code>/usr/local/lib</code> is already cached in <code>/etc/ld.so.cache</code> or included by <code>/etc/ld.so.conf</code>. The library path environment variable is then used for exceptions. The explicit library path environment variable usually takes precedence over the other methods of finding shared library runtimes. This is useful if you wish to use a debug environment on the same platform that also includes release libraries of the same name.
-</p>
-
-
-<a name="unixbldxalan"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Building the Xalan-C/C++ XSLT Libraries for UNIX</h4>
-
-
-<p>I don't like building sources from a root or superuser login. I also like to do builds in a directory separated from the source tree.
-</p>
-
-<p>If your sources tree is read-only and some required files are not executable, then you need to copy the source to writable media and change the execute attributes of specific files. This command sequence will copy an entire directory tree from <code>{source-dir}</code> to <code>{dest-dir}</code>.
-</p>
-<blockquote class="source">
-<pre>
- cd {source-dir}
- find . | cpio -pdmuv {dest-dir}
-</pre>
-</blockquote>
-<p>Connect to the <code>{xalan-src}</code> directory and make specific files executable.
-</p>
-<blockquote class="source">
-<pre>
- cd {xalan-src}
- chmod 755 runConfigure configure install-sh
-</pre>
-</blockquote>
-<p>Connect to your empty build directory and construct a script for building the Xalan-C/C++ XSLT products.
-</p>
-
-<p>The Xalan-C/C++ configuration process uses the <code>runConfigure</code> script as a front-end to the automake <code>configure</code> script. Your shell command script should therefore use the <code>runConfigure</code> script.
-</p>
-
-<table border="1">
-<tr>
-<th class="content" rowspan="1" colspan="2">runConfigure Options</th>
-</tr>
-<tr>
-<th class="content" rowspan="1" colspan="1">Option</th>
-<th class="content" rowspan="1" colspan="1">Description</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-p</td>
-<td class="content" rowspan="1" colspan="1">Build platform: aix, linux, freebsd, netbsd, solaris, hp-10, hp-11, hp11-ia64,
- irix, tru64, macosx, cygwin</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-c</td>
-<td class="content" rowspan="1" colspan="1">C compiler name: gcc, cc, c89, xlc, xlc_r, acc (default = gcc)</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-x</td>
-<td class="content" rowspan="1" colspan="1">C++ compiler name: g++, CC, C89, xlC, xlC_r, aCC (default = g++)</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-d</td>
-<td class="content" rowspan="1" colspan="1">Indicates a debug build, takes no values, default is No Debug</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-t</td>
-<td class="content" rowspan="1" colspan="1">Transcoder to use: 'icu', (Default is null, the Xerces-C/C++ transcoder)</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-m</td>
-<td class="content" rowspan="1" colspan="1">Type of localization support: inmem, icu, nls (default is inmem)</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-M</td>
-<td class="content" rowspan="1" colspan="1">Locale for message localization: "en_US"</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-r</td>
-<td class="content" rowspan="1" colspan="1">Threads option: pthread, dce (default is pthread)</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-b</td>
-<td class="content" rowspan="1" colspan="1">Specify 32 or 64 bit build (Default is 32-bit)<br />
- On Linux, the 32/64 build is determined by the compiler, kernel, and glibc.</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-P</td>
-<td class="content" rowspan="1" colspan="1">Install root directory: value is assigned to the <code>--prefix</code> configure parameter</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-l</td>
-<td class="content" rowspan="1" colspan="1">Extra link options (assigned to <code>LDFLAGS</code>)</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-z</td>
-<td class="content" rowspan="1" colspan="1">Extra compiler options (assigned to <code>CFLAGS</code> and <code>CXXFLAGS</code>)</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-C</td>
-<td class="content" rowspan="1" colspan="1">Extra configuration options (i.e. <code>--srcdir=${SourceDir}</code>)</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">-h</td>
-<td class="content" rowspan="1" colspan="1">Print the <code>runConfigure</code> help and exit</td>
-</tr>
-</table>
-
-<p>Here are the names of some C/C++ compilers associated with commercial UNIX operating systems used to build Xalan-C/C++ and Xerces-C/C++ packages.
-</p>
-
-<table border="1">
-<tr>
-<th class="content" rowspan="1" colspan="1">System</th>
-<th class="content" rowspan="1" colspan="1">Platform</th>
-<th class="content" rowspan="1" colspan="1">C Compiler</th>
-<th class="content" rowspan="1" colspan="1">C++ Compiler</th>
-<th class="content" rowspan="1" colspan="1">Comment</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">AIX</td>
-<td class="content" rowspan="1" colspan="1">aix</td>
-<td class="content" rowspan="1" colspan="1">xlc_r</td>
-<td class="content" rowspan="1" colspan="1">xlC_r</td>
-<td class="content" rowspan="1" colspan="1">thread support</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">AIX</td>
-<td class="content" rowspan="1" colspan="1">aix</td>
-<td class="content" rowspan="1" colspan="1">xlc</td>
-<td class="content" rowspan="1" colspan="1">xlC</td>
-<td class="content" rowspan="1" colspan="1">no thread support</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">Cygwin</td>
-<td class="content" rowspan="1" colspan="1">cygwin</td>
-<td class="content" rowspan="1" colspan="1">gcc</td>
-<td class="content" rowspan="1" colspan="1">g++</td>
-<td class="content" rowspan="1" colspan="1" />
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">HP-UX</td>
-<td class="content" rowspan="1" colspan="1">hp-11</td>
-<td class="content" rowspan="1" colspan="1">cc</td>
-<td class="content" rowspan="1" colspan="1">aCC</td>
-<td class="content" rowspan="1" colspan="1" />
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">HP-UX</td>
-<td class="content" rowspan="1" colspan="1">hp-11-ia64</td>
-<td class="content" rowspan="1" colspan="1">cc</td>
-<td class="content" rowspan="1" colspan="1">aCC</td>
-<td class="content" rowspan="1" colspan="1" />
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">Solaris</td>
-<td class="content" rowspan="1" colspan="1">solaris</td>
-<td class="content" rowspan="1" colspan="1">cc</td>
-<td class="content" rowspan="1" colspan="1">CC</td>
-<td class="content" rowspan="1" colspan="1" />
-</tr>
-</table>
-
-<p>The following example shows you how to construct a usable script with your favorite text editor.
-</p>
-
-<blockquote class="source">
-<pre>
-#!/bin/sh
-# Script to build and install Xalan-C/C++ products from sources
-
-# The Source and Target Directories for Debug Build
-
-# SourceDir="--srcdir=/opt/xalan/c/trunk"
-# DestDir="--prefix=/opt/apache/debug"
-
-# The Source and Target Directories for Release Build
-
-SourceDir="--srcdir=/opt/xalan/c/trunk"
-DestDir="--prefix=/usr/local"
-
-# The Xerces and Xalan package directories
-
-export XALANCROOT=${SourceDir}
-export XERCESCROOT=${DestDir}
-
-# If compiling with IBM-ICU support, the ICUROOT environment variable
-# needs to be defined to specify where the ICU libraries are installed.
-# Specifically, the following directories are accessed:
-# ${ICUROOT}/lib, ${ICUROOT}/include, ${ICUROOT}/data
-# export ICUROOT=/usr/local
-
-export PATH=$PATH:${SourceDir}
-
-# Debug Configure
-
-# runConfigure -p linux -d -c gcc -x g++ -P "${DestDir}" \
-# -C "--srcdir=${SourceDir}"
-
-# Release Configure
-
-runConfigure -p linux -c gcc -x g++ -P "${DestDir}" \
- -C "--srcdir=${SourceDir}"
-
-# Connect to configured src subdirectory to build the library without
-# sample programs. If you run make from your build directory, then the
-# library and all sample programs will be built.
-
-cd src
-make clean
-make
-
-# As a user with permissions to write to ${DestDir} install the Xalan-C/C++ products
-# ${DestDir}/bin the Xalan command-line utility and sample programs
-# ${DestDir)/lib the Xalan-C/C++ static and dynamic libraries
-# ${DestDir}/include/xalanc/* The header files.
-
-make install
-
-## End of sample build script.
-</pre>
-</blockquote>
-
-
-
-<a name="unixcompileref"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Reference on Unix Platforms and C++ Compilers</h3>
-
-<p>Some compilers and platforms may need configuration options and variables that differ from the default Linux build. Beware that the runConfigure script for Xalan-C/C++ is a front-end that calls the configure script. The following table is reference information for the build of Xerces-C/C++ version 3.x. The C++ compiler for Xerces should be the same as used for Xalan builds.
-</p>
-
-<table border="1">
-<tr>
-<th class="content" rowspan="1" colspan="2">Configuration Options For Unix Platforms</th>
-</tr>
-<tr>
-<th class="content" rowspan="1" colspan="1">Solaris x86</th>
-<th class="content" rowspan="1" colspan="1">Sun CC</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure CXX=CC CC=cc</td>
-</tr>
-
-<tr>
-<th class="content" rowspan="1" colspan="1">Solaris x86-64</th>
-<th class="content" rowspan="1" colspan="1">Sun CC</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure CXX=cc CC=cc CFLAGS=-xarch=amd64 CXXFLAGS=-xarch=amd64<br />
-(newer Sun CC versions use -m64 instead of -arch=amd64)</td>
-</tr>
-
-<tr>
-<th class="content" rowspan="1" colspan="1">Solaris Sparc</th>
-<th class="content" rowspan="1" colspan="1">Sun CC</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure CXX=CC CC=cc</td>
-</tr>
-
-<tr>
-<th class="content" rowspan="1" colspan="1">Solaris Sparc v9</th>
-<th class="content" rowspan="1" colspan="1">Sun CC</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure CXX=cc CC=cc CFLAGS=-xarch=v9 CXXFLAGS=-xarch=v9<br />
-(newer Sun CC versions use -m64 instead of -arch=v9)</td>
-</tr>
-
-<tr>
-<th class="content" rowspan="1" colspan="1">AIX PowerPC</th>
-<th class="content" rowspan="1" colspan="1">IBM XLC++</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure CXX=xlc_r CC=xlc_r<br />
-gmake libxerces_c_1a LDFLAGS=-qmkshrobj</td>
-</tr>
-
-<tr>
-<th class="content" rowspan="1" colspan="1">AIX PowerPC-64</th>
-<th class="content" rowspan="1" colspan="1">IBM XLC++</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure CXX=xlc_r CC=xlc_r CXXFLAGS=-q64 CFLAGS=-q64<br />
-gmake libxerces_c_1a LDFLAGS=-qmkshrobj</td>
-</tr>
-
-<tr>
-<th class="content" rowspan="1" colspan="1">HP-UX 1a-64-32</th>
-<th class="content" rowspan="1" colspan="1">HP aCC</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure CXX=aCC CC=aCC CFLAGS=-mt CXXFLAGS=-mt LDFLAGS=-mt</td>
-</tr>
-
-<tr>
-<th class="content" rowspan="1" colspan="1">HP-UX 1a-64</th>
-<th class="content" rowspan="1" colspan="1">HP aCC</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure CXX=aCC CC=aCC CFLAGS=-mt CXXFLAGS=-"mt +DD64" LDFLAGS="-mt +DD64"</td>
-</tr>
-
-<tr>
-<th class="content" rowspan="1" colspan="1">Mac OS X x86-64</th>
-<th class="content" rowspan="1" colspan="1">GCC</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure CFLAGS="-arch x86_64" CXXFLAGS="-arch x86_64"</td>
-</tr>
-
-<tr>
-<th class="content" rowspan="1" colspan="1">Mac OS X PowerPC-64</th>
-<th class="content" rowspan="1" colspan="1">GCC</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure CFLAGS="-arch ppc64" CXXFLAGS="-arch ppc64"</td>
-</tr>
-
-<tr>
-<th class="content" rowspan="1" colspan="1">Mac OS X x86/PowerPC</th>
-<th class="content" rowspan="1" colspan="1">GCC</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure --disable-dependency-tracking CFLAGS="arch i386 -arch ppc"<br />
-CXXFLAGS="-arch i386 -arch ppc"</td>
-</tr>
-
-<tr>
-<th class="content" rowspan="1" colspan="1">MinGW x86</th>
-<th class="content" rowspan="1" colspan="1">GCC</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure LDFLAGS=-no-undefined</td>
-</tr>
-
-<tr>
-<th class="content" rowspan="1" colspan="1">Cygwin x86</th>
-<th class="content" rowspan="1" colspan="1">GCC</th>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="2">./configure LDFLAGS=-no-undefined</td>
-</tr>
-</table>
-
-
-<a name="xercesmodules"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Xerces-C/C++ Transcoders and Plug-in Modules</h3>
-<p>Xerces-C/C++ XML Parsers have undergone some additional modularity features. In the version 3 series, the transcoders are now being implemented as runtime modules. Use of the transcoding modules is still experimental for Xalan-C/C++ transformation applications. The basic transcoder capability still exists. Xerces-C/C++ version 2 series had transcoder libraries explicitly built and installed.
-</p>
-<p>A plug-in memory management architecture was introduced in Xerces-C/C++ version 2.7. The plug-in memory management of Xerces-C/C++ is also supported by Xalan-C/C++ applications.
-</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 2012-10-07</div>
-</div>
-</body>
-</html>
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Building Xalan-C/C++</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * 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.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan-C/C++ Version 1.11</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Building Xalan-C/C++</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="../index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-C++ 1.11</a>
+</li>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="license.html">Licenses</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>
+<a href="charter.html">Charter</a>
+</li></ul><hr /><ul>
+<li>
+<a href="download.html">Download</a>
+</li>
+<li>Build Libraries<br />
+</li>
+<li>
+<a href="install.html">Installation</a>
+</li>
+<li>
+<a href="builddocs.html">Build Documents</a>
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>
+<a href="commandline.html">Command Line</a>
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="programming.html">Programming</a>
+</li>
+<li>
+<a href="extensions.html">Extensions</a>
+</li>
+<li>
+<a href="extensionslib.html">Extensions Library</a>
+</li>
+<li>
+<a href="apiDocs/index.html">API Reference</a>
+</li></ul><hr /><ul>
+<li>
+<a href="faq.html">Xalan-C FAQs</a>
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html#bugs">Bugs</a>
+</li>
+<li>
+<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
+</li>
+<li>
+<a href="secureweb.html">Web Security</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<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>
+<a href="#winbld">Windows Basic Build Instruction</a>
+</li>
+ <li>
+<a href="#winbldcmd">Sample Windows Build Command File</a>
+</li>
+ <li>
+<a href="#winbldinst">Installing the Xalan Library on Windows</a>
+</li>
+ </ul>
+<li>
+<a href="#unixbldenv">UNIX Build Environment</a>
+</li>
+ <ul>
+ <li>
+<a href="#unixlibpath">Finding Runtime Libraries</a>
+</li>
+ <li>
+<a href="#unixbldxalan">Building the Xalan-C/C++ XSLT Libraries for UNIX</a>
+</li>
+ </ul>
+<li>
+<a href="#unixcompileref">Reference on Unix Platforms and C++ Compilers</a>
+</li>
+<li>
+<a href="#xercesmodules">Xerces-C/C++ Transcoders and Plug-in Modules</a>
+</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>
+<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>
+</p>
+<h3>Windows Build Environment</h3>
+
+<p>Build support for Microsoft Visual Studio (VC6) is deprecated.
+</p>
+<p>Building Xalan-C/C++ with Microsoft Visual Studio (VC6) requires the Xerces-C/C++ version 2.8 or older releases. Microsoft VC6 is removed from the Xerces-C/C++ Version 3.x releases.
+</p>
+<p>Building Xalan-C/C++ with Microsoft Visual Studio .NET 2008 (VC9) requires Xerces-C/C++ version 3.1 or newer. Building with Microsoft Visual Studio .NET 2010 (VC10) requires Xerces-C/C++ version 3.1.1 or newer.
+</p>
+<p>Environment variables XERCESCROOT and XALANCROOT are required. Environment ICUROOT is used only if building Xalan-C/C++ with IBM-ICU library support.
+</p>
+<table border="1">
+<tr>
+ <td class="content" rowspan="1" colspan="1">XERCESCROOT</td>
+<td class="content" rowspan="1" colspan="1">The Xerces-C/C++ installation directory</td>
+</tr>
+<tr>
+ <td class="content" rowspan="1" colspan="1">XALANCROOT</td>
+<td class="content" rowspan="1" colspan="1">The Xalan-C/C++ source directory</td>
+</tr>
+<tr>
+ <td class="content" rowspan="1" colspan="1">ICUROOT</td>
+<td class="content" rowspan="1" colspan="1">The IBM-ICU installation directory (only if building with ICU support)</td>
+</tr>
+</table>
+
+<p>I like to create command or batch files to setup the build environment variables and start the Visual Studio .NET development system using the custom build environment. I find this much easier than navigating the graphical interface to add custom build environments. The Microsoft *.vsprops custom property files are not available in the early versions of Visual Studio .NET platforms.
+</p>
+<a name="winbld"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Windows Basic Build Instruction</h4>
+<p>If you want to create binary packages from the sources, you may wish to look
+at the <a href="#winbldcmd">Windows Build Command File</a> in the next section.
+</p>
+<p>A quick experiment in building for Windows is documented in the remainder of this section.
+</p>
+<p>I have Visual Studio 2005, 2008, 2010 on one computer and VC6 and Visual Studio 2003
+installed on another computer.
+</p>
+<p>Microsoft Visual Studio .NET products will usually install
+a Visual Studio Command Prompt icon in the Visual Studio Tools subfolder
+for each version of Visual Studio installed on your computer.
+The Visual Studio Command Prompt automatically sets a basic development environment
+using a "vsvars32.bat" or "vcvarsall.bat" script
+for 32-bit or 64-bit platform builds, and leaves you at the command line for
+customizing your environment.
+</p>
+<p>You then define the XERCESCROOT, XALANCROOT, and ICUROOT environment variables.
+</p>
+<p>If the Xerces-C DLL files are not in directory %XERCESCROOT%\bin, you must add
+a directory to the PATH environment variable so the Xerces-C DLL files can be
+found.
+</p>
+<p>You then launch the Visual Studio .NET by calling <code>devenv</code> with a
+path to the <code>Xalan.sln</code> file as a parameter.
+</p>
+<p>The following section describes how you can build your own scripts to create
+binary packages from Xalan-C compiled sources for the various versions of
+Microsoft Visual Studio products.
+</p>
+
+<a name="winbldcmd"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Sample Windows Build Command File</h4>
+
+<p>I like to use this template for both Xerces-C and Xalan-C builds from sources. The sample shown here is for Xalan-C/C++ because the installation of Xerces-C/C++ should already have been done.
+</p>
+<blockquote class="source">
+<pre>
+SET XERCESCROOT="path to xerces-c installation"
+SET XALANCROOT="sources\xalan\c\"
+</pre>
+</blockquote>
+<p>Set the xalan project path for your version of Microsoft Visual Studio .NET.
+</p>
+<blockquote class="source">
+<pre>
+:: VS 2003 (VC7.1)
+SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC7.1
+
+:: VS 2005 (VC8)
+SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC8
+
+:: VS 2008 (VC9)
+SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC9
+
+:: VS 2010 (VC10)
+SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC10
+</pre>
+</blockquote>
+<p>Set some environment variables so we can easily copy or install the products after they have been built.
+</p>
+<blockquote class="source">
+<pre>
+:: VS 2003 (VC7.1)
+SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC7.1
+
+:: VS 2005 (VC8)
+SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC8
+
+:: VS 2008 (VC9)
+SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC9
+
+:: VS 2010 (VC10)
+SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC10
+</pre>
+</blockquote>
+<p>We use this Visual Studio .NET solution file.
+</p>
+<blockquote class="source">
+<pre>
+SET XALANCBUILDSLN=%XALANCPROJDIR%\xalan.sln
+</pre>
+</blockquote>
+<p>The <code>$(variable)</code> is expanded inside Visual Studio.<br />
+The <code>%variable%</code> is expanded by the cmd utility before launching the Visual Studio.
+</p>
+<blockquote class="source">
+<pre>
+SET PATH=%WINDIR%\system32;%WINDIR%;%WINDIR%\system32\Wbem
+SET INCLUDE=
+SET LIB=
+SET LIBPATH=
+SET SOURCE=
+</pre>
+</blockquote>
+<p>Set the default environment variables for your version of Microsoft Visual Studio .NET.
+</p>
+<blockquote class="source">
+<pre>
+:: VS 2000 (VC7) - obsolete
+call "%VS70COMNTOOLS%vsvars32.bat"
+
+:: VS 2003 (VC7.1) 32-bit platform
+call "%VS71COMNTOOLS%vsvars32.bat"
+
+:: VS 2005 (VC8) 32-bit platform
+call "%VS80COMNTOOLS%vsvars32.bat"
+
+:: VS 2005 (VC8) 64-bit platform
+call "%VS80COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
+
+:: VS 2008 (VC9) 32-bit platform
+call "%VS90COMNTOOLS%vsvars32.bat"
+
+:: VS 2008 (VC9) 64-bit platform
+call "%VS90COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
+
+:: VS 2010 (VC10) 32-bit platform
+call "%VS100COMNTOOLS%vsvars32.bat"
+
+:: VS 2010 (VC10) 64-bit platform
+call "%VS100COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
+</pre>
+</blockquote>
+<p>The LIBPATH and SOURCE environment variables may not be properly
+set by the vsvars32.bat command file. You may wish to start your
+Visual Studio .NET application without any custom environment
+and examine the Tools -> C/C++ project defaults for the various libraries.
+Then specifically set the paths in the build command file for your project.
+</p>
+<p>The Xalan-C and Xerces-C libraries do not use the Microsoft Framework,
+the "mfc" and the "atl" directives. Microsoft is deprecating their "mfc"
+Microsoft Foundation Classes.
+</p>
+<p>Define the necessary environment variables for building the Xalan-C/C++ libraries and sample programs.
+</p>
+<blockquote class="source">
+<pre>
+SET PATH=%PATH%;%XERCESCROOT%\bin
+
+SET INCLUDE=%INCLUDE%;%XERCESCROOT%\include;%XERCESCROOT%\src
+SET INCLUDE=%INCLUDE%;%XALANCROOT%\src
+
+SET LIB=%LIB%;%XERCESCROOT%\lib
+</pre>
+</blockquote>
+<p>If you are going to build for IBM-ICU support, then add the following environments.
+</p>
+<blockquote class="source">
+<pre>
+SET ICUROOT="path to ibm-icu installation"
+
+SET PATH=%PATH%;%ICUROOT%\bin
+SET INCLUDE=%INCLUDE%;%ICUROOT%\include
+SET LIB=%LIB%;%ICUROOT%\lib;%ICUROOT%\data
+</pre>
+</blockquote>
+<p>Now we should be ready to start the Microsoft Visual Studio .NET using our custom environment using the <code>%XALANCBUILDSLN%</code> solution.
+</p>
+<blockquote class="source">
+<pre>
+devenv.exe "%XALANCBUILDSLN%" /useenv
+</pre>
+</blockquote>
+
+<a name="winbldinst"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Installing the Xalan Library on Windows</h4>
+
+<p>The following command script will install the binary and header files to a target directory that is compatible with the XALANCROOT environment variable for creating applications. Environment variables other than XALANCTARGET are defined in the previous section, the <a href="#winbldcmd">Visual Studio .NET build example</a>.
+</p>
+<blockquote class="source">
+<pre>
+SET XALANCTARGET="path-to-target-directory"
+
+MKDIR "%XALANCTARGET%\bin"
+MKDIR "%XALANCTARGET%\include"
+MKDIR "%XALANCTARGET%\lib"
+
+CD "%XALANCBUILDDIR%\Release\Nls"
+COPY *.hpp "%XALANCTARGET%"\include
+
+CD "%XALANCBUILDDIR%\Release"
+COPY *.DLL "%XALANCTARGET%\bin"
+COPY *.LIB "%XALANCTARGET%\lib"
+COPY *.EXP "%XALANCTARGET%\lib"
+
+CD "%XALANCBUILDDIR%\Debug"
+COPY *.DLL "%XALANCTARGET%\bin"
+COPY *.PDB "%XALANCTARGET%\bin"
+COPY *.LIB "%XALANCTARGET%\lib"
+COPY *.EXP "%XALANCTARGET%\lib"
+
+CD "%XALANCROOT%\src
+XCOPY xalanc\*.hpp "%XALANCTARGET%\include\xalanc" /E /C /I /R /Y
+XCOPY xalanc\*.h "%XALANCTARGET%\include\xalanc" /E /C /I /R /Y
+</pre>
+</blockquote>
+
+<a name="unixbldenv"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>UNIX Build Environment</h3>
+
+<p>I don't like building sources using root or superuser login. I like to do builds in a directory separated from the source tree. A debug build and release build will create shared objects of the same name. I like to target these builds to separate directory trees.
+</p>
+<p>Release builds are targeted at the <code>/usr/local</code> file system.
+</p>
+<p>Debug builds are targeted at the <code>/opt/apache/debug</code> file system.
+</p>
+<p>Source trees are referenced wherever convenient. Using the (<code>--srcdir</code>) configuration parameter allows the source tree to be separate from the build tree. The source tree can even reside on read-only media.
+</p>
+<p>Product builds are done in a build directory path separate from the source tree. This is the working directory from where you perform your builds and installs.
+</p>
+<p>
+<b>Source Trees:</b> (<code>--srcdir</code>) configuration parameter
+</p>
+<p>
+ <code>/opt/xerces/c/<trunk>/</code><the Xerces-C/C++ XML parser library source distribution>
+<br />
+ <code>/opt/xalan/c/<trunk></code>/<the Xalan-C/C++ XSLT library source distribution>
+</p>
+<p>If the source distribution is well-constructed, the source directory trees can be read-only.
+</p>
+<p>
+<b>Binary Installation Trees:</b> (<code>--prefix</code>) configuration parameter
+</p>
+<p>
+ <code>/usr/local/</code> <the target for the
+release binary installation>
+<br />
+ <code>./bin</code> The sample programs
+<br />
+ <code>./lib</code> The shared and static library files
+<br />
+ <code>./include</code> The library header files
+<br />
+<br />
+ <code>/opt/apache/debug/</code> <the target for the
+debug binary installation>
+<br />
+ <code>./bin</code> The sample programs
+<br />
+ <code>./lib</code> The shared and static library files
+<br />
+ <code>./include</code> The library header files
+</p>
+
+<p>The default (<code>--prefix</code>) value is <code>/usr/local</code> which I use for release builds.
+</p>
+<p>I choose (<code>--prefix</code>) value of <code>/opt/apache/debug</code> for debug builds.
+</p>
+
+<p>
+<b>Build Tree:</b> The build working directory tree
+</p>
+<p> <code>/<user-directory>/Build/</code>
+</p>
+
+<p>You can use any empty file system or directory path with write access. Starting with an empty directory is a quick way to do a clean build. Make this empty directory to be your current working directory.
+</p>
+<p>I also like to make some shell scripts so that the build process can be automated. I locate these scripts outside of the Build directory so they don't get lost when I purge directory content.
+</p>
+<p>
+ <code>../build-xerces-lib.sh</code>
+</p>
+<p>
+ <code>../build-xalan-lib.sh</code>
+</p>
+<p>
+ <code>../build-xalan-app.sh</code>
+</p>
+<p>I generate these shell scripts with a text editor and use them to minimize keyboard typing errors.
+</p>
+<a name="unixlibpath"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Finding Runtime Libraries</h4>
+
+<p>The various types of UNIX operating systems have differing requirements for finding libraries at runtime.
+</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">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">Mac OS X</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 Xalan-C/C++ and Xerces-C/C++ shared library objects must be installed in a reachable library path for your platform. The <code>make</code> step creates the libraries in the <code>lib</code> subdirectory of your working directory. The <code>make install</code> step installs these shared objects to the designated <code>{prefix}/lib</code> directory or another directory defined by the <code>--libdir</code> configuration parameter.
+</p>
+<p>In many cases, the <code>/usr/local/lib</code> is already cached in <code>/etc/ld.so.cache</code> or included by <code>/etc/ld.so.conf</code>. The library path environment variable is then used for exceptions. The explicit library path environment variable usually takes precedence over the other methods of finding shared library runtimes. This is useful if you wish to use a debug environment on the same platform that also includes release libraries of the same name.
+</p>
+
+
+<a name="unixbldxalan"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Building the Xalan-C/C++ XSLT Libraries for UNIX</h4>
+
+
+<p>I don't like building sources from a root or superuser login. I also like to do builds in a directory separated from the source tree.
+</p>
+
+<p>If your sources tree is read-only and some required files are not executable, then you need to copy the source to writable media and change the execute attributes of specific files. This command sequence will copy an entire directory tree from <code>{source-dir}</code> to <code>{dest-dir}</code>.
+</p>
+<blockquote class="source">
+<pre>
+ cd {source-dir}
+ find . | cpio -pdmuv {dest-dir}
+</pre>
+</blockquote>
+<p>Connect to the <code>{xalan-src}</code> directory and make specific files executable.
+</p>
+<blockquote class="source">
+<pre>
+ cd {xalan-src}
+ chmod 755 runConfigure configure install-sh
+</pre>
+</blockquote>
+<p>Connect to your empty build directory and construct a script for building the Xalan-C/C++ XSLT products.
+</p>
+
+<p>The Xalan-C/C++ configuration process uses the <code>runConfigure</code> script as a front-end to the automake <code>configure</code> script. Your shell command script should therefore use the <code>runConfigure</code> script.
+</p>
+
+<table border="1">
+<tr>
+<th class="content" rowspan="1" colspan="2">runConfigure Options</th>
+</tr>
+<tr>
+<th class="content" rowspan="1" colspan="1">Option</th>
+<th class="content" rowspan="1" colspan="1">Description</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-p</td>
+<td class="content" rowspan="1" colspan="1">Build platform: aix, linux, freebsd, netbsd, solaris, hp-10, hp-11, hp11-ia64,
+ irix, tru64, macosx, cygwin</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-c</td>
+<td class="content" rowspan="1" colspan="1">C compiler name: gcc, cc, c89, xlc, xlc_r, acc (default = gcc)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-x</td>
+<td class="content" rowspan="1" colspan="1">C++ compiler name: g++, CC, C89, xlC, xlC_r, aCC (default = g++)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-d</td>
+<td class="content" rowspan="1" colspan="1">Indicates a debug build, takes no values, default is No Debug</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-t</td>
+<td class="content" rowspan="1" colspan="1">Transcoder to use: 'icu', (Default is null, the Xerces-C/C++ transcoder)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-m</td>
+<td class="content" rowspan="1" colspan="1">Type of localization support: inmem, icu, nls (default is inmem)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-M</td>
+<td class="content" rowspan="1" colspan="1">Locale for message localization: "en_US"</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-r</td>
+<td class="content" rowspan="1" colspan="1">Threads option: pthread, dce (default is pthread)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-b</td>
+<td class="content" rowspan="1" colspan="1">Specify 32 or 64 bit build (Default is 32-bit)<br />
+ On Linux, the 32/64 build is determined by the compiler, kernel, and glibc.</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-P</td>
+<td class="content" rowspan="1" colspan="1">Install root directory: value is assigned to the <code>--prefix</code> configure parameter</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-l</td>
+<td class="content" rowspan="1" colspan="1">Extra link options (assigned to <code>LDFLAGS</code>)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-z</td>
+<td class="content" rowspan="1" colspan="1">Extra compiler options (assigned to <code>CFLAGS</code> and <code>CXXFLAGS</code>)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-C</td>
+<td class="content" rowspan="1" colspan="1">Extra configuration options (i.e. <code>--srcdir=${SourceDir}</code>)</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">-h</td>
+<td class="content" rowspan="1" colspan="1">Print the <code>runConfigure</code> help and exit</td>
+</tr>
+</table>
+
+<p>Here are the names of some C/C++ compilers associated with commercial UNIX operating systems used to build Xalan-C/C++ and Xerces-C/C++ packages.
+</p>
+
+<table border="1">
+<tr>
+<th class="content" rowspan="1" colspan="1">System</th>
+<th class="content" rowspan="1" colspan="1">Platform</th>
+<th class="content" rowspan="1" colspan="1">C Compiler</th>
+<th class="content" rowspan="1" colspan="1">C++ Compiler</th>
+<th class="content" rowspan="1" colspan="1">Comment</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">AIX</td>
+<td class="content" rowspan="1" colspan="1">aix</td>
+<td class="content" rowspan="1" colspan="1">xlc_r</td>
+<td class="content" rowspan="1" colspan="1">xlC_r</td>
+<td class="content" rowspan="1" colspan="1">thread support</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">AIX</td>
+<td class="content" rowspan="1" colspan="1">aix</td>
+<td class="content" rowspan="1" colspan="1">xlc</td>
+<td class="content" rowspan="1" colspan="1">xlC</td>
+<td class="content" rowspan="1" colspan="1">no thread support</td>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">Cygwin</td>
+<td class="content" rowspan="1" colspan="1">cygwin</td>
+<td class="content" rowspan="1" colspan="1">gcc</td>
+<td class="content" rowspan="1" colspan="1">g++</td>
+<td class="content" rowspan="1" colspan="1" />
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">HP-UX</td>
+<td class="content" rowspan="1" colspan="1">hp-11</td>
+<td class="content" rowspan="1" colspan="1">cc</td>
+<td class="content" rowspan="1" colspan="1">aCC</td>
+<td class="content" rowspan="1" colspan="1" />
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">HP-UX</td>
+<td class="content" rowspan="1" colspan="1">hp-11-ia64</td>
+<td class="content" rowspan="1" colspan="1">cc</td>
+<td class="content" rowspan="1" colspan="1">aCC</td>
+<td class="content" rowspan="1" colspan="1" />
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="1">Solaris</td>
+<td class="content" rowspan="1" colspan="1">solaris</td>
+<td class="content" rowspan="1" colspan="1">cc</td>
+<td class="content" rowspan="1" colspan="1">CC</td>
+<td class="content" rowspan="1" colspan="1" />
+</tr>
+</table>
+
+<p>The following example shows you how to construct a usable script with your favorite text editor.
+</p>
+
+<blockquote class="source">
+<pre>
+#!/bin/sh
+# Script to build and install Xalan-C/C++ products from sources
+
+# The Source and Target Directories for Debug Build
+
+# SourceDir="--srcdir=/opt/xalan/c/trunk"
+# DestDir="--prefix=/opt/apache/debug"
+
+# The Source and Target Directories for Release Build
+
+SourceDir="--srcdir=/opt/xalan/c/trunk"
+DestDir="--prefix=/usr/local"
+
+# The Xerces and Xalan package directories
+
+export XALANCROOT=${SourceDir}
+export XERCESCROOT=${DestDir}
+
+# If compiling with IBM-ICU support, the ICUROOT environment variable
+# needs to be defined to specify where the ICU libraries are installed.
+# Specifically, the following directories are accessed:
+# ${ICUROOT}/lib, ${ICUROOT}/include, ${ICUROOT}/data
+# export ICUROOT=/usr/local
+
+export PATH=$PATH:${SourceDir}
+
+# Debug Configure
+
+# runConfigure -p linux -d -c gcc -x g++ -P "${DestDir}" \
+# -C "--srcdir=${SourceDir}"
+
+# Release Configure
+
+runConfigure -p linux -c gcc -x g++ -P "${DestDir}" \
+ -C "--srcdir=${SourceDir}"
+
+# Connect to configured src subdirectory to build the library without
+# sample programs. If you run make from your build directory, then the
+# library and all sample programs will be built.
+
+cd src
+make clean
+make
+
+# As a user with permissions to write to ${DestDir} install the Xalan-C/C++ products
+# ${DestDir}/bin the Xalan command-line utility and sample programs
+# ${DestDir)/lib the Xalan-C/C++ static and dynamic libraries
+# ${DestDir}/include/xalanc/* The header files.
+
+make install
+
+## End of sample build script.
+</pre>
+</blockquote>
+
+
+
+<a name="unixcompileref"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Reference on Unix Platforms and C++ Compilers</h3>
+
+<p>Some compilers and platforms may need configuration options and variables that differ from the default Linux build. Beware that the runConfigure script for Xalan-C/C++ is a front-end that calls the configure script. The following table is reference information for the build of Xerces-C/C++ version 3.x. The C++ compiler for Xerces should be the same as used for Xalan builds.
+</p>
+
+<table border="1">
+<tr>
+<th class="content" rowspan="1" colspan="2">Configuration Options For Unix Platforms</th>
+</tr>
+<tr>
+<th class="content" rowspan="1" colspan="1">Solaris x86</th>
+<th class="content" rowspan="1" colspan="1">Sun CC</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure CXX=CC CC=cc</td>
+</tr>
+
+<tr>
+<th class="content" rowspan="1" colspan="1">Solaris x86-64</th>
+<th class="content" rowspan="1" colspan="1">Sun CC</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure CXX=cc CC=cc CFLAGS=-xarch=amd64 CXXFLAGS=-xarch=amd64<br />
+(newer Sun CC versions use -m64 instead of -arch=amd64)</td>
+</tr>
+
+<tr>
+<th class="content" rowspan="1" colspan="1">Solaris Sparc</th>
+<th class="content" rowspan="1" colspan="1">Sun CC</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure CXX=CC CC=cc</td>
+</tr>
+
+<tr>
+<th class="content" rowspan="1" colspan="1">Solaris Sparc v9</th>
+<th class="content" rowspan="1" colspan="1">Sun CC</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure CXX=cc CC=cc CFLAGS=-xarch=v9 CXXFLAGS=-xarch=v9<br />
+(newer Sun CC versions use -m64 instead of -arch=v9)</td>
+</tr>
+
+<tr>
+<th class="content" rowspan="1" colspan="1">AIX PowerPC</th>
+<th class="content" rowspan="1" colspan="1">IBM XLC++</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure CXX=xlc_r CC=xlc_r<br />
+gmake libxerces_c_1a LDFLAGS=-qmkshrobj</td>
+</tr>
+
+<tr>
+<th class="content" rowspan="1" colspan="1">AIX PowerPC-64</th>
+<th class="content" rowspan="1" colspan="1">IBM XLC++</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure CXX=xlc_r CC=xlc_r CXXFLAGS=-q64 CFLAGS=-q64<br />
+gmake libxerces_c_1a LDFLAGS=-qmkshrobj</td>
+</tr>
+
+<tr>
+<th class="content" rowspan="1" colspan="1">HP-UX 1a-64-32</th>
+<th class="content" rowspan="1" colspan="1">HP aCC</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure CXX=aCC CC=aCC CFLAGS=-mt CXXFLAGS=-mt LDFLAGS=-mt</td>
+</tr>
+
+<tr>
+<th class="content" rowspan="1" colspan="1">HP-UX 1a-64</th>
+<th class="content" rowspan="1" colspan="1">HP aCC</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure CXX=aCC CC=aCC CFLAGS=-mt CXXFLAGS=-"mt +DD64" LDFLAGS="-mt +DD64"</td>
+</tr>
+
+<tr>
+<th class="content" rowspan="1" colspan="1">Mac OS X x86-64</th>
+<th class="content" rowspan="1" colspan="1">GCC</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure CFLAGS="-arch x86_64" CXXFLAGS="-arch x86_64"</td>
+</tr>
+
+<tr>
+<th class="content" rowspan="1" colspan="1">Mac OS X PowerPC-64</th>
+<th class="content" rowspan="1" colspan="1">GCC</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure CFLAGS="-arch ppc64" CXXFLAGS="-arch ppc64"</td>
+</tr>
+
+<tr>
+<th class="content" rowspan="1" colspan="1">Mac OS X x86/PowerPC</th>
+<th class="content" rowspan="1" colspan="1">GCC</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure --disable-dependency-tracking CFLAGS="arch i386 -arch ppc"<br />
+CXXFLAGS="-arch i386 -arch ppc"</td>
+</tr>
+
+<tr>
+<th class="content" rowspan="1" colspan="1">MinGW x86</th>
+<th class="content" rowspan="1" colspan="1">GCC</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure LDFLAGS=-no-undefined</td>
+</tr>
+
+<tr>
+<th class="content" rowspan="1" colspan="1">Cygwin x86</th>
+<th class="content" rowspan="1" colspan="1">GCC</th>
+</tr>
+<tr>
+<td class="content" rowspan="1" colspan="2">./configure LDFLAGS=-no-undefined</td>
+</tr>
+</table>
+
+
+<a name="xercesmodules"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Xerces-C/C++ Transcoders and Plug-in Modules</h3>
+<p>Xerces-C/C++ XML Parsers have undergone some additional modularity features. In the version 3 series, the transcoders are now being implemented as runtime modules. Use of the transcoding modules is still experimental for Xalan-C/C++ transformation applications. The basic transcoder capability still exists. Xerces-C/C++ version 2 series had transcoder libraries explicitly built and installed.
+</p>
+<p>A plug-in memory management architecture was introduced in Xerces-C/C++ version 2.7. The plug-in memory management of Xerces-C/C++ is also supported by Xalan-C/C++ applications.
+</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 - Tue 2012-10-09</div>
+</div>
+</body>
+</html>
diff --git a/docs/xalan/xalan-c/charter.html b/docs/xalan/xalan-c/charter.html
index e77847a..8eccb5f 100644
--- a/docs/xalan/xalan-c/charter.html
+++ b/docs/xalan/xalan-c/charter.html
@@ -1,488 +1,488 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html>
-<head>
-<title>ASF: Xalan Project Charter</title>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
-</head>
-<!--
- * 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.
- -->
-<body>
-<div id="title">
-<table class="HdrTitle">
-<tbody>
-<tr>
-<th rowspan="2">
-<a href="../index.html">
-<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
-</a>
-</th>
-<th text-align="center" width="75%">
-<a href="index.html">Xalan-C/C++ Version 1.11</a>
-</th>
-</tr>
-<tr>
-<td valign="middle">Xalan Project Charter</td>
-</tr>
-</tbody>
-</table>
-<table class="HdrButtons" align="center" border="1">
-<tbody>
-<tr>
-<td>
-<a href="http://www.apache.org">Apache Foundation</a>
-</td>
-<td>
-<a href="http://xalan.apache.org">Xalan Project</a>
-</td>
-<td>
-<a href="http://xerces.apache.org">Xerces Project</a>
-</td>
-<td>
-<a href="http://www.w3.org/TR">Web Consortium</a>
-</td>
-<td>
-<a href="http://www.oasis-open.org/standards">Oasis Open</a>
-</td>
-</tr>
-</tbody>
-</table>
-</div>
-<div id="navLeft">
-<ul>
-<li>
-<a href="resources.html">Resources</a>
-<br />
-</li>
-<li>
-<a href="../index.html">Home</a>
-</li></ul><hr /><ul>
-<li>
-<a href="index.html">Xalan-C++ 1.11</a>
-</li>
-<li>
-<a href="whatsnew.html">What's New</a>
-</li>
-<li>
-<a href="license.html">Licenses</a>
-</li></ul><hr /><ul>
-<li>
-<a href="overview.html">Overview</a>
-</li>
-<li>Charter<br />
-</li></ul><hr /><ul>
-<li>
-<a href="download.html">Download</a>
-</li>
-<li>
-<a href="buildlibs.html">Build Libraries</a>
-</li>
-<li>
-<a href="install.html">Installation</a>
-</li>
-<li>
-<a href="builddocs.html">Build Documents</a>
-</li></ul><hr /><ul>
-<li>
-<a href="samples.html">Sample Apps</a>
-</li>
-<li>
-<a href="commandline.html">Command Line</a>
-</li>
-<li>
-<a href="usagepatterns.html">Usage Patterns</a>
-</li></ul><hr /><ul>
-<li>
-<a href="programming.html">Programming</a>
-</li>
-<li>
-<a href="extensions.html">Extensions</a>
-</li>
-<li>
-<a href="extensionslib.html">Extensions Library</a>
-</li>
-<li>
-<a href="apiDocs/index.html">API Reference</a>
-</li></ul><hr /><ul>
-<li>
-<a href="faq.html">Xalan-C FAQs</a>
-</li></ul><hr /><ul>
-<li>
-<a href="whatsnew.html#bugs">Bugs</a>
-</li>
-<li>
-<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
-</li>
-<li>
-<a href="secureweb.html">Web Security</a>
-</li>
-</ul>
-</div>
-<div id="content">
-<h2>Xalan Project Charter</h2>
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Xalan Project Charter</h3>
- <p>The following charter applies to all Xalan projects.</p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>1 INTRODUCTION</h3>
- <p>1.1 Apache Xalan is a collaborative software development project
- dedicated to providing robust, full-featured, commercial-quality, and
- freely available XSLT support on a wide variety of platforms. This
- project is managed in cooperation with various individuals worldwide
- (both independent and company-affiliated experts), who use the
- Internet to communicate, plan, and develop XSLT software and related
- documentation.</p>
- <p>1.2 This charter briefly describes the mission, history, organization
- and processes of the project.</p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>2 MISSION</h3>
- <p>2.1 Apache Xalan exists to promote the use of XSLT. We view XSLT
- (Extensible Stylesheet Language Transformations) as a compelling
- paradigm that transforms XML documents, thereby facilitating the
- exchange, transformation, and presentation of knowledge. The ability
- to transform XML documents into usable information has great potential
- to improve the functionality and use of information systems. We intend
- to build freely available XSLT processing components in order to
- engender such improvements.</p>
- <p>2.2 Apache Xalan consists of a set of components that transform XML
- documents. Where appropriate, these components plug into other XML
- components using standard APIs (formal, de facto, or proposed). The
- components must be high performance, reliable, and easy to use. Where
- inter-related, the components must be part of an underlying architectural
- orchestration that will allow them to work together without major
- negotiations or breakage.</p>
- <p>2.3 We believe that the best way to define this XML transformation
- architecture is by having both individuals and corporations
- collaborate on the best possible infrastructure, APIs, code, testing,
- and release cycles. Components must be vendor neutral and usable as
- core components for all.</p>
- <p>2.4 In order to achieve a coherent architecture between Apache Xalan
- components and other components and applications, standards (formal or
- de facto) will be used as much as possible for both protocols and
- APIs. Where appropriate, experiences and lessons learned will be fed
- back to standards bodies in an effort to assist in the development of
- those standards. We will also encourage the innovation of new
- protocols, APIs, and components in order to seed new concepts not
- yet defined by standards.</p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>3 HISTORY</h3>
- <p>3.1 This project was established under the direction of the Apache
- Software Foundation in October 2004 to facilitate joint open-source
- development. Prior to October 2004 this project was a subproject
- of the Apache XML project.</p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>4 TERMS</h3>
- <p>4.1 The ASF Board. The management board of the Apache Software
- Foundation.</p>
- <p>4.2 The Project. The Apache Xalan project; intended to refer to the
- source code, website, subprojects, and community that are Apache Xalan.</p>
- <p>4.3 Subproject. The Apache Xalan project may have subprojects; a
- subproject is responsible for a component or application whose scope
- is well defined.</p>
- <p>4.4 Product. Some deliverable (usually a binary or source package)
- that a subproject makes available to the public. Subprojects may have
- multiple products.</p>
- <p>4.5 Release. A specific version of a product. Subprojects may have
- multiple releases of a given product.</p>
- <p>4.6 Contributor. Anyone who makes a contribution to the development
- of the Apache Xalan project.</p>
- <p>4.7 Committer. The Apache Xalan project has a set of committers.
- Committers are contributors who have read/write access to the source
- code repository.</p>
- <p>4.8 PMC. The PMC (Project Management Committee) is the group of people
- that form the entity that makes decisions and controls the project.
- Individual people or committers do not control the project.</p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>5 THE PROJECT MANAGEMENT COMMITTEE</h3>
- <p>5.1 The Apache Xalan project is managed by a core group of committers
- known as the Project Management Committee [PMC]. Subprojects, if any,
- much each have at least one representative committer on the PMC.</p>
- <p>5.2 The activities of the PMC are coordinated by the Chairperson,
- who is an officer of the corporation and reports to the Apache
- Board. The Chairperson will, on the request of the Apache Board,
- provide reports to the Board on issues related to the running of
- the Apache Xalan project.</p>
- <p>5.3 The PMC has the following responsibilities:</p>
- <p>a) Accepting new subproject proposals, formally submitting these
- proposals for Apache Xalan committer vote, and creating the subproject
- (see SUBPROJECTS below). This is done in collaboration with the
- Incubator (see <a href="http://incubator.apache.org">http://incubator.apache.org</a>).</p>
- <p>b) Facilitating code or other donations by individuals or companies,
- in collaboration with the Incubator.</p>
- <p>c) Resolving license issues and other legal issues in conjunction with
- the ASF board.</p>
- <p>d) Ensuring that administrative and infrastructure work is completed.</p>
- <p>e) Facilitating relationships among projects and subprojects.</p>
- <p>f) Facilitating relationships between the Apache Xalan project and the
- external world.</p>
- <p>g) Overseeing Apache Xalan to ensure that the mission defined in this
- document is being fulfilled.</p>
- <p>h) Resolving conflicts within the project.</p>
- <p>i) Reporting to the ASF board (through the Chair) on the progress
- of the project.</p>
- <p>j) Propose new releases of projects or subprojects. Such proposals pass
- if 75% of the PMC members vote in agreement.</p>
-
- <p>5.4 A contributor can, at any time, nominate a committer to be on the PMC,
- by calling for a vote. If two thirds, or more, of the active committers
- vote in agreement then the nomination is given to the PMC. The person
- becomes a new PMC member if 75% or more of the PMC members vote in
- agreement, with no dissenting votes among the PMC members. This individual
- should be elected based on merit for the evolution of the project and
- demonstration of commitment.</p>
- <p>5.5 In cases where the subproject is unable to directly provide a
- representative on the PMC, another member of the PMC will be required to
- represent that subproject on the PMC. This will be strongly discouraged.
- It is preferable that all subprojects have direct representation on the
- PMC.</p>
- <p>5.6 At least every twelve months, or more often if directed by the ASF
- board, the PMC members will elect a Chairperson from among themselves;
- the person with the most votes from the other PMC members is recommended
- to the ASF board for the position of Chairperson, and with the ASF board's
- approval, becomes the Chairperson for the new term.</p>
- <p>5.7 Upon agreement by the Apache Board, the recommended Chairperson will,
- if they are not already, be appointed an officer of the corporation. See
- <a href="http://www.apache.org/foundation/bylaws.html">
- http://www.apache.org/foundation/bylaws.html</a> for more information.</p>
- <p>5.8 The PMC is responsible for maintaining and updating this charter.
- Development must follow the process outlined below, so any change to the
- development process necessitates a change to the charter. Proposed changes
- to this charter by the PMC are passed if 75% or more of the PMC members
- approve the proposal, with no dissenting votes. However, an active Apache
- Xalan committer may challenge the change.</p>
- <p>5.9 An active Apache Xalan committer may challenge a change to this charter
- proposed by the PMC within two weeks of its proposal. When challenged the
- proposed change is passed if within two weeks of the challenge the active
- committers approve the change with a two-thirds majority vote.</p>
- <p>5.10 The PMC ultimately makes the decisions for the project, not the individual
- people. At any time the PMC can reject patches or other contributions to the
- project if 75% or more of the PMC members vote to reject the contribution.</p>
- <p>5.11 A PMC member may resign their membership at any time. However, in the
- unlikely event that a member of the PMC becomes disruptive to the process,
- such as ceasing to take part in PMC votes, the PMC member may be removed from
- the PMC by a vote among the other PMC members. The PMC member is removed if
- 75% or more of the other PMC members approve the removal, with no dissenting
- votes among the other PMC members.</p>
- <p>5.12 A person remains a PMC member until he or she resigns, is removed by a
- vote from among the other PMC members, dies or is incapacitated.</p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>6 SUBPROJECTS</h3>
- <p>6.1 A subproject of the Apache Xalan project is responsible for a component
- or application whose scope is well defined. Each subproject has its own set
- of developers, and is responsible for approving its own committers. Apache
- Xalan is composed of subprojects which fit into one of two categories:</p>
- <p>(a) An XSLT processor implementation in some particular programming
- language. There may be multiple processors for a given language if
- the API's the processors support are sufficiently dissimilar. At the
- time of writing, there is one processor for C++ and two for Java.</p>
- <p>(b) A set of components which are used in related applications and are
- tightly bound, usually through internal API's, to one (or more) of the
- processor subprojects.</p>
- <p>6.2 A new subproject proposal is submitted to the PMC, and then accepted
- by a majority Apache Xalan project active committer vote within two weeks
- after the proposal.</p>
- <p>6.3 Each subproject must have a set of requirements as well as an
- up-to-date release plan and design document on its dedicated web page.</p>
- <p>6.4 It is recommended that each subproject have a smoke-test system
- that works at least as a basic integration test.</p>
- <p>6.5 A subproject may be removed if 75% or more of the PMC members approve
- the proposal, there are no dissenting votes among the PMC members,
- and no challenges by active Apache Xalan project committers
- within two weeks after the proposal.
- A contributor may challenge the proposed removal
- of a subproject within two weeks of the proposal.
- In this case the proposed removal is passed if within two weeks of the
- challenge the active committers approve the removal with a two-thirds
- majority vote. Any subproject removal is subject to the approval of the
- ASF board.</p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>7 CONTRIBUTORS</h3>
- <p>7.1 Like all Apache projects, the Apache Xalan project is a
- meritocracy -- the more work you do, the more you are allowed to do.</p>
- <p>7.2 People who make regular and substantial contributions may become
- committers as described below. Contributions include: participating in
- mailing lists, reporting issues or bugs in issue-records in the Issue Database,
- providing patches, and proposing changes to a product.</p>
- <p>7.3 In order to ensure that all code contained in the Apache Xalan
- project's code repository is free of licensing, intellectual property and patent
- issues, any person wishing to contribute a new feature to Apache Xalan must either
- sign:</p>
- <p>a) If contributing as an individual, sign the "Individual
- Contributor License Agreement (CLA)"
- (<a href="http://www.apache.org/licenses/icla.txt">http://www.apache.org/licenses/icla.txt</a>)
- and file a copy with the Secretary of the Corporation; or </p>
- <p>b) If making the contribution as part of their employment
- responsibilities, sign the "Corporate CLA (CCLA)",
- (<a href="http://www.apache.org/licenses/cla-corporate.txt">http://www.apache.org/licenses/cla-corporate.txt</a>)
- and file a copy with the Secretary of the Corporation.</p>
- <p>7.4 If the contribution in question is a small bugfix, the contributor need
- not sign a CLA, but need only provide the following information, attaching
- it to the communication containing the patch:</p>
- <p>a) Name and employer</p>
- <p>b) Are you the author of the code being contributed?</p>
- <p>c) Do you have the right to grant the copyright and patent
- licenses for the contribution that are set forth in the ASF v.2.0
- license (<a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)?</p>
- <p>d) Does your employer have any rights to code that you have
- written, for example, through your contract for employment? If
- so, has your employer given you permission to contribute the code
- on its behalf or waived its rights in the code?</p>
- <p>e) Are you aware of any third-party licenses or other
- restrictions (such as related patents or trademarks) that could
- apply to your contribution? If so, what are they?</p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>8 COMMITTERS</h3>
- <p>8.1 The Apache Xalan project has a set of committers. If there
- are subprojects, each subproject will also have a set of committers.
- Committers are contributors who have read/write access to the source code
- repository. New committers are added when a contributor is nominated by a
- committer and approved by at least 50 percent of the active committers for
- that subproject with no opposing votes. In most cases, new committers will
- already be participating in the development process by submitting suggestions
- and/or fixes via issue-records in the Issue Database or mailing lists.</p>
- <p>8.2 For the purposes of voting, committers will be classed as "active" or
- "inactive". Only active committers will be included in the totals used to
- determine the success or failure of a particular vote.</p>
- <p>8.3 Committers remain active as long as they are contributing code or
- posting to the project or subproject mailing lists. If a committers has
- neither contributed code nor posted to the mailing lists in 3
- months, a member of the PMC will e-mail the committer,
- the project or subproject development list, and the PMC mailing list
- notifying the committer that they are now in inactive status.</p>
- <p>8.4 An inactive status will not prevent a committer committing new code
- changes or posting to the mailing lists. Either of these activities will
- automatically re-activate the committer for the purposes of voting.</p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>9 INFRASTRUCTURE</h3>
- <p>9.1 The Apache Xalan project relies on the Apache XML project
- and the Apache Infrastructure project for the following:</p>
- <p>a) Issue Database -- This is a system with issue-records,
- for tracking bugs, issues, features and requests.</p>
- <p>b) Repository -- The xalan.apache.org project has its set
- of parts that make up the software, and these parts are
- managed in a repository. Committers make changes to the source code,
- documentation and other associated parts that are stored in
- the repository. Any subproject will have its set of committers
- for its repository.</p>
- <p>c) Website -- The website <a href="http://xalan.apache.org">xalan.apache.org</a>
- will contain information about the Apache Xalan project and its subprojects,
- including documentation, downloads of releases, and this charter.</p>
- <p>d) Mailing Lists -- appropriate mailing lists will be created
- at the discretion of the PMC. Such mailing lists could
- for example include: a PMC mailing list, a general mailing list,
- project or subproject public developer mailing lists,
- project or subproject public user mailing lists.</p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>10 LICENSING</h3>
- <p>10.1 All contributions to the Apache Xalan project adhere to the "Apache
- Software Foundation License, Version 2.0"
- (<a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>).
- All further contributions, including patches, must be made under the same terms.</p>
- <p>10.2 When a committer is considering integrating a contribution
- from a contributor who has no CLA on file with the Corporation,
- it is the responsibility of the committer, in consultation with
- the PMC, to conduct due diligence on the pedigree of the
- contribution under consideration; see sections 7.3 and 7.4. </p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>11 THE DEVELOPMENT PROCESS</h3>
- <p>11.1 For a committer to commit a change to the MAIN branch of the
- repository an issue-record must be opened in the "Issue Database"
- to track the change. The status of the issue must be kept up to date.</p>
- <p>11.2 No voting is required to commit changes, but one other active
- committer must review the changes. Before the changes are committed, the reviewer
- must add a comment in the corresponding issue-record indicating that
- they have reviewed and approve the changes.</p>
- <p>11.3 Issue-records and reviews are not required for committing changes to
- other experimental branches (not the MAIN branch) in a repository.</p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>12 VOTING</h3>
- <p>12.1 Unless otherwise stated in this mission, votes cast on Apache Xalan
- proposals must be made within two weeks of the proposal. A challenge to
- a proposal must also be made within two weeks of the proposal. Likewise,
- votes cast on challenges must be cast within two weeks of the challenge.</p>
-
-
- <p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>13 RELATIONSHIP TO OTHER APACHE PROJECTS</h3>
- <p>13.1 The Apache Xalan project should work closely with other Apache
- projects, such as Xerces and XML, to avoid redundancy
- and achieve a coherent architecture among Apache Xalan and these
- projects.</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 2012-10-07</div>
-</div>
-</body>
-</html>
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Xalan Project Charter</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * 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.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan-C/C++ Version 1.11</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Xalan Project Charter</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="../index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-C++ 1.11</a>
+</li>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="license.html">Licenses</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>Charter<br />
+</li></ul><hr /><ul>
+<li>
+<a href="download.html">Download</a>
+</li>
+<li>
+<a href="buildlibs.html">Build Libraries</a>
+</li>
+<li>
+<a href="install.html">Installation</a>
+</li>
+<li>
+<a href="builddocs.html">Build Documents</a>
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>
+<a href="commandline.html">Command Line</a>
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="programming.html">Programming</a>
+</li>
+<li>
+<a href="extensions.html">Extensions</a>
+</li>
+<li>
+<a href="extensionslib.html">Extensions Library</a>
+</li>
+<li>
+<a href="apiDocs/index.html">API Reference</a>
+</li></ul><hr /><ul>
+<li>
+<a href="faq.html">Xalan-C FAQs</a>
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html#bugs">Bugs</a>
+</li>
+<li>
+<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
+</li>
+<li>
+<a href="secureweb.html">Web Security</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<h2>Xalan Project Charter</h2>
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Xalan Project Charter</h3>
+ <p>The following charter applies to all Xalan projects.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>1 INTRODUCTION</h3>
+ <p>1.1 Apache Xalan is a collaborative software development project
+ dedicated to providing robust, full-featured, commercial-quality, and
+ freely available XSLT support on a wide variety of platforms. This
+ project is managed in cooperation with various individuals worldwide
+ (both independent and company-affiliated experts), who use the
+ Internet to communicate, plan, and develop XSLT software and related
+ documentation.</p>
+ <p>1.2 This charter briefly describes the mission, history, organization
+ and processes of the project.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>2 MISSION</h3>
+ <p>2.1 Apache Xalan exists to promote the use of XSLT. We view XSLT
+ (Extensible Stylesheet Language Transformations) as a compelling
+ paradigm that transforms XML documents, thereby facilitating the
+ exchange, transformation, and presentation of knowledge. The ability
+ to transform XML documents into usable information has great potential
+ to improve the functionality and use of information systems. We intend
+ to build freely available XSLT processing components in order to
+ engender such improvements.</p>
+ <p>2.2 Apache Xalan consists of a set of components that transform XML
+ documents. Where appropriate, these components plug into other XML
+ components using standard APIs (formal, de facto, or proposed). The
+ components must be high performance, reliable, and easy to use. Where
+ inter-related, the components must be part of an underlying architectural
+ orchestration that will allow them to work together without major
+ negotiations or breakage.</p>
+ <p>2.3 We believe that the best way to define this XML transformation
+ architecture is by having both individuals and corporations
+ collaborate on the best possible infrastructure, APIs, code, testing,
+ and release cycles. Components must be vendor neutral and usable as
+ core components for all.</p>
+ <p>2.4 In order to achieve a coherent architecture between Apache Xalan
+ components and other components and applications, standards (formal or
+ de facto) will be used as much as possible for both protocols and
+ APIs. Where appropriate, experiences and lessons learned will be fed
+ back to standards bodies in an effort to assist in the development of
+ those standards. We will also encourage the innovation of new
+ protocols, APIs, and components in order to seed new concepts not
+ yet defined by standards.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>3 HISTORY</h3>
+ <p>3.1 This project was established under the direction of the Apache
+ Software Foundation in October 2004 to facilitate joint open-source
+ development. Prior to October 2004 this project was a subproject
+ of the Apache XML project.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>4 TERMS</h3>
+ <p>4.1 The ASF Board. The management board of the Apache Software
+ Foundation.</p>
+ <p>4.2 The Project. The Apache Xalan project; intended to refer to the
+ source code, website, subprojects, and community that are Apache Xalan.</p>
+ <p>4.3 Subproject. The Apache Xalan project may have subprojects; a
+ subproject is responsible for a component or application whose scope
+ is well defined.</p>
+ <p>4.4 Product. Some deliverable (usually a binary or source package)
+ that a subproject makes available to the public. Subprojects may have
+ multiple products.</p>
+ <p>4.5 Release. A specific version of a product. Subprojects may have
+ multiple releases of a given product.</p>
+ <p>4.6 Contributor. Anyone who makes a contribution to the development
+ of the Apache Xalan project.</p>
+ <p>4.7 Committer. The Apache Xalan project has a set of committers.
+ Committers are contributors who have read/write access to the source
+ code repository.</p>
+ <p>4.8 PMC. The PMC (Project Management Committee) is the group of people
+ that form the entity that makes decisions and controls the project.
+ Individual people or committers do not control the project.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>5 THE PROJECT MANAGEMENT COMMITTEE</h3>
+ <p>5.1 The Apache Xalan project is managed by a core group of committers
+ known as the Project Management Committee [PMC]. Subprojects, if any,
+ much each have at least one representative committer on the PMC.</p>
+ <p>5.2 The activities of the PMC are coordinated by the Chairperson,
+ who is an officer of the corporation and reports to the Apache
+ Board. The Chairperson will, on the request of the Apache Board,
+ provide reports to the Board on issues related to the running of
+ the Apache Xalan project.</p>
+ <p>5.3 The PMC has the following responsibilities:</p>
+ <p>a) Accepting new subproject proposals, formally submitting these
+ proposals for Apache Xalan committer vote, and creating the subproject
+ (see SUBPROJECTS below). This is done in collaboration with the
+ Incubator (see <a href="http://incubator.apache.org">http://incubator.apache.org</a>).</p>
+ <p>b) Facilitating code or other donations by individuals or companies,
+ in collaboration with the Incubator.</p>
+ <p>c) Resolving license issues and other legal issues in conjunction with
+ the ASF board.</p>
+ <p>d) Ensuring that administrative and infrastructure work is completed.</p>
+ <p>e) Facilitating relationships among projects and subprojects.</p>
+ <p>f) Facilitating relationships between the Apache Xalan project and the
+ external world.</p>
+ <p>g) Overseeing Apache Xalan to ensure that the mission defined in this
+ document is being fulfilled.</p>
+ <p>h) Resolving conflicts within the project.</p>
+ <p>i) Reporting to the ASF board (through the Chair) on the progress
+ of the project.</p>
+ <p>j) Propose new releases of projects or subprojects. Such proposals pass
+ if 75% of the PMC members vote in agreement.</p>
+
+ <p>5.4 A contributor can, at any time, nominate a committer to be on the PMC,
+ by calling for a vote. If two thirds, or more, of the active committers
+ vote in agreement then the nomination is given to the PMC. The person
+ becomes a new PMC member if 75% or more of the PMC members vote in
+ agreement, with no dissenting votes among the PMC members. This individual
+ should be elected based on merit for the evolution of the project and
+ demonstration of commitment.</p>
+ <p>5.5 In cases where the subproject is unable to directly provide a
+ representative on the PMC, another member of the PMC will be required to
+ represent that subproject on the PMC. This will be strongly discouraged.
+ It is preferable that all subprojects have direct representation on the
+ PMC.</p>
+ <p>5.6 At least every twelve months, or more often if directed by the ASF
+ board, the PMC members will elect a Chairperson from among themselves;
+ the person with the most votes from the other PMC members is recommended
+ to the ASF board for the position of Chairperson, and with the ASF board's
+ approval, becomes the Chairperson for the new term.</p>
+ <p>5.7 Upon agreement by the Apache Board, the recommended Chairperson will,
+ if they are not already, be appointed an officer of the corporation. See
+ <a href="http://www.apache.org/foundation/bylaws.html">
+ http://www.apache.org/foundation/bylaws.html</a> for more information.</p>
+ <p>5.8 The PMC is responsible for maintaining and updating this charter.
+ Development must follow the process outlined below, so any change to the
+ development process necessitates a change to the charter. Proposed changes
+ to this charter by the PMC are passed if 75% or more of the PMC members
+ approve the proposal, with no dissenting votes. However, an active Apache
+ Xalan committer may challenge the change.</p>
+ <p>5.9 An active Apache Xalan committer may challenge a change to this charter
+ proposed by the PMC within two weeks of its proposal. When challenged the
+ proposed change is passed if within two weeks of the challenge the active
+ committers approve the change with a two-thirds majority vote.</p>
+ <p>5.10 The PMC ultimately makes the decisions for the project, not the individual
+ people. At any time the PMC can reject patches or other contributions to the
+ project if 75% or more of the PMC members vote to reject the contribution.</p>
+ <p>5.11 A PMC member may resign their membership at any time. However, in the
+ unlikely event that a member of the PMC becomes disruptive to the process,
+ such as ceasing to take part in PMC votes, the PMC member may be removed from
+ the PMC by a vote among the other PMC members. The PMC member is removed if
+ 75% or more of the other PMC members approve the removal, with no dissenting
+ votes among the other PMC members.</p>
+ <p>5.12 A person remains a PMC member until he or she resigns, is removed by a
+ vote from among the other PMC members, dies or is incapacitated.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>6 SUBPROJECTS</h3>
+ <p>6.1 A subproject of the Apache Xalan project is responsible for a component
+ or application whose scope is well defined. Each subproject has its own set
+ of developers, and is responsible for approving its own committers. Apache
+ Xalan is composed of subprojects which fit into one of two categories:</p>
+ <p>(a) An XSLT processor implementation in some particular programming
+ language. There may be multiple processors for a given language if
+ the API's the processors support are sufficiently dissimilar. At the
+ time of writing, there is one processor for C++ and two for Java.</p>
+ <p>(b) A set of components which are used in related applications and are
+ tightly bound, usually through internal API's, to one (or more) of the
+ processor subprojects.</p>
+ <p>6.2 A new subproject proposal is submitted to the PMC, and then accepted
+ by a majority Apache Xalan project active committer vote within two weeks
+ after the proposal.</p>
+ <p>6.3 Each subproject must have a set of requirements as well as an
+ up-to-date release plan and design document on its dedicated web page.</p>
+ <p>6.4 It is recommended that each subproject have a smoke-test system
+ that works at least as a basic integration test.</p>
+ <p>6.5 A subproject may be removed if 75% or more of the PMC members approve
+ the proposal, there are no dissenting votes among the PMC members,
+ and no challenges by active Apache Xalan project committers
+ within two weeks after the proposal.
+ A contributor may challenge the proposed removal
+ of a subproject within two weeks of the proposal.
+ In this case the proposed removal is passed if within two weeks of the
+ challenge the active committers approve the removal with a two-thirds
+ majority vote. Any subproject removal is subject to the approval of the
+ ASF board.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>7 CONTRIBUTORS</h3>
+ <p>7.1 Like all Apache projects, the Apache Xalan project is a
+ meritocracy -- the more work you do, the more you are allowed to do.</p>
+ <p>7.2 People who make regular and substantial contributions may become
+ committers as described below. Contributions include: participating in
+ mailing lists, reporting issues or bugs in issue-records in the Issue Database,
+ providing patches, and proposing changes to a product.</p>
+ <p>7.3 In order to ensure that all code contained in the Apache Xalan
+ project's code repository is free of licensing, intellectual property and patent
+ issues, any person wishing to contribute a new feature to Apache Xalan must either
+ sign:</p>
+ <p>a) If contributing as an individual, sign the "Individual
+ Contributor License Agreement (CLA)"
+ (<a href="http://www.apache.org/licenses/icla.txt">http://www.apache.org/licenses/icla.txt</a>)
+ and file a copy with the Secretary of the Corporation; or </p>
+ <p>b) If making the contribution as part of their employment
+ responsibilities, sign the "Corporate CLA (CCLA)",
+ (<a href="http://www.apache.org/licenses/cla-corporate.txt">http://www.apache.org/licenses/cla-corporate.txt</a>)
+ and file a copy with the Secretary of the Corporation.</p>
+ <p>7.4 If the contribution in question is a small bugfix, the contributor need
+ not sign a CLA, but need only provide the following information, attaching
+ it to the communication containing the patch:</p>
+ <p>a) Name and employer</p>
+ <p>b) Are you the author of the code being contributed?</p>
+ <p>c) Do you have the right to grant the copyright and patent
+ licenses for the contribution that are set forth in the ASF v.2.0
+ license (<a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)?</p>
+ <p>d) Does your employer have any rights to code that you have
+ written, for example, through your contract for employment? If
+ so, has your employer given you permission to contribute the code
+ on its behalf or waived its rights in the code?</p>
+ <p>e) Are you aware of any third-party licenses or other
+ restrictions (such as related patents or trademarks) that could
+ apply to your contribution? If so, what are they?</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>8 COMMITTERS</h3>
+ <p>8.1 The Apache Xalan project has a set of committers. If there
+ are subprojects, each subproject will also have a set of committers.
+ Committers are contributors who have read/write access to the source code
+ repository. New committers are added when a contributor is nominated by a
+ committer and approved by at least 50 percent of the active committers for
+ that subproject with no opposing votes. In most cases, new committers will
+ already be participating in the development process by submitting suggestions
+ and/or fixes via issue-records in the Issue Database or mailing lists.</p>
+ <p>8.2 For the purposes of voting, committers will be classed as "active" or
+ "inactive". Only active committers will be included in the totals used to
+ determine the success or failure of a particular vote.</p>
+ <p>8.3 Committers remain active as long as they are contributing code or
+ posting to the project or subproject mailing lists. If a committers has
+ neither contributed code nor posted to the mailing lists in 3
+ months, a member of the PMC will e-mail the committer,
+ the project or subproject development list, and the PMC mailing list
+ notifying the committer that they are now in inactive status.</p>
+ <p>8.4 An inactive status will not prevent a committer committing new code
+ changes or posting to the mailing lists. Either of these activities will
+ automatically re-activate the committer for the purposes of voting.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>9 INFRASTRUCTURE</h3>
+ <p>9.1 The Apache Xalan project relies on the Apache XML project
+ and the Apache Infrastructure project for the following:</p>
+ <p>a) Issue Database -- This is a system with issue-records,
+ for tracking bugs, issues, features and requests.</p>
+ <p>b) Repository -- The xalan.apache.org project has its set
+ of parts that make up the software, and these parts are
+ managed in a repository. Committers make changes to the source code,
+ documentation and other associated parts that are stored in
+ the repository. Any subproject will have its set of committers
+ for its repository.</p>
+ <p>c) Website -- The website <a href="http://xalan.apache.org">xalan.apache.org</a>
+ will contain information about the Apache Xalan project and its subprojects,
+ including documentation, downloads of releases, and this charter.</p>
+ <p>d) Mailing Lists -- appropriate mailing lists will be created
+ at the discretion of the PMC. Such mailing lists could
+ for example include: a PMC mailing list, a general mailing list,
+ project or subproject public developer mailing lists,
+ project or subproject public user mailing lists.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>10 LICENSING</h3>
+ <p>10.1 All contributions to the Apache Xalan project adhere to the "Apache
+ Software Foundation License, Version 2.0"
+ (<a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>).
+ All further contributions, including patches, must be made under the same terms.</p>
+ <p>10.2 When a committer is considering integrating a contribution
+ from a contributor who has no CLA on file with the Corporation,
+ it is the responsibility of the committer, in consultation with
+ the PMC, to conduct due diligence on the pedigree of the
+ contribution under consideration; see sections 7.3 and 7.4. </p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>11 THE DEVELOPMENT PROCESS</h3>
+ <p>11.1 For a committer to commit a change to the MAIN branch of the
+ repository an issue-record must be opened in the "Issue Database"
+ to track the change. The status of the issue must be kept up to date.</p>
+ <p>11.2 No voting is required to commit changes, but one other active
+ committer must review the changes. Before the changes are committed, the reviewer
+ must add a comment in the corresponding issue-record indicating that
+ they have reviewed and approve the changes.</p>
+ <p>11.3 Issue-records and reviews are not required for committing changes to
+ other experimental branches (not the MAIN branch) in a repository.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>12 VOTING</h3>
+ <p>12.1 Unless otherwise stated in this mission, votes cast on Apache Xalan
+ proposals must be made within two weeks of the proposal. A challenge to
+ a proposal must also be made within two weeks of the proposal. Likewise,
+ votes cast on challenges must be cast within two weeks of the challenge.</p>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>13 RELATIONSHIP TO OTHER APACHE PROJECTS</h3>
+ <p>13.1 The Apache Xalan project should work closely with other Apache
+ projects, such as Xerces and XML, to avoid redundancy
+ and achieve a coherent architecture among Apache Xalan and these
+ projects.</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 - Tue 2012-10-09</div>
+</div>
+</body>
+</html>
diff --git a/docs/xalan/xalan-c/commandline.html b/docs/xalan/xalan-c/commandline.html
index f2f7f9c..1e3c282 100644
--- a/docs/xalan/xalan-c/commandline.html
+++ b/docs/xalan/xalan-c/commandline.html
@@ -1,255 +1,255 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html>
-<head>
-<title>ASF: Xalan-C++ Command-Line Utilities</title>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
-</head>
-<!--
- * 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.
- -->
-<body>
-<div id="title">
-<table class="HdrTitle">
-<tbody>
-<tr>
-<th rowspan="2">
-<a href="../index.html">
-<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
-</a>
-</th>
-<th text-align="center" width="75%">
-<a href="index.html">Xalan-C/C++ Version 1.11</a>
-</th>
-</tr>
-<tr>
-<td valign="middle">Xalan-C++ Command-Line Utilities</td>
-</tr>
-</tbody>
-</table>
-<table class="HdrButtons" align="center" border="1">
-<tbody>
-<tr>
-<td>
-<a href="http://www.apache.org">Apache Foundation</a>
-</td>
-<td>
-<a href="http://xalan.apache.org">Xalan Project</a>
-</td>
-<td>
-<a href="http://xerces.apache.org">Xerces Project</a>
-</td>
-<td>
-<a href="http://www.w3.org/TR">Web Consortium</a>
-</td>
-<td>
-<a href="http://www.oasis-open.org/standards">Oasis Open</a>
-</td>
-</tr>
-</tbody>
-</table>
-</div>
-<div id="navLeft">
-<ul>
-<li>
-<a href="resources.html">Resources</a>
-<br />
-</li>
-<li>
-<a href="../index.html">Home</a>
-</li></ul><hr /><ul>
-<li>
-<a href="index.html">Xalan-C++ 1.11</a>
-</li>
-<li>
-<a href="whatsnew.html">What's New</a>
-</li>
-<li>
-<a href="license.html">Licenses</a>
-</li></ul><hr /><ul>
-<li>
-<a href="overview.html">Overview</a>
-</li>
-<li>
-<a href="charter.html">Charter</a>
-</li></ul><hr /><ul>
-<li>
-<a href="download.html">Download</a>
-</li>
-<li>
-<a href="buildlibs.html">Build Libraries</a>
-</li>
-<li>
-<a href="install.html">Installation</a>
-</li>
-<li>
-<a href="builddocs.html">Build Documents</a>
-</li></ul><hr /><ul>
-<li>
-<a href="samples.html">Sample Apps</a>
-</li>
-<li>Command Line<br />
-</li>
-<li>
-<a href="usagepatterns.html">Usage Patterns</a>
-</li></ul><hr /><ul>
-<li>
-<a href="programming.html">Programming</a>
-</li>
-<li>
-<a href="extensions.html">Extensions</a>
-</li>
-<li>
-<a href="extensionslib.html">Extensions Library</a>
-</li>
-<li>
-<a href="apiDocs/index.html">API Reference</a>
-</li></ul><hr /><ul>
-<li>
-<a href="faq.html">Xalan-C FAQs</a>
-</li></ul><hr /><ul>
-<li>
-<a href="whatsnew.html#bugs">Bugs</a>
-</li>
-<li>
-<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
-</li>
-<li>
-<a href="secureweb.html">Web Security</a>
-</li>
-</ul>
-</div>
-<div id="content">
-<h2>Xalan-C++ Command-Line Utilities</h2>
-<ul>
-<li>
-<a href="#use">Using a command-line utility</a>
-</li>
-<li>
-<a href="#xalanexe">Using the Xalan executable</a>
-</li>
-
-</ul>
-<a name="use"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Using a command-line utility</h3>
-<p>To perform a transformation, you can call Xalan-C++ from the command line (or script),
- or from within an application (see <a href="usagepatterns.html">Usage Patterns</a>).</p>
-<p>To perform a transformation from the command line or a script, do the following:</p>
- <ol>
- <li>
-<a href="download.html">Download Xalan-C++</a>.<br />
-<br />
-</li>
- <li>
-<a href="install.html">Set the path/library path</a> to include the Xalan executable and the Xalan and Xerces
- libraries.<br />
-<br />
-</li>
- <li>Call the Xalan executable with the appropriate flags and arguments (described below).</li>
- </ol>
-
-<a name="xalanexe"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Using the Xalan executable</h3>
-<p>Call the Xalan executable as follows:<br />
-<br />
- <code>Xalan <b>
-<i>[options]</i>
-</b> <b>
-<i>xmlSource</i>
-</b> <b>
-<i>xslStylesheet</i>
-</b>
-</code>
-<br />
-<br />
- where <b>
-<i>xmlSource</i>
-</b> is the XML source document, <b>
-<i>xslStylesheet</i>
-</b> is the stylesheet to apply, and
- <b>
-<i>[options]</i>
-</b> are any (or none) of the following:</p>
-<table border="1">
- <tr>
-<th class="content" rowspan="1" colspan="1">Option</th>
-<th class="content" rowspan="1" colspan="1">Description</th>
-</tr>
- <tr>
-<td class="content" rowspan="1" colspan="1">-a</td>
-<td class="content" rowspan="1" colspan="1">Use stylesheet processing instruction, not the stylesheet argument.</td>
-</tr>
- <tr>
-<td class="content" rowspan="1" colspan="1">-e encoding</td>
-<td class="content" rowspan="1" colspan="1">Force the specified encoding for the output.</td>
-</tr>
- <tr>
-<td class="content" rowspan="1" colspan="1">-i integer</td>
-<td class="content" rowspan="1" colspan="1">Indent the specified amount.</td>
-</tr>
- <tr>
-<td class="content" rowspan="1" colspan="1">-m</td>
-<td class="content" rowspan="1" colspan="1">Omit the META tag in HTML output.</td>
-</tr>
- <tr>
-<td class="content" rowspan="1" colspan="1">-o filename</td>
-<td class="content" rowspan="1" colspan="1">Write transformation result to this file (rather than to the console).</td>
-</tr>
- <tr>
-<td class="content" rowspan="1" colspan="1">-p name expr</td>
-<td class="content" rowspan="1" colspan="1">Set a stylesheet parameter with this expression.</td>
-</tr>
- <tr>
-<td class="content" rowspan="1" colspan="1">-t name expr</td>
-<td class="content" rowspan="1" colspan="1">Display timing information.</td>
-</tr>
- <tr>
-<td class="content" rowspan="1" colspan="1">-u name expr</td>
-<td class="content" rowspan="1" colspan="1">Disable escaping of URLs in HTML output.</td>
-</tr>
- <tr>
-<td class="content" rowspan="1" colspan="1">-v</td>
-<td class="content" rowspan="1" colspan="1">Validate the XML source document.</td>
-</tr>
- <tr>
-<td class="content" rowspan="1" colspan="1">-</td>
-<td class="content" rowspan="1" colspan="1">A dash as the 'source' argument reads from stdin.<br />A dash as the 'stylesheet' argument reads
- from stdin.<br />('-' cannot be used for both arguments.)</td>
-</tr>
-</table>
-<p>To display a list of the options call the Xalan executable as follows:</p>
-<p>
-<code>Xalan -?</code>
-</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 2012-10-07</div>
-</div>
-</body>
-</html>
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Xalan-C++ Command-Line Utilities</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * 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.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan-C/C++ Version 1.11</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Xalan-C++ Command-Line Utilities</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="../index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-C++ 1.11</a>
+</li>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="license.html">Licenses</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>
+<a href="charter.html">Charter</a>
+</li></ul><hr /><ul>
+<li>
+<a href="download.html">Download</a>
+</li>
+<li>
+<a href="buildlibs.html">Build Libraries</a>
+</li>
+<li>
+<a href="install.html">Installation</a>
+</li>
+<li>
+<a href="builddocs.html">Build Documents</a>
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>Command Line<br />
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="programming.html">Programming</a>
+</li>
+<li>
+<a href="extensions.html">Extensions</a>
+</li>
+<li>
+<a href="extensionslib.html">Extensions Library</a>
+</li>
+<li>
+<a href="apiDocs/index.html">API Reference</a>
+</li></ul><hr /><ul>
+<li>
+<a href="faq.html">Xalan-C FAQs</a>
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html#bugs">Bugs</a>
+</li>
+<li>
+<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
+</li>
+<li>
+<a href="secureweb.html">Web Security</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<h2>Xalan-C++ Command-Line Utilities</h2>
+<ul>
+<li>
+<a href="#use">Using a command-line utility</a>
+</li>
+<li>
+<a href="#xalanexe">Using the Xalan executable</a>
+</li>
+
+</ul>
+<a name="use"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Using a command-line utility</h3>
+<p>To perform a transformation, you can call Xalan-C++ from the command line (or script),
+ or from within an application (see <a href="usagepatterns.html">Usage Patterns</a>).</p>
+<p>To perform a transformation from the command line or a script, do the following:</p>
+ <ol>
+ <li>
+<a href="download.html">Download Xalan-C++</a>.<br />
+<br />
+</li>
+ <li>
+<a href="install.html">Set the path/library path</a> to include the Xalan executable and the Xalan and Xerces
+ libraries.<br />
+<br />
+</li>
+ <li>Call the Xalan executable with the appropriate flags and arguments (described below).</li>
+ </ol>
+
+<a name="xalanexe"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Using the Xalan executable</h3>
+<p>Call the Xalan executable as follows:<br />
+<br />
+ <code>Xalan <b>
+<i>[options]</i>
+</b> <b>
+<i>xmlSource</i>
+</b> <b>
+<i>xslStylesheet</i>
+</b>
+</code>
+<br />
+<br />
+ where <b>
+<i>xmlSource</i>
+</b> is the XML source document, <b>
+<i>xslStylesheet</i>
+</b> is the stylesheet to apply, and
+ <b>
+<i>[options]</i>
+</b> are any (or none) of the following:</p>
+<table border="1">
+ <tr>
+<th class="content" rowspan="1" colspan="1">Option</th>
+<th class="content" rowspan="1" colspan="1">Description</th>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">-a</td>
+<td class="content" rowspan="1" colspan="1">Use stylesheet processing instruction, not the stylesheet argument.</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">-e encoding</td>
+<td class="content" rowspan="1" colspan="1">Force the specified encoding for the output.</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">-i integer</td>
+<td class="content" rowspan="1" colspan="1">Indent the specified amount.</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">-m</td>
+<td class="content" rowspan="1" colspan="1">Omit the META tag in HTML output.</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">-o filename</td>
+<td class="content" rowspan="1" colspan="1">Write transformation result to this file (rather than to the console).</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">-p name expr</td>
+<td class="content" rowspan="1" colspan="1">Set a stylesheet parameter with this expression.</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">-t name expr</td>
+<td class="content" rowspan="1" colspan="1">Display timing information.</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">-u name expr</td>
+<td class="content" rowspan="1" colspan="1">Disable escaping of URLs in HTML output.</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">-v</td>
+<td class="content" rowspan="1" colspan="1">Validate the XML source document.</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">-</td>
+<td class="content" rowspan="1" colspan="1">A dash as the 'source' argument reads from stdin.<br />A dash as the 'stylesheet' argument reads
+ from stdin.<br />('-' cannot be used for both arguments.)</td>
+</tr>
+</table>
+<p>To display a list of the options call the Xalan executable as follows:</p>
+<p>
+<code>Xalan -?</code>
+</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 - Tue 2012-10-09</div>
+</div>
+</body>
+</html>
diff --git a/docs/xalan/xalan-c/download.html b/docs/xalan/xalan-c/download.html
index 1455360..7a2616f 100644
--- a/docs/xalan/xalan-c/download.html
+++ b/docs/xalan/xalan-c/download.html
@@ -1,558 +1,594 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html>
-<head>
-<title>ASF: Downloading Xalan-C++</title>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
-</head>
-<!--
- * 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.
- -->
-<body>
-<div id="title">
-<table class="HdrTitle">
-<tbody>
-<tr>
-<th rowspan="2">
-<a href="../index.html">
-<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
-</a>
-</th>
-<th text-align="center" width="75%">
-<a href="index.html">Xalan-C/C++ Version 1.11</a>
-</th>
-</tr>
-<tr>
-<td valign="middle">Downloading Xalan-C++</td>
-</tr>
-</tbody>
-</table>
-<table class="HdrButtons" align="center" border="1">
-<tbody>
-<tr>
-<td>
-<a href="http://www.apache.org">Apache Foundation</a>
-</td>
-<td>
-<a href="http://xalan.apache.org">Xalan Project</a>
-</td>
-<td>
-<a href="http://xerces.apache.org">Xerces Project</a>
-</td>
-<td>
-<a href="http://www.w3.org/TR">Web Consortium</a>
-</td>
-<td>
-<a href="http://www.oasis-open.org/standards">Oasis Open</a>
-</td>
-</tr>
-</tbody>
-</table>
-</div>
-<div id="navLeft">
-<ul>
-<li>
-<a href="resources.html">Resources</a>
-<br />
-</li>
-<li>
-<a href="../index.html">Home</a>
-</li></ul><hr /><ul>
-<li>
-<a href="index.html">Xalan-C++ 1.11</a>
-</li>
-<li>
-<a href="whatsnew.html">What's New</a>
-</li>
-<li>
-<a href="license.html">Licenses</a>
-</li></ul><hr /><ul>
-<li>
-<a href="overview.html">Overview</a>
-</li>
-<li>
-<a href="charter.html">Charter</a>
-</li></ul><hr /><ul>
-<li>Download<br />
-</li>
-<li>
-<a href="buildlibs.html">Build Libraries</a>
-</li>
-<li>
-<a href="install.html">Installation</a>
-</li>
-<li>
-<a href="builddocs.html">Build Documents</a>
-</li></ul><hr /><ul>
-<li>
-<a href="samples.html">Sample Apps</a>
-</li>
-<li>
-<a href="commandline.html">Command Line</a>
-</li>
-<li>
-<a href="usagepatterns.html">Usage Patterns</a>
-</li></ul><hr /><ul>
-<li>
-<a href="programming.html">Programming</a>
-</li>
-<li>
-<a href="extensions.html">Extensions</a>
-</li>
-<li>
-<a href="extensionslib.html">Extensions Library</a>
-</li>
-<li>
-<a href="apiDocs/index.html">API Reference</a>
-</li></ul><hr /><ul>
-<li>
-<a href="faq.html">Xalan-C FAQs</a>
-</li></ul><hr /><ul>
-<li>
-<a href="whatsnew.html#bugs">Bugs</a>
-</li>
-<li>
-<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
-</li>
-<li>
-<a href="secureweb.html">Web Security</a>
-</li>
-</ul>
-</div>
-<div id="content">
-<h2>Downloading Xalan-C++</h2>
-<ul>
- <li>
-<a href="#DownloadWhat">Downloading What You Need</a>
-</li>
- <li>
-<a href="#DownloadNotes">Downloading Notes</a>
-</li>
-
- <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>
-
-<a name="DownloadWhat"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Downloading What You Need</h3>
-
-<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 that is already assembled for your web browsers.
-</p>
-
-<p>Building the API Reference documents requires a current version of the
-<a href="http://www.doxygen.org">Doxygen</a> and
-<a href="http://www.graphviz.org">GraphViz</a> programs for UNIX or Linux.
-We have not tried building the API Reference on a Windows platform.
-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>
-<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-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>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-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++ <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>
-
-<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-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>
-
-<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">
- <tr>
- <th class="content" rowspan="1" colspan="1">Platform - Operating System</th>
- <th class="content" rowspan="1" colspan="1">Compilers</th>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Windows X86</td>
- <td class="content" rowspan="1" colspan="1">VC7.1, VC8, VC9, VC10</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Windows X86_64</td>
- <td class="content" rowspan="1" colspan="1">VC8, VC9, VC10</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">HPUX ia64</td>
- <td class="content" rowspan="1" colspan="1">ACC 6</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">HPUX ia64_64</td>
- <td class="content" rowspan="1" colspan="1">ACC 6</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">AIX powerpc</td>
- <td class="content" rowspan="1" colspan="1">xlc 7.0</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">AIX powerpc_64</td>
- <td class="content" rowspan="1" colspan="1">xlc 7.0</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">SOLARIS sparc</td>
- <td class="content" rowspan="1" colspan="1">cc 5.10</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">SOLARIS sparc_64</td>
- <td class="content" rowspan="1" colspan="1">cc 5.10</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">SOLARIS X86</td>
- <td class="content" rowspan="1" colspan="1">cc 5.10</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">SOLARIS X86_64</td>
- <td class="content" rowspan="1" colspan="1">cc 5.10</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">LINUX X86</td>
- <td class="content" rowspan="1" colspan="1">gcc 3.4</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Linux X86_64</td>
- <td class="content" rowspan="1" colspan="1">gcc 3.4</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">MAC OSX X86</td>
- <td class="content" rowspan="1" colspan="1">gcc 4.0</td>
- </tr>
- </table>
-</p>
-<p>Building for platforms other than those listed will require
-a build of the Xerces-C/C++ XML Parser library from the sources.
-Use of Xalan and Xerces libraries compiled with different versions
-of compilers may cause problems</p>
-
-<table class="note">
-<tr>
-<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>
-</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>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">
-<tr>
-<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>
-</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 - Tue 2012-10-09</div>
-</div>
-</body>
-</html>
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Downloading Xalan-C++</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * 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.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan-C/C++ Version 1.11</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Downloading Xalan-C++</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="../index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-C++ 1.11</a>
+</li>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="license.html">Licenses</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>
+<a href="charter.html">Charter</a>
+</li></ul><hr /><ul>
+<li>Download<br />
+</li>
+<li>
+<a href="buildlibs.html">Build Libraries</a>
+</li>
+<li>
+<a href="install.html">Installation</a>
+</li>
+<li>
+<a href="builddocs.html">Build Documents</a>
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>
+<a href="commandline.html">Command Line</a>
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="programming.html">Programming</a>
+</li>
+<li>
+<a href="extensions.html">Extensions</a>
+</li>
+<li>
+<a href="extensionslib.html">Extensions Library</a>
+</li>
+<li>
+<a href="apiDocs/index.html">API Reference</a>
+</li></ul><hr /><ul>
+<li>
+<a href="faq.html">Xalan-C FAQs</a>
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html#bugs">Bugs</a>
+</li>
+<li>
+<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
+</li>
+<li>
+<a href="secureweb.html">Web Security</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<h2>Downloading Xalan-C++</h2>
+<ul>
+ <li>
+<a href="#DownloadWhat">Downloading What You Need</a>
+</li>
+ <li>
+<a href="#DownloadNotes">Downloading Notes</a>
+</li>
+
+ <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>
+
+<a name="DownloadWhat"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Downloading What You Need</h3>
+
+<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>
+<b>Download Xalan-C/C++ Distributions from Apache Mirrors</b>
+</p>
+<table border="1">
+ <tr>
+<td class="content" rowspan="1" colspan="1">
+<a href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c">
+ The Xalan-C/C++ Distribution Tree</a>
+</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">
+<a href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/sources">
+ The Xalan-C/C++ Source Packages</a>
+</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">
+<a href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/docs">
+ The Xalan-C/C++ Documentation Packages</a>
+</td>
+</tr>
+ <tr>
+<td class="content" rowspan="1" colspan="1">
+<a href="http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/binaries">
+ The Xalan-C/C++ Binary Packages</a>
+</td>
+</tr>
+</table>
+
+<p>
+<b>Download Xerces-C/C++ XML Parser Library</b>
+</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>
+<b>Our Xalan Packages</b>
+</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 that is already assembled for your web browsers.
+</p>
+
+<p>Building the API Reference documents requires a current version of the
+<a href="http://www.doxygen.org">Doxygen</a> and
+<a href="http://www.graphviz.org">GraphViz</a> programs for UNIX or Linux.
+We have not tried building the API Reference on a Windows platform.
+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>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>
+
+<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/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>
+<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-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>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-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++ <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>
+
+<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-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>
+<b>Windows Packages - 64 BIT</b>
+</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>
+<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>
+
+<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">
+ <tr>
+ <th class="content" rowspan="1" colspan="1">Platform - Operating System</th>
+ <th class="content" rowspan="1" colspan="1">Compilers</th>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Windows X86</td>
+ <td class="content" rowspan="1" colspan="1">VC7.1, VC8, VC9, VC10</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Windows X86_64</td>
+ <td class="content" rowspan="1" colspan="1">VC8, VC9, VC10</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">HPUX ia64</td>
+ <td class="content" rowspan="1" colspan="1">ACC 6</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">HPUX ia64_64</td>
+ <td class="content" rowspan="1" colspan="1">ACC 6</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">AIX powerpc</td>
+ <td class="content" rowspan="1" colspan="1">xlc 7.0</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">AIX powerpc_64</td>
+ <td class="content" rowspan="1" colspan="1">xlc 7.0</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">SOLARIS sparc</td>
+ <td class="content" rowspan="1" colspan="1">cc 5.10</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">SOLARIS sparc_64</td>
+ <td class="content" rowspan="1" colspan="1">cc 5.10</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">SOLARIS X86</td>
+ <td class="content" rowspan="1" colspan="1">cc 5.10</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">SOLARIS X86_64</td>
+ <td class="content" rowspan="1" colspan="1">cc 5.10</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">LINUX X86</td>
+ <td class="content" rowspan="1" colspan="1">gcc 3.4</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Linux X86_64</td>
+ <td class="content" rowspan="1" colspan="1">gcc 3.4</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">MAC OSX X86</td>
+ <td class="content" rowspan="1" colspan="1">gcc 4.0</td>
+ </tr>
+ </table>
+</p>
+<p>Building for platforms other than those listed will require
+a build of the Xerces-C/C++ XML Parser library from the sources.
+Use of Xalan and Xerces libraries compiled with different versions
+of compilers may cause problems</p>
+
+<table class="note">
+<tr>
+<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>
+</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://icu-project.org">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>
+
+<table class="note">
+<tr>
+<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>
+</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 - Mon 2012-10-22</div>
+</div>
+</body>
+</html>
diff --git a/docs/xalan/xalan-c/extensions.html b/docs/xalan/xalan-c/extensions.html
index 5775176..3b96b60 100644
--- a/docs/xalan/xalan-c/extensions.html
+++ b/docs/xalan/xalan-c/extensions.html
@@ -1,440 +1,440 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html>
-<head>
-<title>ASF: Xalan-C++ Extension Functions</title>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
-</head>
-<!--
- * 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.
- -->
-<body>
-<div id="title">
-<table class="HdrTitle">
-<tbody>
-<tr>
-<th rowspan="2">
-<a href="../index.html">
-<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
-</a>
-</th>
-<th text-align="center" width="75%">
-<a href="index.html">Xalan-C/C++ Version 1.11</a>
-</th>
-</tr>
-<tr>
-<td valign="middle">Xalan-C++ Extension Functions</td>
-</tr>
-</tbody>
-</table>
-<table class="HdrButtons" align="center" border="1">
-<tbody>
-<tr>
-<td>
-<a href="http://www.apache.org">Apache Foundation</a>
-</td>
-<td>
-<a href="http://xalan.apache.org">Xalan Project</a>
-</td>
-<td>
-<a href="http://xerces.apache.org">Xerces Project</a>
-</td>
-<td>
-<a href="http://www.w3.org/TR">Web Consortium</a>
-</td>
-<td>
-<a href="http://www.oasis-open.org/standards">Oasis Open</a>
-</td>
-</tr>
-</tbody>
-</table>
-</div>
-<div id="navLeft">
-<ul>
-<li>
-<a href="resources.html">Resources</a>
-<br />
-</li>
-<li>
-<a href="../index.html">Home</a>
-</li></ul><hr /><ul>
-<li>
-<a href="index.html">Xalan-C++ 1.11</a>
-</li>
-<li>
-<a href="whatsnew.html">What's New</a>
-</li>
-<li>
-<a href="license.html">Licenses</a>
-</li></ul><hr /><ul>
-<li>
-<a href="overview.html">Overview</a>
-</li>
-<li>
-<a href="charter.html">Charter</a>
-</li></ul><hr /><ul>
-<li>
-<a href="download.html">Download</a>
-</li>
-<li>
-<a href="buildlibs.html">Build Libraries</a>
-</li>
-<li>
-<a href="install.html">Installation</a>
-</li>
-<li>
-<a href="builddocs.html">Build Documents</a>
-</li></ul><hr /><ul>
-<li>
-<a href="samples.html">Sample Apps</a>
-</li>
-<li>
-<a href="commandline.html">Command Line</a>
-</li>
-<li>
-<a href="usagepatterns.html">Usage Patterns</a>
-</li></ul><hr /><ul>
-<li>
-<a href="programming.html">Programming</a>
-</li>
-<li>Extensions<br />
-</li>
-<li>
-<a href="extensionslib.html">Extensions Library</a>
-</li>
-<li>
-<a href="apiDocs/index.html">API Reference</a>
-</li></ul><hr /><ul>
-<li>
-<a href="faq.html">Xalan-C FAQs</a>
-</li></ul><hr /><ul>
-<li>
-<a href="whatsnew.html#bugs">Bugs</a>
-</li>
-<li>
-<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
-</li>
-<li>
-<a href="secureweb.html">Web Security</a>
-</li>
-</ul>
-</div>
-<div id="content">
-<h2>Xalan-C++ Extension Functions</h2>
-<ul>
- <li>
-<a href="#intro">Introduction</a>
-</li>
- <li>
-<a href="#implement">Implementing an extension function</a>
-</li>
- <li>
-<a href="#install">Installing an extension function</a>
-</li>
- <li>
-<a href="#use">Using an extension function</a>
-</li>
-</ul>
-<a name="intro"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Introduction</h3>
-<p>At times, you may want to call your own custom C functions from a stylesheet. For these situations, Xalan-C++ supports the
- creation and use of extension functions. Xalan-C++ also provides a <a href="extensionslib.html">library of extension functions
- </a> for your use.</p>
-<p>You can think of extension functions as extending the core library of functions that XPath provides. Like the
- XPath functions, an extension function returns an XObject, which may contain a value of any of the five XSLT
- data types: node-set, result-tree-fragment, string, boolean, or number.</p>
-<p>You can send arguments to an extension function in the form of XPath expressions, literals (for string, boolean, and number),
- the values returned by other functions, and XSL variables or parameters set to any of the preceding.</p>
-<p>For an example that implements, installs, and uses three extension functions, see the
-<a href="samples.html#externalfunctions">External Functions</a> sample.</p>
-<table class="note">
-<tr>
-<td class="noteImg">
-<img src="resources/note.gif" alt="note" />
-</td>
-<td class="noteTxt">Xalan-C++ does not support extension elements.</td>
-</tr>
-</table>
-
-
-<a name="implement"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Implementing an extension function</h3>
-<p>Like the standard XPath functions, the functions you create derive from the Function base class. Set up your
- extension function class as follows:</p>
-<ol>
- <li>The body of a function is the execute() method. Use the appropriate XObjectFactory method -- createNumber()
- in the example below -- to create an XObject corresponding to the XSLT data type the function returns.<br />
-<br />
-</li>
- <li>Implement a clone() method to enable Xalan to create and maintain a copy of the extension
- function.<br />
-<br />
-</li>
- <li>(Optional) As Xalan does for the XPath functions, you may want to prevent the compiler from generating
- an assignment or equality operator for this function.</li>
-</ol>
-<p>These features all appear in the following example.</p>
-<blockquote class="source">
-<pre>
-// Base header file. Must be first.
-#include <xalanc/Include/PlatformDefinitions.hpp>
-
-#include <cmath>
-#include <ctime>
-
-#include <xercesc/util/PlatformUtils.hpp>
-#include <xalanc/XalanTransformer/XalanTransformer.hpp>
-#include <xalanc/XPath/XObjectFactory.hpp>
-
-XALAN_CPP_NAMESPACE_USE
-
-// This class defines a function that will return the square root
-// of its argument.
-class FunctionSquareRoot : public Function
-{
-public:
-
- /**
- * Execute an XPath function object. The function must return a valid
- * XObject.
- *
- * @param executionContext executing context
- * @param context current context node
- * @param opPos current op position
- * @param args vector of pointers to XObject arguments
- * @return pointer to the result XObject
- */
- virtual XObjectPtr
- execute(
- XPathExecutionContext& executionContext,
- XalanNode* /* context */,
- const XObjectPtr arg,
- const Locator* /* locator */) const
- {
- if (args.size() != 1)
- {
- executionContext.error("The square-root() function takes one argument!",
- context);
- }
- assert(args[0] != 0);
- // Use the XObjectFactory createNumber() method to create an XObject
- // corresponding to the XSLT number data type.
- return executionContext.getXObjectFactory().createNumber(
- sqrt(args[0]->num()));
- }
-
- /**
- * Implement clone() so Xalan can copy the square-root function into
- * its own function table.
- *
- * @return pointer to the new object
- */
-// For compilers that do not support covariant return types,
-// clone() must be declared to return the base type.
-#if defined(XALAN_NO_COVARIANT_RETURN_TYPE)
- virtual Function*
-#else
- virtual FunctionSquareRoot*
-#endif
- clone() const
- {
- return new FunctionSquareRoot(*this);
- }
-
-private:
- // The assignment and equality operators are not implemented...
- FunctionSquareRoot&
- operator=(const FunctionSquareRoot&);
- bool
- operator==(const FunctionSquareRoot&) const;
-}
-</pre>
-</blockquote>
-
-<a name="install"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Installing an extension function</h3>
-<p>
-<a href="apiDocs/classXalanTransformer.html">XalanTransformer</a> provides methods for installing and uninstalling external functions:</p>
-<ul>
- <li>installExternalFunction() makes the function available in the current instance of XalanTransformer. Use uninstallExternalFunction() to remove the function.<br />
-<br />
-</li>
- <li>installExternalFunctionGlobal() makes the function available globally. Use uninstallExternalFunctionGlobal() to remove the function. The global install and uninstall operations are not thread-safe. However, all global functions should be thread-safe, because multiple threads could call a particular function instance at the same time.</li>
-</ul>
-<p>These methods include arguments for the namespace, the function name, and the function implementation.</p>
-<p>When you install an extension function, the function inhabits the namespace you designate. For information about XML namespaces, see <a href="http://www.w3.org/TR/REC-xml-names/">Namespaces in XML</a>.</p>
-<p>The following code fragment installs locally the square root function defined above, and binds it to the extension-function name "square-root" in the namespace "http://MyExternalFunction.mycompany.org" so it can be accessed from stylesheets. Keep in mind that the function name does not need to be the same as the name of the function class, and that a function name may be used more than once provided that each function with that name is installed in a different namespace.</p>
-<blockquote class="source">
-<pre>#include <xalanc/Include/PlatformDefinitions.hpp>
-#include <xercesc/util/PlatformUtils.hpp>
-#include <xalanc/XalanTransformer/XalanTransformer.hpp>
-// You have created a header file for FunctionSquareRoot.
-#include <MyFunctions/FunctionSquareRoot.hpp>
-// The namespace...
-const XalanDOMString
- theNamespace("http://MyExternalFunction.mycompany.org");
-
-theXalanTransformer.installExternalFunction(theNamespace,
- XalanDOMString("square-root"),
- FunctionSquareRoot());</pre>
-</blockquote>
-<p>For an example that installs three functions, see the <a href="samples.html#externalfunctions">External Functions</a> sample.</p>
-
-<a name="use"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Using an extension function</h3>
-<p>To use the extension function in a stylesheet, you must do the following:</p>
-<ol>
- <li>Declare the extension function namespace.<br />
-<br />
- <code>xmlns:<b>
-<i>prefix</i>
-</b>=<b>
-<i>URI</i>
-</b>
-</code>
-<br />
-<br />
- The <b>
-<i>prefix</i>
-</b> identifies the namespace, and <b>
-<i>URI</i>
-</b> matches the namespace specified when the function
- is installed.<br />
-<br />
- By default, namespace declarations are included in the transformation output. To exclude namespaces from the output,
- use<br />
-<br />
- <code>exclude-result-prefixes="<b>
-<i>prefix-1 prefix-2 ...</i>
-</b>"</code>
-<br />
-<br />
- in the stylesheet element or<br />
-<br />
- <code>xsl:exclude-result-prefixes="<b>
-<i>prefix-1 prefix-2 ...</i>
-</b>"</code>
-<br />
-<br />
- in a literal result element or extension element.<br />
-<br />
-</li>
- <li>Call the extension function in the same manner you would call an XPath function. The function name you use in the stylesheet is a Qualified Name (QName) made up of the prefix you declared in step 1 and the function name you specified when you installed the function.<br />
-<br />
- You can use XPath expressions, literals (for string, boolean, and number), and values returned by other functions to
- specify function arguments.</li>
-</ol>
-<p>Suppose, for example, you are working with XML documents containing area elements like
- <code><area value="397"/></code>, where the value attribute identifies the area of a square.</p>
-<p>The following stylesheet declares the square-root function namespace (the prefix is up to you), instructs
- the processor not to copy the namespace declaration to the result tree, and uses the square-root function to return
- the square root of //area/@value:</p>
-<blockquote class="source">
-<pre>
-<?xml version="1.0"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
- version="1.0"
- xmlns:external="http://ExternalFunction.xalan-c.xml.apache.org"
- exclude-result-prefixes="external">
-
- <xsl:template match="//area">
- <out>
- The area of the square is
- <xsl:value-of select="@value"/> square units.
- The length of each side is
- <xsl:value-of select="external:square-root(@value)"/> units
- </out>
-</pre>
-</blockquote>
-<p>This stylesheet converts <code><area value="397"/></code> into the following output:</p>
-<blockquote class="source">
-<pre><out>
- The area of the square is
- 397 square units.
- The length of each side is
- 19.9249 units.
-</out>
-</pre>
-</blockquote>
-<p>For a slightly more complex variation on this example,
-see the <a href="samples.html#externalfunctions">External Functions</a> sample.</p>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Passing Nodes to a function</h4>
-<p>Please keep in mind that <b>all</b> LocationPath expressions return a node-set, even if the expression only
- returns a single attribute or a text node (node-sets with one member). You can use the XSLT string() function
- to convert a node-set value to string, and the number() function to convert a node-set value to number (a double).</p>
-<p>If you pass a node-set to an extension function, be sure to set up the function to process a node-set.</p>
-<p>Suppose, for example, you have a ProcessNodes function class that uses<br />
-<br />
- <code>const NodeRefListBase& theNodeList = args[0]->nodeset();</code>
-<br />
-<br />
- in the execute() method to get a reference to the node-set.</p>
-<p>Assuming you install the function as "ProcessNodes" and use the "node-ext" prefix in a stylesheet to refer to the ProcessNodes function namespace, any of the following function calls are syntactically possible:</p>
-<p>
-<code><!--Process the current node--></code>
-<br />
-<code><xsl:variable name="success" select="node-ext:ProcessNodes(.)"/></code>
-</p>
-<p>
-<code><!--Process all nodes in current context--></code>
-<br />
-<code><xsl:variable name="success" select="node-ext:ProcessNodes(*)"/></code>
-</p>
-<p>
-<code><!-- Process all nodes --></code>
-<br />
-<code><xsl:variable name="success" select="node-ext:ProcessNodes(/*)"/></code>
-</p>
-<p>
-<code><!--Process the foo/baz nodes in current context --></code>
-<br />
-<code><xsl:variable name="success" select="node-ext:ProcessNodes(foo/baz)"/></code>
-</p>
-<p>
-<code><!--Process the/foo/baz and /bar/saz nodes --></code>
-<br />
-<code><xsl:variable name="success" select="node-ext:ProcessNodes(/foo/baz | /bar/saz)"/></code>
-</p>
-<p>The NodeRefListBase is in fact a list of references into the XML document, so keep in mind that getNextSibling(),
-for example, gets you the next sibling in the document, which may not be the next Node in the node-set.</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 2012-10-07</div>
-</div>
-</body>
-</html>
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Xalan-C++ Extension Functions</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * 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.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan-C/C++ Version 1.11</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Xalan-C++ Extension Functions</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="../index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-C++ 1.11</a>
+</li>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="license.html">Licenses</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>
+<a href="charter.html">Charter</a>
+</li></ul><hr /><ul>
+<li>
+<a href="download.html">Download</a>
+</li>
+<li>
+<a href="buildlibs.html">Build Libraries</a>
+</li>
+<li>
+<a href="install.html">Installation</a>
+</li>
+<li>
+<a href="builddocs.html">Build Documents</a>
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>
+<a href="commandline.html">Command Line</a>
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="programming.html">Programming</a>
+</li>
+<li>Extensions<br />
+</li>
+<li>
+<a href="extensionslib.html">Extensions Library</a>
+</li>
+<li>
+<a href="apiDocs/index.html">API Reference</a>
+</li></ul><hr /><ul>
+<li>
+<a href="faq.html">Xalan-C FAQs</a>
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html#bugs">Bugs</a>
+</li>
+<li>
+<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
+</li>
+<li>
+<a href="secureweb.html">Web Security</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<h2>Xalan-C++ Extension Functions</h2>
+<ul>
+ <li>
+<a href="#intro">Introduction</a>
+</li>
+ <li>
+<a href="#implement">Implementing an extension function</a>
+</li>
+ <li>
+<a href="#install">Installing an extension function</a>
+</li>
+ <li>
+<a href="#use">Using an extension function</a>
+</li>
+</ul>
+<a name="intro"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Introduction</h3>
+<p>At times, you may want to call your own custom C functions from a stylesheet. For these situations, Xalan-C++ supports the
+ creation and use of extension functions. Xalan-C++ also provides a <a href="extensionslib.html">library of extension functions
+ </a> for your use.</p>
+<p>You can think of extension functions as extending the core library of functions that XPath provides. Like the
+ XPath functions, an extension function returns an XObject, which may contain a value of any of the five XSLT
+ data types: node-set, result-tree-fragment, string, boolean, or number.</p>
+<p>You can send arguments to an extension function in the form of XPath expressions, literals (for string, boolean, and number),
+ the values returned by other functions, and XSL variables or parameters set to any of the preceding.</p>
+<p>For an example that implements, installs, and uses three extension functions, see the
+<a href="samples.html#externalfunctions">External Functions</a> sample.</p>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">Xalan-C++ does not support extension elements.</td>
+</tr>
+</table>
+
+
+<a name="implement"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Implementing an extension function</h3>
+<p>Like the standard XPath functions, the functions you create derive from the Function base class. Set up your
+ extension function class as follows:</p>
+<ol>
+ <li>The body of a function is the execute() method. Use the appropriate XObjectFactory method -- createNumber()
+ in the example below -- to create an XObject corresponding to the XSLT data type the function returns.<br />
+<br />
+</li>
+ <li>Implement a clone() method to enable Xalan to create and maintain a copy of the extension
+ function.<br />
+<br />
+</li>
+ <li>(Optional) As Xalan does for the XPath functions, you may want to prevent the compiler from generating
+ an assignment or equality operator for this function.</li>
+</ol>
+<p>These features all appear in the following example.</p>
+<blockquote class="source">
+<pre>
+// Base header file. Must be first.
+#include <xalanc/Include/PlatformDefinitions.hpp>
+
+#include <cmath>
+#include <ctime>
+
+#include <xercesc/util/PlatformUtils.hpp>
+#include <xalanc/XalanTransformer/XalanTransformer.hpp>
+#include <xalanc/XPath/XObjectFactory.hpp>
+
+XALAN_CPP_NAMESPACE_USE
+
+// This class defines a function that will return the square root
+// of its argument.
+class FunctionSquareRoot : public Function
+{
+public:
+
+ /**
+ * Execute an XPath function object. The function must return a valid
+ * XObject.
+ *
+ * @param executionContext executing context
+ * @param context current context node
+ * @param opPos current op position
+ * @param args vector of pointers to XObject arguments
+ * @return pointer to the result XObject
+ */
+ virtual XObjectPtr
+ execute(
+ XPathExecutionContext& executionContext,
+ XalanNode* /* context */,
+ const XObjectPtr arg,
+ const Locator* /* locator */) const
+ {
+ if (args.size() != 1)
+ {
+ executionContext.error("The square-root() function takes one argument!",
+ context);
+ }
+ assert(args[0] != 0);
+ // Use the XObjectFactory createNumber() method to create an XObject
+ // corresponding to the XSLT number data type.
+ return executionContext.getXObjectFactory().createNumber(
+ sqrt(args[0]->num()));
+ }
+
+ /**
+ * Implement clone() so Xalan can copy the square-root function into
+ * its own function table.
+ *
+ * @return pointer to the new object
+ */
+// For compilers that do not support covariant return types,
+// clone() must be declared to return the base type.
+#if defined(XALAN_NO_COVARIANT_RETURN_TYPE)
+ virtual Function*
+#else
+ virtual FunctionSquareRoot*
+#endif
+ clone() const
+ {
+ return new FunctionSquareRoot(*this);
+ }
+
+private:
+ // The assignment and equality operators are not implemented...
+ FunctionSquareRoot&
+ operator=(const FunctionSquareRoot&);
+ bool
+ operator==(const FunctionSquareRoot&) const;
+}
+</pre>
+</blockquote>
+
+<a name="install"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Installing an extension function</h3>
+<p>
+<a href="apiDocs/classXalanTransformer.html">XalanTransformer</a> provides methods for installing and uninstalling external functions:</p>
+<ul>
+ <li>installExternalFunction() makes the function available in the current instance of XalanTransformer. Use uninstallExternalFunction() to remove the function.<br />
+<br />
+</li>
+ <li>installExternalFunctionGlobal() makes the function available globally. Use uninstallExternalFunctionGlobal() to remove the function. The global install and uninstall operations are not thread-safe. However, all global functions should be thread-safe, because multiple threads could call a particular function instance at the same time.</li>
+</ul>
+<p>These methods include arguments for the namespace, the function name, and the function implementation.</p>
+<p>When you install an extension function, the function inhabits the namespace you designate. For information about XML namespaces, see <a href="http://www.w3.org/TR/REC-xml-names/">Namespaces in XML</a>.</p>
+<p>The following code fragment installs locally the square root function defined above, and binds it to the extension-function name "square-root" in the namespace "http://MyExternalFunction.mycompany.org" so it can be accessed from stylesheets. Keep in mind that the function name does not need to be the same as the name of the function class, and that a function name may be used more than once provided that each function with that name is installed in a different namespace.</p>
+<blockquote class="source">
+<pre>#include <xalanc/Include/PlatformDefinitions.hpp>
+#include <xercesc/util/PlatformUtils.hpp>
+#include <xalanc/XalanTransformer/XalanTransformer.hpp>
+// You have created a header file for FunctionSquareRoot.
+#include <MyFunctions/FunctionSquareRoot.hpp>
+// The namespace...
+const XalanDOMString
+ theNamespace("http://MyExternalFunction.mycompany.org");
+
+theXalanTransformer.installExternalFunction(theNamespace,
+ XalanDOMString("square-root"),
+ FunctionSquareRoot());</pre>
+</blockquote>
+<p>For an example that installs three functions, see the <a href="samples.html#externalfunctions">External Functions</a> sample.</p>
+
+<a name="use"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Using an extension function</h3>
+<p>To use the extension function in a stylesheet, you must do the following:</p>
+<ol>
+ <li>Declare the extension function namespace.<br />
+<br />
+ <code>xmlns:<b>
+<i>prefix</i>
+</b>=<b>
+<i>URI</i>
+</b>
+</code>
+<br />
+<br />
+ The <b>
+<i>prefix</i>
+</b> identifies the namespace, and <b>
+<i>URI</i>
+</b> matches the namespace specified when the function
+ is installed.<br />
+<br />
+ By default, namespace declarations are included in the transformation output. To exclude namespaces from the output,
+ use<br />
+<br />
+ <code>exclude-result-prefixes="<b>
+<i>prefix-1 prefix-2 ...</i>
+</b>"</code>
+<br />
+<br />
+ in the stylesheet element or<br />
+<br />
+ <code>xsl:exclude-result-prefixes="<b>
+<i>prefix-1 prefix-2 ...</i>
+</b>"</code>
+<br />
+<br />
+ in a literal result element or extension element.<br />
+<br />
+</li>
+ <li>Call the extension function in the same manner you would call an XPath function. The function name you use in the stylesheet is a Qualified Name (QName) made up of the prefix you declared in step 1 and the function name you specified when you installed the function.<br />
+<br />
+ You can use XPath expressions, literals (for string, boolean, and number), and values returned by other functions to
+ specify function arguments.</li>
+</ol>
+<p>Suppose, for example, you are working with XML documents containing area elements like
+ <code><area value="397"/></code>, where the value attribute identifies the area of a square.</p>
+<p>The following stylesheet declares the square-root function namespace (the prefix is up to you), instructs
+ the processor not to copy the namespace declaration to the result tree, and uses the square-root function to return
+ the square root of //area/@value:</p>
+<blockquote class="source">
+<pre>
+<?xml version="1.0"?>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ version="1.0"
+ xmlns:external="http://ExternalFunction.xalan-c.xml.apache.org"
+ exclude-result-prefixes="external">
+
+ <xsl:template match="//area">
+ <out>
+ The area of the square is
+ <xsl:value-of select="@value"/> square units.
+ The length of each side is
+ <xsl:value-of select="external:square-root(@value)"/> units
+ </out>
+</pre>
+</blockquote>
+<p>This stylesheet converts <code><area value="397"/></code> into the following output:</p>
+<blockquote class="source">
+<pre><out>
+ The area of the square is
+ 397 square units.
+ The length of each side is
+ 19.9249 units.
+</out>
+</pre>
+</blockquote>
+<p>For a slightly more complex variation on this example,
+see the <a href="samples.html#externalfunctions">External Functions</a> sample.</p>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Passing Nodes to a function</h4>
+<p>Please keep in mind that <b>all</b> LocationPath expressions return a node-set, even if the expression only
+ returns a single attribute or a text node (node-sets with one member). You can use the XSLT string() function
+ to convert a node-set value to string, and the number() function to convert a node-set value to number (a double).</p>
+<p>If you pass a node-set to an extension function, be sure to set up the function to process a node-set.</p>
+<p>Suppose, for example, you have a ProcessNodes function class that uses<br />
+<br />
+ <code>const NodeRefListBase& theNodeList = args[0]->nodeset();</code>
+<br />
+<br />
+ in the execute() method to get a reference to the node-set.</p>
+<p>Assuming you install the function as "ProcessNodes" and use the "node-ext" prefix in a stylesheet to refer to the ProcessNodes function namespace, any of the following function calls are syntactically possible:</p>
+<p>
+<code><!--Process the current node--></code>
+<br />
+<code><xsl:variable name="success" select="node-ext:ProcessNodes(.)"/></code>
+</p>
+<p>
+<code><!--Process all nodes in current context--></code>
+<br />
+<code><xsl:variable name="success" select="node-ext:ProcessNodes(*)"/></code>
+</p>
+<p>
+<code><!-- Process all nodes --></code>
+<br />
+<code><xsl:variable name="success" select="node-ext:ProcessNodes(/*)"/></code>
+</p>
+<p>
+<code><!--Process the foo/baz nodes in current context --></code>
+<br />
+<code><xsl:variable name="success" select="node-ext:ProcessNodes(foo/baz)"/></code>
+</p>
+<p>
+<code><!--Process the/foo/baz and /bar/saz nodes --></code>
+<br />
+<code><xsl:variable name="success" select="node-ext:ProcessNodes(/foo/baz | /bar/saz)"/></code>
+</p>
+<p>The NodeRefListBase is in fact a list of references into the XML document, so keep in mind that getNextSibling(),
+for example, gets you the next sibling in the document, which may not be the next Node in the node-set.</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 - Tue 2012-10-09</div>
+</div>
+</body>
+</html>
diff --git a/docs/xalan/xalan-c/extensionslib.html b/docs/xalan/xalan-c/extensionslib.html
index 167a8e5..67aa2e6 100644
--- a/docs/xalan/xalan-c/extensionslib.html
+++ b/docs/xalan/xalan-c/extensionslib.html
@@ -1,368 +1,368 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html>
-<head>
-<title>ASF: Extensions library</title>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
-</head>
-<!--
- * 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.
- -->
-<body>
-<div id="title">
-<table class="HdrTitle">
-<tbody>
-<tr>
-<th rowspan="2">
-<a href="../index.html">
-<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
-</a>
-</th>
-<th text-align="center" width="75%">
-<a href="index.html">Xalan-C/C++ Version 1.11</a>
-</th>
-</tr>
-<tr>
-<td valign="middle">Extensions library</td>
-</tr>
-</tbody>
-</table>
-<table class="HdrButtons" align="center" border="1">
-<tbody>
-<tr>
-<td>
-<a href="http://www.apache.org">Apache Foundation</a>
-</td>
-<td>
-<a href="http://xalan.apache.org">Xalan Project</a>
-</td>
-<td>
-<a href="http://xerces.apache.org">Xerces Project</a>
-</td>
-<td>
-<a href="http://www.w3.org/TR">Web Consortium</a>
-</td>
-<td>
-<a href="http://www.oasis-open.org/standards">Oasis Open</a>
-</td>
-</tr>
-</tbody>
-</table>
-</div>
-<div id="navLeft">
-<ul>
-<li>
-<a href="resources.html">Resources</a>
-<br />
-</li>
-<li>
-<a href="../index.html">Home</a>
-</li></ul><hr /><ul>
-<li>
-<a href="index.html">Xalan-C++ 1.11</a>
-</li>
-<li>
-<a href="whatsnew.html">What's New</a>
-</li>
-<li>
-<a href="license.html">Licenses</a>
-</li></ul><hr /><ul>
-<li>
-<a href="overview.html">Overview</a>
-</li>
-<li>
-<a href="charter.html">Charter</a>
-</li></ul><hr /><ul>
-<li>
-<a href="download.html">Download</a>
-</li>
-<li>
-<a href="buildlibs.html">Build Libraries</a>
-</li>
-<li>
-<a href="install.html">Installation</a>
-</li>
-<li>
-<a href="builddocs.html">Build Documents</a>
-</li></ul><hr /><ul>
-<li>
-<a href="samples.html">Sample Apps</a>
-</li>
-<li>
-<a href="commandline.html">Command Line</a>
-</li>
-<li>
-<a href="usagepatterns.html">Usage Patterns</a>
-</li></ul><hr /><ul>
-<li>
-<a href="programming.html">Programming</a>
-</li>
-<li>
-<a href="extensions.html">Extensions</a>
-</li>
-<li>Extensions Library<br />
-</li>
-<li>
-<a href="apiDocs/index.html">API Reference</a>
-</li></ul><hr /><ul>
-<li>
-<a href="faq.html">Xalan-C FAQs</a>
-</li></ul><hr /><ul>
-<li>
-<a href="whatsnew.html#bugs">Bugs</a>
-</li>
-<li>
-<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
-</li>
-<li>
-<a href="secureweb.html">Web Security</a>
-</li>
-</ul>
-</div>
-<div id="content">
-<h2>Extensions library</h2>
-<ul>
- <li>
-<a href="#intro">Introduction</a>
-</li>
- <li>
-<a href="#exslt">Beta support for EXSLT extensions</a>
-</li>
- <li>
-<a href="#xalanns">Xalan namespace</a>
-</li>
- <li>
-<a href="#nodeset">nodeset</a>
-</li>
- <li>
-<a href="#intersection">intersection</a>
-</li>
- <li>
-<a href="#difference">difference</a>
-</li>
- <li>
-<a href="#distinct">distinct</a>
-</li>
- <li>
-<a href="#evaluate">evaluate</a>
-</li>
- <li>
-<a href="#hassamenodes">hasSameNodes</a>
-</li>
-</ul>
-
-<a name="intro"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Introduction</h3>
-<p>Extension functions provide a powerful mechanism
- for extending and simplifying what you can do with an XLST processor like
- Xalan. With input and contributions from the XML open-source developer community, we are working on placing the most useful
- extensions in an extensions library distributed with Xalan-C++. If you have ideas and/or contributions you would like to make,
- please email us at the <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a>.</p>
-
-
-<a name="exslt"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>EXSLT extensions</h3>
-<p>Xalan-C++ supports the <a href="http://exslt.org/">EXSLT</a> initiative to provide a set of
- standard extension functions to XSLT users. Xalan-C++ includes beta implementations for
- functions in four of the EXSLT namespaces (some are calls to extension already in the Xalan namespace).</p>
-<p>The source files for the implementations are in the XalanEXSLT subdirectory of the source tree. See</p>
-<ul>
- <li>
-<a href="apiDocs/XalanEXSLTCommonImpl_8hpp.html">XalanEXSLTCommonImpl</a>
-</li>
- <li>
-<a href="apiDocs/XalanEXSLTMathImpl_8hpp.html">XalanEXSLTMathImpl</a>
-</li>
- <li>
-<a href="apiDocs/XalanEXSLTSetImpl_8hpp.html">XalanEXSLTSetImpl</a>
-</li>
- <li>
-<a href="apiDocs/XalanEXSLTStringImpl_8hpp.html">XalanEXSLTStringImpl</a>
-</li>
- <li>
-<a href="apiDocs/XalanEXSLTDynamicImpl_8hpp.html">XalanEXSLTDynamicImpl</a>
-</li>
- <li>
-<a href="apiDocs/XalanEXSLTDateTimeImpl_8hpp.html">XalanEXSLTDateTimeImpl</a>
-</li>
-</ul>
-<p>For the function specifications, see:</p>
-<ul>
- <li>
-<a href="http://www.exslt.org/exsl/exsl.html">EXSLT common functions</a>
-</li>
- <li>
-<a href="http://www.exslt.org/math/math.html">EXSLT math functions</a>
-</li>
- <li>
-<a href="http://www.exslt.org/set/set.html">EXSLT set functions</a>
-</li>
- <li>
-<a href="http://www.exslt.org/str/str.html">EXSLT string functions</a>
-</li>
- <li>
-<a href="http://www.exslt.org/dyn/dyn.html">EXSLT dynamic functions</a>
-</li>
- <li>
-<a href="http://www.exslt.org/date/date.html">EXSLT date-time functions</a>
-</li>
-</ul>
-<p>Anyone who would like to participate in the Xalan-C++ initiative to support EXSLT by testing these implementations or implementing
- other EXSLT functions is more than welcome. Please email us at the <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a>.</p>
-
-
-<a name="xalanns"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Xalan namespace</h3>
-<p>We are placing the Xalan extension functions in the XalanExtensions module and we have defined a namespace for this module:</p>
-<p> <code>http://xml.apache.org/xalan</code>
-</p>
-<p>If you are calling Xalan-C++-supplied extensions, we recommend that you define this namespace in your stylesheet element, and
- call the extension using the namespace prefix that you have associated with that namespace. That way, if we later reorganize
- how the Xalan-C++-supplied extensions are stored, you won't have to modify your stylesheet.</p>
-<p>For an example that uses this namespace, see <a href="#ex-nodeset">Example with the nodeset extension function</a>.</p>
-
-
-<a name="nodeset"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>nodeset</h3>
-<p>Implemented in <a href="apiDocs/classFunctionNodeSet.html">FunctionNodeSet</a>, <code>nodeset (result-tree-fragment)</code>
- casts a result tree fragment into a node-set.</p>
-<table class="note">
-<tr>
-<td class="noteImg">
-<img src="resources/note.gif" alt="note" />
-</td>
-<td class="noteTxt">When you bind a variable to a template, rather than to the value generated by a select expression, the data type of the variable
- is result tree fragment. For more information, see <a href="http://www.w3.org/TR/xslt#section-Result-Tree-Fragments">Result
- Tree Fragments</a>.</td>
-</tr>
-</table>
-
-<a name="ex-nodeset"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>Example with the nodeset extension function</h4>
-<p>The following stylesheet uses the nodeset extension function to cast a result tree fragment into a node-set that can then be
- navigated in standard XPath manner. It uses the http://xml.apache.org/xalan namespace to provide access to the nodeset() method
- in xml.apache.xalan.lib.Extensions.</p>
-<blockquote class="source">
-<pre>
-<?xml version="1.0"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
- version="1.0"
- xmlns:xalan="http://xml.apache.org/xalan"
- exclude-result-prefixes="xalan">
-<xsl:template match="/">
- <out>
- <xsl:variable name="rtf">
- <docelem>
- <elem1>
- <elem1a>ELEMENT1A</elem1a>
- <elem1b>,ELEMENT1B</elem1b>
- </elem1>
- <elem2>
- <elem2a>ELEMENT2A</elem2a>
- </elem2>
- </docelem>
- </xsl:variable>
- <xsl:for-each select="xalan:nodeset($rtf)/docelem//*">
- <xsl:value-of select="name(.)"/><xsl:text>,</xsl:text>
- </xsl:for-each>
- </out>
-</xsl:template>
-</xsl:stylesheet>
-</pre>
-</blockquote>
-<p>The output of running this stylesheet (with any XML input source) is a comma-delimited list of the element names in the node-set<br />
- <code><out>elem1,elem1a,elem1b,elem2,elem2a</out></code>
-</p>
-<table class="note">
-<tr>
-<td class="noteImg">
-<img src="resources/note.gif" alt="note" />
-</td>
-<td class="noteTxt">For illustration purposes, the preceding stylesheet pays no attention to the structure and content of the XML input document.
- Instead, it processes the template (in the stylesheet) bound to the variable named rtf.</td>
-</tr>
-</table>
-
-
-<a name="intersection"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>intersection</h3>
-<p>Implemented in <a href="apiDocs/classFunctionIntersection.html">FunctionIntersection</a>, <code>intersection (node-set1,
- node-set2)</code> returns a node-set with all nodes that are in ns1 and in ns2.</p>
-
-<a name="difference"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>difference</h3>
-<p>Implemented in <a href="apiDocs/classFunctionDifference.html">FunctionDifference</a>, <code>difference(node-set1,
- node-set2)</code> returns a node-set with the nodes in node-set1 and not in node-set2.</p>
-
-<a name="distinct"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>distinct</h3>
-<p>Implemented in <a href="apiDocs/classFunctionDistinct.html">FunctionDistinct</a>, distinct (node-set) returns a node-set
- containing nodes with distinct string values. If more than one node in the node-set contains the same text node value, distinct
- only returns the first of these nodes that it finds.</p>
-
-<a name="evaluate"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>evaluate</h3>
-<p>Implemented in <a href="apiDocs/classFunctionEvaluate.html">FunctionEvaluate</a>, <code>evaluate (xpath-expression)</code>
- returns the result of evaluating the xpath-expression in the current XPath expression context (automatically passed in by the
- extension mechanism).</p>
-<p>Use the evaluation extension function when the value of the expression is not known until run time.</p>
-
-<a name="hassamenodes"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>hasSameNodes</h3>
-<p>Implemented in <a href="apiDocs/classFunctionHasSameNodes.html">FunctionHasSameNodes</a>, <code>hasSameNodes(node-set1,
- node-set2)</code> returns true if both node-set1 and node-set2 contain exactly the same set of nodes.</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 2012-10-07</div>
-</div>
-</body>
-</html>
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Extensions library</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * 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.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan-C/C++ Version 1.11</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Extensions library</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="../index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-C++ 1.11</a>
+</li>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="license.html">Licenses</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>
+<a href="charter.html">Charter</a>
+</li></ul><hr /><ul>
+<li>
+<a href="download.html">Download</a>
+</li>
+<li>
+<a href="buildlibs.html">Build Libraries</a>
+</li>
+<li>
+<a href="install.html">Installation</a>
+</li>
+<li>
+<a href="builddocs.html">Build Documents</a>
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>
+<a href="commandline.html">Command Line</a>
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="programming.html">Programming</a>
+</li>
+<li>
+<a href="extensions.html">Extensions</a>
+</li>
+<li>Extensions Library<br />
+</li>
+<li>
+<a href="apiDocs/index.html">API Reference</a>
+</li></ul><hr /><ul>
+<li>
+<a href="faq.html">Xalan-C FAQs</a>
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html#bugs">Bugs</a>
+</li>
+<li>
+<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
+</li>
+<li>
+<a href="secureweb.html">Web Security</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<h2>Extensions library</h2>
+<ul>
+ <li>
+<a href="#intro">Introduction</a>
+</li>
+ <li>
+<a href="#exslt">Beta support for EXSLT extensions</a>
+</li>
+ <li>
+<a href="#xalanns">Xalan namespace</a>
+</li>
+ <li>
+<a href="#nodeset">nodeset</a>
+</li>
+ <li>
+<a href="#intersection">intersection</a>
+</li>
+ <li>
+<a href="#difference">difference</a>
+</li>
+ <li>
+<a href="#distinct">distinct</a>
+</li>
+ <li>
+<a href="#evaluate">evaluate</a>
+</li>
+ <li>
+<a href="#hassamenodes">hasSameNodes</a>
+</li>
+</ul>
+
+<a name="intro"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Introduction</h3>
+<p>Extension functions provide a powerful mechanism
+ for extending and simplifying what you can do with an XLST processor like
+ Xalan. With input and contributions from the XML open-source developer community, we are working on placing the most useful
+ extensions in an extensions library distributed with Xalan-C++. If you have ideas and/or contributions you would like to make,
+ please email us at the <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a>.</p>
+
+
+<a name="exslt"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>EXSLT extensions</h3>
+<p>Xalan-C++ supports the <a href="http://exslt.org/">EXSLT</a> initiative to provide a set of
+ standard extension functions to XSLT users. Xalan-C++ includes beta implementations for
+ functions in four of the EXSLT namespaces (some are calls to extension already in the Xalan namespace).</p>
+<p>The source files for the implementations are in the XalanEXSLT subdirectory of the source tree. See</p>
+<ul>
+ <li>
+<a href="apiDocs/XalanEXSLTCommonImpl_8hpp.html">XalanEXSLTCommonImpl</a>
+</li>
+ <li>
+<a href="apiDocs/XalanEXSLTMathImpl_8hpp.html">XalanEXSLTMathImpl</a>
+</li>
+ <li>
+<a href="apiDocs/XalanEXSLTSetImpl_8hpp.html">XalanEXSLTSetImpl</a>
+</li>
+ <li>
+<a href="apiDocs/XalanEXSLTStringImpl_8hpp.html">XalanEXSLTStringImpl</a>
+</li>
+ <li>
+<a href="apiDocs/XalanEXSLTDynamicImpl_8hpp.html">XalanEXSLTDynamicImpl</a>
+</li>
+ <li>
+<a href="apiDocs/XalanEXSLTDateTimeImpl_8hpp.html">XalanEXSLTDateTimeImpl</a>
+</li>
+</ul>
+<p>For the function specifications, see:</p>
+<ul>
+ <li>
+<a href="http://www.exslt.org/exsl/exsl.html">EXSLT common functions</a>
+</li>
+ <li>
+<a href="http://www.exslt.org/math/math.html">EXSLT math functions</a>
+</li>
+ <li>
+<a href="http://www.exslt.org/set/set.html">EXSLT set functions</a>
+</li>
+ <li>
+<a href="http://www.exslt.org/str/str.html">EXSLT string functions</a>
+</li>
+ <li>
+<a href="http://www.exslt.org/dyn/dyn.html">EXSLT dynamic functions</a>
+</li>
+ <li>
+<a href="http://www.exslt.org/date/date.html">EXSLT date-time functions</a>
+</li>
+</ul>
+<p>Anyone who would like to participate in the Xalan-C++ initiative to support EXSLT by testing these implementations or implementing
+ other EXSLT functions is more than welcome. Please email us at the <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a>.</p>
+
+
+<a name="xalanns"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Xalan namespace</h3>
+<p>We are placing the Xalan extension functions in the XalanExtensions module and we have defined a namespace for this module:</p>
+<p> <code>http://xml.apache.org/xalan</code>
+</p>
+<p>If you are calling Xalan-C++-supplied extensions, we recommend that you define this namespace in your stylesheet element, and
+ call the extension using the namespace prefix that you have associated with that namespace. That way, if we later reorganize
+ how the Xalan-C++-supplied extensions are stored, you won't have to modify your stylesheet.</p>
+<p>For an example that uses this namespace, see <a href="#ex-nodeset">Example with the nodeset extension function</a>.</p>
+
+
+<a name="nodeset"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>nodeset</h3>
+<p>Implemented in <a href="apiDocs/classFunctionNodeSet.html">FunctionNodeSet</a>, <code>nodeset (result-tree-fragment)</code>
+ casts a result tree fragment into a node-set.</p>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">When you bind a variable to a template, rather than to the value generated by a select expression, the data type of the variable
+ is result tree fragment. For more information, see <a href="http://www.w3.org/TR/xslt#section-Result-Tree-Fragments">Result
+ Tree Fragments</a>.</td>
+</tr>
+</table>
+
+<a name="ex-nodeset"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Example with the nodeset extension function</h4>
+<p>The following stylesheet uses the nodeset extension function to cast a result tree fragment into a node-set that can then be
+ navigated in standard XPath manner. It uses the http://xml.apache.org/xalan namespace to provide access to the nodeset() method
+ in xml.apache.xalan.lib.Extensions.</p>
+<blockquote class="source">
+<pre>
+<?xml version="1.0"?>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ version="1.0"
+ xmlns:xalan="http://xml.apache.org/xalan"
+ exclude-result-prefixes="xalan">
+<xsl:template match="/">
+ <out>
+ <xsl:variable name="rtf">
+ <docelem>
+ <elem1>
+ <elem1a>ELEMENT1A</elem1a>
+ <elem1b>,ELEMENT1B</elem1b>
+ </elem1>
+ <elem2>
+ <elem2a>ELEMENT2A</elem2a>
+ </elem2>
+ </docelem>
+ </xsl:variable>
+ <xsl:for-each select="xalan:nodeset($rtf)/docelem//*">
+ <xsl:value-of select="name(.)"/><xsl:text>,</xsl:text>
+ </xsl:for-each>
+ </out>
+</xsl:template>
+</xsl:stylesheet>
+</pre>
+</blockquote>
+<p>The output of running this stylesheet (with any XML input source) is a comma-delimited list of the element names in the node-set<br />
+ <code><out>elem1,elem1a,elem1b,elem2,elem2a</out></code>
+</p>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">For illustration purposes, the preceding stylesheet pays no attention to the structure and content of the XML input document.
+ Instead, it processes the template (in the stylesheet) bound to the variable named rtf.</td>
+</tr>
+</table>
+
+
+<a name="intersection"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>intersection</h3>
+<p>Implemented in <a href="apiDocs/classFunctionIntersection.html">FunctionIntersection</a>, <code>intersection (node-set1,
+ node-set2)</code> returns a node-set with all nodes that are in ns1 and in ns2.</p>
+
+<a name="difference"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>difference</h3>
+<p>Implemented in <a href="apiDocs/classFunctionDifference.html">FunctionDifference</a>, <code>difference(node-set1,
+ node-set2)</code> returns a node-set with the nodes in node-set1 and not in node-set2.</p>
+
+<a name="distinct"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>distinct</h3>
+<p>Implemented in <a href="apiDocs/classFunctionDistinct.html">FunctionDistinct</a>, distinct (node-set) returns a node-set
+ containing nodes with distinct string values. If more than one node in the node-set contains the same text node value, distinct
+ only returns the first of these nodes that it finds.</p>
+
+<a name="evaluate"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>evaluate</h3>
+<p>Implemented in <a href="apiDocs/classFunctionEvaluate.html">FunctionEvaluate</a>, <code>evaluate (xpath-expression)</code>
+ returns the result of evaluating the xpath-expression in the current XPath expression context (automatically passed in by the
+ extension mechanism).</p>
+<p>Use the evaluation extension function when the value of the expression is not known until run time.</p>
+
+<a name="hassamenodes"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>hasSameNodes</h3>
+<p>Implemented in <a href="apiDocs/classFunctionHasSameNodes.html">FunctionHasSameNodes</a>, <code>hasSameNodes(node-set1,
+ node-set2)</code> returns true if both node-set1 and node-set2 contain exactly the same set of nodes.</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 - Tue 2012-10-09</div>
+</div>
+</body>
+</html>
diff --git a/docs/xalan/xalan-c/faq.html b/docs/xalan/xalan-c/faq.html
index 939e4a8..9e3a0e4 100644
--- a/docs/xalan/xalan-c/faq.html
+++ b/docs/xalan/xalan-c/faq.html
@@ -1,732 +1,732 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html>
-<head>
-<title>ASF: Frequently asked questions</title>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
-</head>
-<!--
- * 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.
- -->
-<body>
-<div id="title">
-<table class="HdrTitle">
-<tbody>
-<tr>
-<th rowspan="2">
-<a href="../index.html">
-<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
-</a>
-</th>
-<th text-align="center" width="75%">
-<a href="index.html">Xalan-C/C++ Version 1.11</a>
-</th>
-</tr>
-<tr>
-<td valign="middle">Frequently asked questions</td>
-</tr>
-</tbody>
-</table>
-<table class="HdrButtons" align="center" border="1">
-<tbody>
-<tr>
-<td>
-<a href="http://www.apache.org">Apache Foundation</a>
-</td>
-<td>
-<a href="http://xalan.apache.org">Xalan Project</a>
-</td>
-<td>
-<a href="http://xerces.apache.org">Xerces Project</a>
-</td>
-<td>
-<a href="http://www.w3.org/TR">Web Consortium</a>
-</td>
-<td>
-<a href="http://www.oasis-open.org/standards">Oasis Open</a>
-</td>
-</tr>
-</tbody>
-</table>
-</div>
-<div id="navLeft">
-<ul>
-<li>
-<a href="resources.html">Resources</a>
-<br />
-</li>
-<li>
-<a href="../index.html">Home</a>
-</li></ul><hr /><ul>
-<li>
-<a href="index.html">Xalan-C++ 1.11</a>
-</li>
-<li>
-<a href="whatsnew.html">What's New</a>
-</li>
-<li>
-<a href="license.html">Licenses</a>
-</li></ul><hr /><ul>
-<li>
-<a href="overview.html">Overview</a>
-</li>
-<li>
-<a href="charter.html">Charter</a>
-</li></ul><hr /><ul>
-<li>
-<a href="download.html">Download</a>
-</li>
-<li>
-<a href="buildlibs.html">Build Libraries</a>
-</li>
-<li>
-<a href="install.html">Installation</a>
-</li>
-<li>
-<a href="builddocs.html">Build Documents</a>
-</li></ul><hr /><ul>
-<li>
-<a href="samples.html">Sample Apps</a>
-</li>
-<li>
-<a href="commandline.html">Command Line</a>
-</li>
-<li>
-<a href="usagepatterns.html">Usage Patterns</a>
-</li></ul><hr /><ul>
-<li>
-<a href="programming.html">Programming</a>
-</li>
-<li>
-<a href="extensions.html">Extensions</a>
-</li>
-<li>
-<a href="extensionslib.html">Extensions Library</a>
-</li>
-<li>
-<a href="apiDocs/index.html">API Reference</a>
-</li></ul><hr /><ul>
-<li>Xalan-C FAQs<br />
-</li></ul><hr /><ul>
-<li>
-<a href="whatsnew.html#bugs">Bugs</a>
-</li>
-<li>
-<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
-</li>
-<li>
-<a href="secureweb.html">Web Security</a>
-</li>
-</ul>
-</div>
-<div id="content">
-<h2 class="faqSubHead">Questions</h2>
-<ol start="1">
-<li>
-<a href="#faq-1">Where do I go to learn about XSLT</a>
-</li>
-<li>
-<a href="#faq-2">Asking questions about Xalan-C++</a>
-</li>
-<li>
-<a href="#faq-3">What is Xerces-C++?</a>
-</li>
-<li>
-<a href="#faq-4">Which version of Xerces should I be using?</a>
-</li>
-<li>
-<a href="#faq-5">Should I be using the Xerces DOM or Xalan DOM?</a>
-</li>
-<li>
-<a href="#faq-6">Problems with samples in Windows</a>
-</li>
-<li>
-<a href="#faq-7">Building on Windows</a>
-</li>
-<li>
-<a href="#faq-8">Building on UNIX</a>
-</li>
-<li>
-<a href="#faq-9">Make errors on UNIX platforms</a>
-</li>
-<li>
-<a href="#faq-10">What is ICU</a>
-</li>
-<li>
-<a href="#faq-11">A tar checksum error on Solaris</a>
-</li>
-<li>
-<a href="#faq-12">Xalan-C++ in Apache</a>
-</li>
-<li>
-<a href="#faq-13">Is Xalan-C++ thread-safe?</a>
-</li>
-<li>
-<a href="#faq-14">What can I do to speed up transformations?</a>
-</li>
-<li>
-<a href="#faq-15">Stylesheet validation</a>
-</li>
-<li>
-<a href="#faq-16">What does the XalanDOMException HIERARCHY_REQUEST_ERR mean?</a>
-</li>
-<li>
-<a href="#faq-17">Submitting Patches</a>
-</li>
-<li>
-<a href="#faq-18">Transformation Output Methods</a>
-</li>
-<li>
-<a href="#faq-19">Problems Using Sun's Forte/Workshop Compiler with code containing std::istrstream</a>
-</li>
-<li>
-<a href="#faq-20">Modifying an instance of XalanDocument</a>
-</li>
-<li>
-<a href="#faq-21">Changing Where Error Output is Sent</a>
-</li>
-<li>
-<a href="#faq-22">Programmatic Error Information</a>
-</li>
-<li>
-<a href="#faq-23">String Transcoding</a>
-</li>
-<li>
-<a href="#faq-24">Error Code/Exception Summary</a>
-</li>
-<li>
-<a href="#faq-25">Extension Functions</a>
-</li>
-<li>
-<a href="#faq-26">Outputting results to a file on Windows 95/98</a>
-</li>
-<li>
-<a href="#faq-27">Using format-number and ICU</a>
-</li>
-<li>
-<a href="#faq-28">Perl wrapper for Xalan-C++?</a>
-</li>
-<li>
-<a href="#faq-29">Missing LocalMsgIndex.hpp file</a>
-</li>
-</ol>
-<h2 class="faqSubHead">Answers</h2>
-<h3 id="faq-1" class="faqTitle">1. Where do I go to learn about XSLT</h3>
-<div class="faqQuestion">Where do I go to learn about XSLT?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>The definitive sources are the W3C XSLT and XPath recommendations: <a href="http://www.w3.org/TR/xslt">W3C Recommendation 16 November 1999 XSL Transformations (XSLT) Version 1.0</a> and
- <a href="http://www.w3.org/TR/xpath">XML Path Language (XPath) Version 1.0</a>.</p>
- <p>For a brief listing of tutorials, discussion forums, and other materials, see <a href="overview.html#uptospeed">Getting up to speed with XSLT</a>.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-2" class="faqTitle">2. Asking questions about Xalan-C++</h3>
-<div class="faqQuestion">Where can I ask a question?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>For specific questions on Xalan-C++, see list archives:
- <a href="http://marc.info/?l=xalan-c-users">xalan-c-users</a>
- and <a href="http://marc.info/?l=xalan-dev">xalan-dev</a>.
- You must subscribe to these Apache mailing lists before posting your questions.</p>
-<p>The Apache Software Foundation has information on how you can subscribe to
- the <a href="http://www.apache.org/foundation/mailinglists.html">mailing lists</a>.</p>
-<p>You can post messages to the lists by sending mail to:<br />
- <a href="mailto:c-users@xalan.apache.org">Post message to xalan-c-users</a>. (User's list)<br />
- <a href="mailto:dev@xalan.apache.org">Post message to xalan-dev list</a>. (Developer's list)</p>
-<p>Again, please review the archives before posting a new question.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-3" class="faqTitle">3. What is Xerces-C++?</h3>
-<div class="faqQuestion">What is Xerces-C++ and why do I need it?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>Xerces-C++ is a validating XML parser written in a portable subset of C++. Xerces-C++ makes it easy to give your application the ability
- to read and write XML data. Like Xalan-C++, Xerces-C++ is available from the Apache XML site:
- <a href="http://xerces.apache.org/index.html">http://xerces.apache.org</a>
-</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-4" class="faqTitle">4. Which version of Xerces should I be using?</h3>
-<div class="faqQuestion">Which version of Xerces should I be using?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>The Xalan-C++ release notes includes information about the Xerces-C++ release with which the Xalan-C++ release has been coordinated
- and tested. See <a href="whatsnew.html#status">Status</a>
-</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-5" class="faqTitle">5. Should I be using the Xerces DOM or Xalan DOM?</h3>
-<div class="faqQuestion">Should I be using the Xerces DOM or Xalan DOM?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>The Xalan DOM implementation is highly optimised for transformations. However, whilst you can build documents in the Xalan DOM,
- subsequent modification will not work. The Xalan DOM is designed to be either an input or an output from a transformation, not
- as a general DOM implementation.</p>
- <p>So in cases where you want to simply transform documents using Xalan, using the internal DOM implementation is the best approach.</p>
- <p>In cases where you want to modify the DOM document on the fly, you should use the Xerces DOM as the base document. You can wrap
- the Xerces DOM in a wrapper (see <a href="usagepatterns.html#xercesdomwrapperparsedsource"> passing in a Xerces DOM</a>)
- to then use as an input to a Xalan transformation. Alternatively you can output the result of a transformation to a Xerces DOM
- document (see <a href="usagepatterns.html#dom">working with DOM input and output</a>). In either case, the Xerces document
- can be freely modified. However, after you modify the document, you need to re-build the wrapper so that any changes are replicated
- in the Xalan wrappers.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-6" class="faqTitle">6. Problems with samples in Windows</h3>
-<div class="faqQuestion">I have encountered problem executing the Xalan-C++ sample applications after rebuilding them under Win32 Environment (Windows NT 4.0, SP3).
- When I tried to execute the sample, I receive the error message
- "Debug Assertion Failed! ... Expression: _BLOCK_TYPE_IS_VALID(pHead->nBlockUse)".</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>You may be mixing debug and release versions of executables and libraries. In other words, if you are compiling the sample for debug,
- then you should link with the debug version of the Xalan-C++ and Xerces-C++ libraries and run with the debug version of the dynamic link
- libraries.</p>
- <p>You must also make sure your application is linking with the Debug multithreaded DLL run-time library or the Multithreaded DLL
- run-time library. To check this setting do the following in Visual C++:</p>
- <ol>
- <li>Select Settings from the Project menu.<br />
-<br />
-</li>
- <li>Click the C/C++ tab.<br />
-<br />
-</li>
- <li>In the Category drop-down list, select Code Generation.<br />
-<br />
-</li>
- <li>In the Use run-time library drop-down list, select Multithreaded DLL for the Win32 Release configuration, or select Debug
- Multithreaded DLL for the Win32 Debug configuration.</li>
- </ol>
- <p>Once you have changed this setting, you must rebuild your project.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-7" class="faqTitle">7. Building on Windows</h3>
-<div class="faqQuestion">What do I need to rebuild Xalan-C++ on Windows?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>In order to build Xalan-C++ on Windows, you will need the following:</p>
-<ul>
-<li>The Xalan-C/C++ source distribution package.</li>
-<li>The Xerces-C/C++ source distribution package or a compatible binary distribution package.</li>
-<li>A compatible Microsoft Visual Studio .NET (2003, 2005, 2008, 2010) software development platform.</li>
-</ul>
-<p>The Xalan-C/C++ Version 1.11 (pre-release) is available from the Apache Subversion
- repository at <b>http://svn.apache.org/repos/asf/xalan/c/trunk/.</b>
-</p>
-<p>After Xalan-C/C++ Version 1.11 is released, it can be downloaded from:
- <a href="http://www.apache.org/dyn/closer.cgi/xalan/xalan-c">Xalan Distributions</a>.</p>
-<p>The Xerces-C/C++ Version 3.1.1 is can be downloaded from:
- <a href="http://www.apache.org/dyn/closer.cgi/xerces/c/3">Xerces Distributions</a>.</p>
-<p>If you are building with the
- <a href="http://www.ibm.com/software/globalization/icu/">IBM-ICU</a>
- International Components for Unicode library, you will
- need to rebuild both the Xerces and Xalan libraries.</p>
-<p>For more details, see <a href="buildlibs.html#winbldenv">Steps for doing a Windows build</a>.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-8" class="faqTitle">8. Building on UNIX</h3>
-<div class="faqQuestion">What do I need to rebuild Xalan-C++ on UNIX?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>To build Xalan-C++ on supported UNIX platforms, you need Xerces-C++, the GNU make utility, and a supported C++ compiler. For more
- details see: <a href="buildlibs.html#unixbldenv">Steps for doing a UNIX build</a>.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-9" class="faqTitle">9. Make errors on UNIX platforms</h3>
-<div class="faqQuestion">I get errors in the Makefile when running the make utility. What's wrong?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>You must use the GNU make utility. Other make utilities may not work with the Xalan Makefile</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-10" class="faqTitle">10. What is ICU</h3>
-<div class="faqQuestion">What is ICU and why do I need it?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>The <a href="http://www.ibm.com/software/globalization/icu/">IBM-ICU</a>
- International Components for Unicode(ICU) is a C and C++ library that provides robust and
- full-featured Unicode support on a wide variety of platforms.
- Xalan-C++ uses the ICU to extend support for encoding, number formatting, and sorting.</p>
- <p>The ICU is available for download from <a href="http://oss.software.ibm.com/icu/index.html">
- http://oss.software.ibm.com/icu/index.html</a>.</p>
- <p>Xalan release 1.10 was tested with International Components for Unicode(ICU) version 3.2. The curent Xalan
- release 1.11 is not fully tested with IBM-ICU.</p>
- <p>For more details see: <a href="usagepatterns.html#icu">Using the International Components for Unicode (ICU)</a>.</p>
-
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-11" class="faqTitle">11. A tar checksum error on Solaris</h3>
-<div class="faqQuestion">I am getting a tar checksum error on Solaris. What's the problem?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>The Solaris tar utility you are using does not properly handle files with long pathnames. You must use GNU tar (gtar), which
- handles arbitrarily long pathnames and is freely available on every platform on which Xalan-C++ is supported. If you don't already
- have GNU tar installed on your system, you can obtain it from the Free Software Foundation
- <a href="http://www.gnu.org/software/tar/tar.html">http://www.gnu.org/software/tar/tar.html</a>. For additional background
- information on this problem, see the online manual<a href="http://www.gnu.org/manual/tar/html_chapter/tar_8.html#SEC112">
- GNU tar and POSIX tar </a> for the utility.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-12" class="faqTitle">12. Xalan-C++ in Apache</h3>
-<div class="faqQuestion">Is it possible to run Xalan-C++ from an Apache server?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>A simple Apache module called <a href="samples.html#apachemodulexslt">ApacheModuleXSLT</a> is provided as a sample.
- It demonstrates how to integrate Xalan-C++ with Apache.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-13" class="faqTitle">13. Is Xalan-C++ thread-safe?</h3>
-<div class="faqQuestion">Is Xalan-C++ thread-safe?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>Instances of XalanTransformer are not thread-safe; each thread should use its own instance.</p>
- <p>In order to support very efficient use in multi-threaded applications, Xalan-C++ is designed to avoid synchronization as much as
- possible. Each thread of execution is required to have its own set of "support" objects that contain the state of the
- transformation. Accordingly, no synchronization is required when multiple threads are executing.</p>
- <p>Parsed ("compiled") stylesheets (see <a href="usagepatterns.html#compiled">Compiling stylesheets</a>) and parsed
- source documents may be freely shared by multiple threads of execution without worrying about providing synchronized access to
- them. The <b>only</b> exception to this rule: You use XercesParserLiaison to parse a document after calling
- XercesParserLiaison::setBuildBridgeNodes(false) or XercesParserLiaison::setThreadSafe(false). In this case, the document
- <b>cannot</b> be shared by multiple threads of execution. For reasons of performance, we do not recommend the use of
- XercesParserLiaison, so this should not be an issue for most applications.</p>
- <p>All other objects in Xalan-C++ are <b>not</b> thread-safe. Each thread must have its own instance of each object.</p>
- <p>See the <a href="samples.html#threadsafe">ThreadSafe</a> sample program for more information.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-14" class="faqTitle">14. What can I do to speed up transformations?</h3>
-<div class="faqQuestion">What can I do to speed up transformations?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>To maximize performance, here are some suggestions for you to keep in mind as you set up your applications:</p>
- <ul>
- <li>Use a compiled stylesheet when you expect to use the stylesheet more than once.<br />
-<br />
-</li>
- <li>Set up your stylesheets to function efficiently.<br />
-<br />
-</li>
- <ul>
- <li>Don't use "//" (descendant axes) patterns near the root of a large document.<br />
-<br />
-</li>
- <li>Use xsl:key elements and the key() function as an efficient way to retrieve node sets.<br />
-<br />
-</li>
- <li>Where possible, use pattern matching rather than xsl:if or xsl:when statements.<br />
-<br />
-</li>
- <li>xsl:for-each is fast because it does not require pattern matching.<br />
-<br />
-</li>
- <li>Keep in mind that xsl:sort prevents incremental processing.<br />
-<br />
-</li>
- <li>When you create variables, <xsl:variable name="fooElem" select="foo"/> is usually faster than
- <xsl:variable name="fooElem"><xsl:value-of-select="foo"/></xsl:variable>.<br />
-<br />
-</li>
- <li>Be careful using the last() function.<br />
-<br />
-</li>
- <li>The use of index predicates within match patterns can be expensive.<br />
-<br />
-</li>
- </ul>
- </ul>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-15" class="faqTitle">15. Stylesheet validation</h3>
-<div class="faqQuestion">Can I validate an XSL stylesheet?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>An XSL stylesheet is an XML document, so it can have a DOCTYPE and be subject to validation, but you probably will have
- to write a custom DTD for the purpose.</p>
- <p>The XSLT Recommendation includes a <a href="http://www.w3.org/TR/xslt#dtd">DTD Fragment
- for XSL Stylesheets</a> with some indications of what you need to do to create a complete DTD for a given
- stylesheet. Keep in mind that stylesheets can include literal result elements and produce output that is not valid
- XML.</p>
- <p>You can use the xsl:stylesheet doctype defined in xsl-html40s.dtd for stylesheets that generate HTML.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-16" class="faqTitle">16. What does the XalanDOMException HIERARCHY_REQUEST_ERR mean?</h3>
-<div class="faqQuestion">What does the XalanDOMException HIERARCHY_REQUEST_ERR mean?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>It means that an attempt was made to add a node to a DOM that would create an invalid structure. For example, text nodes
- are not allowed as children of the document node.</p>
- <p>This is a common error when attempting to transform to DOM. Source documents and stylesheets that might produce valid serialized XML
- might not produce value DOM. The usual suspect is text nodes being generated before the document element is generated.</p>
- <p>If you think you have seen this error because of a bug in Xalan-C++'s source tree implementation, please post a bug report on Bugzilla, and attach a minimal source document
- and stylesheet that produce the problem to the bug report.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-17" class="faqTitle">17. Submitting Patches</h3>
-<div class="faqQuestion">Who do I submit patches to?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>Your contributions are much appreciated! You can e-mail your patches to
- <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a> or raise an issue on the
- <a href="https://issues.apache.org/jira/browse/XALANC">Jira issue tracking system</a>.</p>
- <p>The Xalan projects use Jira as the issue tracking system. Any significant bug or feature request is
- posted to this system. You must subscribe to the system in order to submit patches and raise
- issues.</p>
-<ul>
-<li>Subscribe to Jira at:
- <a href="https://issues.apache.org/jira">https://issues.apache.org/jira</a>
-</li>
-<li>Browse the issues at:
- <a href="https://issues.apache.org/jira/browse/XALANC">https://issues.apache.org/jira/browse/XALANC</a>
-</li>
-</ul>
- <p>Issues posted to the project on Jira at XALANC are automatically posted to the
- <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a>
-</p>
- <p>Our mailing lists are moderated. You should subscribe to the mailing list in order to
- post a message, otherwise message delivery requires manual intervention or may be dropped.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-18" class="faqTitle">18. Transformation Output Methods</h3>
-<div class="faqQuestion">How do I output a transformation to a DOM, a file, an in-memory buffer, or as input to another transformation? Since the C++
- language can automatically construct an XSLTResultTarget from any of its constructor's argument types, you usually don't need
- to create one explicitly.</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>The output parameter of XalanTransformer::transform() is an XSLTResultTarget which has many constructors.</p>
- <p>Output to a file:</p>
- <ul>
- <li>The easiest way is to use a null-terminated string containing the file name to create an XSLTResultTarget. Or, use an
- instance of std::ofstream. The command line executables, and many of the sample applications use file names, so take a
- look through the source code for more information.</li>
- </ul>
- <p>Output to an in-memory buffer:</p>
- <ul>
- <li>Use an instance of std::ostrstream or std::ostringstream to create an XSLTResultTarget. See the StreamTransform sample
- for more information.</li>
- </ul>
- <p>Input to another transformation:</p>
- <ul>
- <li>Any of the previous output targets could be used as the input to another transformation, but the FormatterToSourceTree
- is probably the best for efficiency reasons. See the source code for the TestXSLT command line program for more
- information.</li>
- </ul>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-19" class="faqTitle">19. Problems Using Sun's Forte/Workshop Compiler with code containing std::istrstream</h3>
-<div class="faqQuestion">Why won't XSLTInputSource work with std::istrstream on Sun Solaris using Forte/Sun Workshop compiler?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<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>
-</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>The issue is resolved if you use the SunStudio platform for your code development.
- The Solaris SunStudio is now available from Oracle.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-20" class="faqTitle">20. Modifying an instance of XalanDocument</h3>
-<div class="faqQuestion">My transformation outputs to a XalanDocument (actually XalanSourceTreeDocument underneath) but W3C DOM functions like
- DOMElement::setAttribute don't work! Am I going crazy or what?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>No, you aren't going crazy. Xalan's default source tree is read-only for efficiency. If you need a DOM that supports
- modifications, use the Xerces DOM instead. See the TransformToXercesDOM sample for more information.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-21" class="faqTitle">21. Changing Where Error Output is Sent</h3>
-<div class="faqQuestion">XalanTransformer outputs errors to the console. How do I, for example, output error to a file?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>By default, XalanTransformer creates a XalanTransformerProblemListener (a subclass of ProblemListener) that writes
- output to std::cerr. To change this you can:</p>
- <ul>
- <li>Redirect std::cerr from the command line.</li>
- <li>Call XalanTranformer::setWarningStream with a different std::ostream before calling XalanTransformer::transform.</li>
- <li>Instantiate your own XalanTransformerProblemListener with a different output stream and call
- XalanTransformer::setProblemListener() before calling XalanTransformer::transform().</li>
- <li>Subclass some ProblemListener type and do custom handling of errors (you still then need to tell XalanTransformer
- instances to use your ProblemListener.)</li>
- </ul>
- <p>In most case you probably want to do one of the first two.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-22" class="faqTitle">22. Programmatic Error Information</h3>
-<div class="faqQuestion">How do I programmatically get the file name, line number, and column number for an error in an XML file?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>Create a custom ErrorHandler (a Xerces-C++ class) and call XalanTransformer::setErrorHandler before parsing any sources.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-23" class="faqTitle">23. String Transcoding</h3>
-<div class="faqQuestion">How do I make a char* out of XalanDOMString (or vice-versa)?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>See the static method XalanDOMString::transcode, or the functions TranscodeToLocalCodePage in the API documentation.
- However, you should be very careful when transcoding Unicode characters to the local code page, because not all Unicode
- characters can be represented.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-24" class="faqTitle">24. Error Code/Exception Summary</h3>
-<div class="faqQuestion">Is there a table of error codes somewhere? How about a summary of what methods throw which exceptions?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>There isn't, but we're working on it.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-25" class="faqTitle">25. Extension Functions</h3>
-<div class="faqQuestion">The Xalan extension functions (xalan:node-set, etc.) don't work for me. Help!</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>Did you declare the namespace on the xsl:stylesheet or xsl:transform element? It should look like this: </p>
- <p><xsl:stylesheet version="1.0" xmlns:xalan="http://xml.apache.org/xalan"> ...rest of stylesheet</p>
- <p>If you did and you still have problems, you might want to ask the mailing list.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-26" class="faqTitle">26. Outputting results to a file on Windows 95/98</h3>
-<div class="faqQuestion">Why can't I ouput my results to a file on Windows 95/98?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>Well, you can, but it doesn't always work. Neither Windows 95 or 98 are supported or tested. There have been reports of
- problems on it, especially regarding Unicode support. See
- <a href="http://marc.info/?l=xalan-dev&m=99840914524755&w=2">this post</a>.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-27" class="faqTitle">27. Using format-number and ICU</h3>
-<div class="faqQuestion">Why does Xalan emit a warning when using the XSLT function format-number()?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>Did you build with ICU support? See <a href="usagepatterns.html#icu">Using the International Components for
- Unicode (ICU)</a>.</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-28" class="faqTitle">28. Perl wrapper for Xalan-C++?</h3>
-<div class="faqQuestion">Is there a Perl wrapper for Xalan-C++?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>There is no Apache Perl wrapper, however Edwin Pratomo has written a wrapper for Xalan-C++ version 1.4 that can be found
- on CPAN</p>
-</div>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3 id="faq-29" class="faqTitle">29. Missing LocalMsgIndex.hpp file</h3>
-<div class="faqQuestion">Why can't I find the LocalMsgIndex.hpp file?</div>
-<br />
-<hr />
-<div class="faqAnswer">
-<p>The LocalMsgIndex.hpp file is not shipped with the distributions because this file is generated during compile time. This
- file is created at the start of the build process and customized for the locale and message set you are using.</p>
- <p>On Windows, the LocalMsgIndex.hpp header is generated by the Localization project. By building any project that has a
- dependency on the Localization project, will trigger the Message Localization component to built and the LocalMsgIndex.hpp
- to be generated.</p>
- <p>On Windows binary distributions, the LocalMsgIndex.hpp file is a member of the "<code>Include</code>" directory.</p>
- <p>On Unix binary distributions, the LocalMsgIndex.hpp file is a member of the "<code>include/xalanc/PlatformSupport</code>" directory.</p>
-</div>
-<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 2012-10-07</div>
-</div>
-</body>
-</html>
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Frequently asked questions</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * 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.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan-C/C++ Version 1.11</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Frequently asked questions</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="../index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-C++ 1.11</a>
+</li>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="license.html">Licenses</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>
+<a href="charter.html">Charter</a>
+</li></ul><hr /><ul>
+<li>
+<a href="download.html">Download</a>
+</li>
+<li>
+<a href="buildlibs.html">Build Libraries</a>
+</li>
+<li>
+<a href="install.html">Installation</a>
+</li>
+<li>
+<a href="builddocs.html">Build Documents</a>
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>
+<a href="commandline.html">Command Line</a>
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="programming.html">Programming</a>
+</li>
+<li>
+<a href="extensions.html">Extensions</a>
+</li>
+<li>
+<a href="extensionslib.html">Extensions Library</a>
+</li>
+<li>
+<a href="apiDocs/index.html">API Reference</a>
+</li></ul><hr /><ul>
+<li>Xalan-C FAQs<br />
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html#bugs">Bugs</a>
+</li>
+<li>
+<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
+</li>
+<li>
+<a href="secureweb.html">Web Security</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<h2 class="faqSubHead">Questions</h2>
+<ol start="1">
+<li>
+<a href="#faq-1">Where do I go to learn about XSLT</a>
+</li>
+<li>
+<a href="#faq-2">Asking questions about Xalan-C++</a>
+</li>
+<li>
+<a href="#faq-3">What is Xerces-C++?</a>
+</li>
+<li>
+<a href="#faq-4">Which version of Xerces should I be using?</a>
+</li>
+<li>
+<a href="#faq-5">Should I be using the Xerces DOM or Xalan DOM?</a>
+</li>
+<li>
+<a href="#faq-6">Problems with samples in Windows</a>
+</li>
+<li>
+<a href="#faq-7">Building on Windows</a>
+</li>
+<li>
+<a href="#faq-8">Building on UNIX</a>
+</li>
+<li>
+<a href="#faq-9">Make errors on UNIX platforms</a>
+</li>
+<li>
+<a href="#faq-10">What is ICU</a>
+</li>
+<li>
+<a href="#faq-11">A tar checksum error on Solaris</a>
+</li>
+<li>
+<a href="#faq-12">Xalan-C++ in Apache</a>
+</li>
+<li>
+<a href="#faq-13">Is Xalan-C++ thread-safe?</a>
+</li>
+<li>
+<a href="#faq-14">What can I do to speed up transformations?</a>
+</li>
+<li>
+<a href="#faq-15">Stylesheet validation</a>
+</li>
+<li>
+<a href="#faq-16">What does the XalanDOMException HIERARCHY_REQUEST_ERR mean?</a>
+</li>
+<li>
+<a href="#faq-17">Submitting Patches</a>
+</li>
+<li>
+<a href="#faq-18">Transformation Output Methods</a>
+</li>
+<li>
+<a href="#faq-19">Problems Using Sun's Forte/Workshop Compiler with code containing std::istrstream</a>
+</li>
+<li>
+<a href="#faq-20">Modifying an instance of XalanDocument</a>
+</li>
+<li>
+<a href="#faq-21">Changing Where Error Output is Sent</a>
+</li>
+<li>
+<a href="#faq-22">Programmatic Error Information</a>
+</li>
+<li>
+<a href="#faq-23">String Transcoding</a>
+</li>
+<li>
+<a href="#faq-24">Error Code/Exception Summary</a>
+</li>
+<li>
+<a href="#faq-25">Extension Functions</a>
+</li>
+<li>
+<a href="#faq-26">Outputting results to a file on Windows 95/98</a>
+</li>
+<li>
+<a href="#faq-27">Using format-number and ICU</a>
+</li>
+<li>
+<a href="#faq-28">Perl wrapper for Xalan-C++?</a>
+</li>
+<li>
+<a href="#faq-29">Missing LocalMsgIndex.hpp file</a>
+</li>
+</ol>
+<h2 class="faqSubHead">Answers</h2>
+<h3 id="faq-1" class="faqTitle">1. Where do I go to learn about XSLT</h3>
+<div class="faqQuestion">Where do I go to learn about XSLT?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>The definitive sources are the W3C XSLT and XPath recommendations: <a href="http://www.w3.org/TR/xslt">W3C Recommendation 16 November 1999 XSL Transformations (XSLT) Version 1.0</a> and
+ <a href="http://www.w3.org/TR/xpath">XML Path Language (XPath) Version 1.0</a>.</p>
+ <p>For a brief listing of tutorials, discussion forums, and other materials, see <a href="overview.html#uptospeed">Getting up to speed with XSLT</a>.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-2" class="faqTitle">2. Asking questions about Xalan-C++</h3>
+<div class="faqQuestion">Where can I ask a question?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>For specific questions on Xalan-C++, see list archives:
+ <a href="http://marc.info/?l=xalan-c-users">xalan-c-users</a>
+ and <a href="http://marc.info/?l=xalan-dev">xalan-dev</a>.
+ You must subscribe to these Apache mailing lists before posting your questions.</p>
+<p>The Apache Software Foundation has information on how you can subscribe to
+ the <a href="http://www.apache.org/foundation/mailinglists.html">mailing lists</a>.</p>
+<p>You can post messages to the lists by sending mail to:<br />
+ <a href="mailto:c-users@xalan.apache.org">Post message to xalan-c-users</a>. (User's list)<br />
+ <a href="mailto:dev@xalan.apache.org">Post message to xalan-dev list</a>. (Developer's list)</p>
+<p>Again, please review the archives before posting a new question.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-3" class="faqTitle">3. What is Xerces-C++?</h3>
+<div class="faqQuestion">What is Xerces-C++ and why do I need it?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>Xerces-C++ is a validating XML parser written in a portable subset of C++. Xerces-C++ makes it easy to give your application the ability
+ to read and write XML data. Like Xalan-C++, Xerces-C++ is available from the Apache XML site:
+ <a href="http://xerces.apache.org/index.html">http://xerces.apache.org</a>
+</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-4" class="faqTitle">4. Which version of Xerces should I be using?</h3>
+<div class="faqQuestion">Which version of Xerces should I be using?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>The Xalan-C++ release notes includes information about the Xerces-C++ release with which the Xalan-C++ release has been coordinated
+ and tested. See <a href="whatsnew.html#status">Status</a>
+</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-5" class="faqTitle">5. Should I be using the Xerces DOM or Xalan DOM?</h3>
+<div class="faqQuestion">Should I be using the Xerces DOM or Xalan DOM?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>The Xalan DOM implementation is highly optimised for transformations. However, whilst you can build documents in the Xalan DOM,
+ subsequent modification will not work. The Xalan DOM is designed to be either an input or an output from a transformation, not
+ as a general DOM implementation.</p>
+ <p>So in cases where you want to simply transform documents using Xalan, using the internal DOM implementation is the best approach.</p>
+ <p>In cases where you want to modify the DOM document on the fly, you should use the Xerces DOM as the base document. You can wrap
+ the Xerces DOM in a wrapper (see <a href="usagepatterns.html#xercesdomwrapperparsedsource"> passing in a Xerces DOM</a>)
+ to then use as an input to a Xalan transformation. Alternatively you can output the result of a transformation to a Xerces DOM
+ document (see <a href="usagepatterns.html#dom">working with DOM input and output</a>). In either case, the Xerces document
+ can be freely modified. However, after you modify the document, you need to re-build the wrapper so that any changes are replicated
+ in the Xalan wrappers.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-6" class="faqTitle">6. Problems with samples in Windows</h3>
+<div class="faqQuestion">I have encountered problem executing the Xalan-C++ sample applications after rebuilding them under Win32 Environment (Windows NT 4.0, SP3).
+ When I tried to execute the sample, I receive the error message
+ "Debug Assertion Failed! ... Expression: _BLOCK_TYPE_IS_VALID(pHead->nBlockUse)".</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>You may be mixing debug and release versions of executables and libraries. In other words, if you are compiling the sample for debug,
+ then you should link with the debug version of the Xalan-C++ and Xerces-C++ libraries and run with the debug version of the dynamic link
+ libraries.</p>
+ <p>You must also make sure your application is linking with the Debug multithreaded DLL run-time library or the Multithreaded DLL
+ run-time library. To check this setting do the following in Visual C++:</p>
+ <ol>
+ <li>Select Settings from the Project menu.<br />
+<br />
+</li>
+ <li>Click the C/C++ tab.<br />
+<br />
+</li>
+ <li>In the Category drop-down list, select Code Generation.<br />
+<br />
+</li>
+ <li>In the Use run-time library drop-down list, select Multithreaded DLL for the Win32 Release configuration, or select Debug
+ Multithreaded DLL for the Win32 Debug configuration.</li>
+ </ol>
+ <p>Once you have changed this setting, you must rebuild your project.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-7" class="faqTitle">7. Building on Windows</h3>
+<div class="faqQuestion">What do I need to rebuild Xalan-C++ on Windows?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>In order to build Xalan-C++ on Windows, you will need the following:</p>
+<ul>
+<li>The Xalan-C/C++ source distribution package.</li>
+<li>The Xerces-C/C++ source distribution package or a compatible binary distribution package.</li>
+<li>A compatible Microsoft Visual Studio .NET (2003, 2005, 2008, 2010) software development platform.</li>
+</ul>
+<p>The Xalan-C/C++ Version 1.11 (pre-release) is available from the Apache Subversion
+ repository at <b>http://svn.apache.org/repos/asf/xalan/c/trunk/.</b>
+</p>
+<p>After Xalan-C/C++ Version 1.11 is released, it can be downloaded from:
+ <a href="http://www.apache.org/dyn/closer.cgi/xalan/xalan-c">Xalan Distributions</a>.</p>
+<p>The Xerces-C/C++ Version 3.1.1 is can be downloaded from:
+ <a href="http://www.apache.org/dyn/closer.cgi/xerces/c/3">Xerces Distributions</a>.</p>
+<p>If you are building with the
+ <a href="http://www.ibm.com/software/globalization/icu/">IBM-ICU</a>
+ International Components for Unicode library, you will
+ need to rebuild both the Xerces and Xalan libraries.</p>
+<p>For more details, see <a href="buildlibs.html#winbldenv">Steps for doing a Windows build</a>.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-8" class="faqTitle">8. Building on UNIX</h3>
+<div class="faqQuestion">What do I need to rebuild Xalan-C++ on UNIX?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>To build Xalan-C++ on supported UNIX platforms, you need Xerces-C++, the GNU make utility, and a supported C++ compiler. For more
+ details see: <a href="buildlibs.html#unixbldenv">Steps for doing a UNIX build</a>.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-9" class="faqTitle">9. Make errors on UNIX platforms</h3>
+<div class="faqQuestion">I get errors in the Makefile when running the make utility. What's wrong?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>You must use the GNU make utility. Other make utilities may not work with the Xalan Makefile</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-10" class="faqTitle">10. What is ICU</h3>
+<div class="faqQuestion">What is ICU and why do I need it?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>The <a href="http://www.ibm.com/software/globalization/icu/">IBM-ICU</a>
+ International Components for Unicode(ICU) is a C and C++ library that provides robust and
+ full-featured Unicode support on a wide variety of platforms.
+ Xalan-C++ uses the ICU to extend support for encoding, number formatting, and sorting.</p>
+ <p>The ICU is available for download from <a href="http://oss.software.ibm.com/icu/index.html">
+ http://oss.software.ibm.com/icu/index.html</a>.</p>
+ <p>Xalan release 1.10 was tested with International Components for Unicode(ICU) version 3.2. The curent Xalan
+ release 1.11 is not fully tested with IBM-ICU.</p>
+ <p>For more details see: <a href="usagepatterns.html#icu">Using the International Components for Unicode (ICU)</a>.</p>
+
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-11" class="faqTitle">11. A tar checksum error on Solaris</h3>
+<div class="faqQuestion">I am getting a tar checksum error on Solaris. What's the problem?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>The Solaris tar utility you are using does not properly handle files with long pathnames. You must use GNU tar (gtar), which
+ handles arbitrarily long pathnames and is freely available on every platform on which Xalan-C++ is supported. If you don't already
+ have GNU tar installed on your system, you can obtain it from the Free Software Foundation
+ <a href="http://www.gnu.org/software/tar/tar.html">http://www.gnu.org/software/tar/tar.html</a>. For additional background
+ information on this problem, see the online manual<a href="http://www.gnu.org/manual/tar/html_chapter/tar_8.html#SEC112">
+ GNU tar and POSIX tar </a> for the utility.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-12" class="faqTitle">12. Xalan-C++ in Apache</h3>
+<div class="faqQuestion">Is it possible to run Xalan-C++ from an Apache server?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>A simple Apache module called <a href="samples.html#apachemodulexslt">ApacheModuleXSLT</a> is provided as a sample.
+ It demonstrates how to integrate Xalan-C++ with Apache.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-13" class="faqTitle">13. Is Xalan-C++ thread-safe?</h3>
+<div class="faqQuestion">Is Xalan-C++ thread-safe?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>Instances of XalanTransformer are not thread-safe; each thread should use its own instance.</p>
+ <p>In order to support very efficient use in multi-threaded applications, Xalan-C++ is designed to avoid synchronization as much as
+ possible. Each thread of execution is required to have its own set of "support" objects that contain the state of the
+ transformation. Accordingly, no synchronization is required when multiple threads are executing.</p>
+ <p>Parsed ("compiled") stylesheets (see <a href="usagepatterns.html#compiled">Compiling stylesheets</a>) and parsed
+ source documents may be freely shared by multiple threads of execution without worrying about providing synchronized access to
+ them. The <b>only</b> exception to this rule: You use XercesParserLiaison to parse a document after calling
+ XercesParserLiaison::setBuildBridgeNodes(false) or XercesParserLiaison::setThreadSafe(false). In this case, the document
+ <b>cannot</b> be shared by multiple threads of execution. For reasons of performance, we do not recommend the use of
+ XercesParserLiaison, so this should not be an issue for most applications.</p>
+ <p>All other objects in Xalan-C++ are <b>not</b> thread-safe. Each thread must have its own instance of each object.</p>
+ <p>See the <a href="samples.html#threadsafe">ThreadSafe</a> sample program for more information.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-14" class="faqTitle">14. What can I do to speed up transformations?</h3>
+<div class="faqQuestion">What can I do to speed up transformations?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>To maximize performance, here are some suggestions for you to keep in mind as you set up your applications:</p>
+ <ul>
+ <li>Use a compiled stylesheet when you expect to use the stylesheet more than once.<br />
+<br />
+</li>
+ <li>Set up your stylesheets to function efficiently.<br />
+<br />
+</li>
+ <ul>
+ <li>Don't use "//" (descendant axes) patterns near the root of a large document.<br />
+<br />
+</li>
+ <li>Use xsl:key elements and the key() function as an efficient way to retrieve node sets.<br />
+<br />
+</li>
+ <li>Where possible, use pattern matching rather than xsl:if or xsl:when statements.<br />
+<br />
+</li>
+ <li>xsl:for-each is fast because it does not require pattern matching.<br />
+<br />
+</li>
+ <li>Keep in mind that xsl:sort prevents incremental processing.<br />
+<br />
+</li>
+ <li>When you create variables, <xsl:variable name="fooElem" select="foo"/> is usually faster than
+ <xsl:variable name="fooElem"><xsl:value-of-select="foo"/></xsl:variable>.<br />
+<br />
+</li>
+ <li>Be careful using the last() function.<br />
+<br />
+</li>
+ <li>The use of index predicates within match patterns can be expensive.<br />
+<br />
+</li>
+ </ul>
+ </ul>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-15" class="faqTitle">15. Stylesheet validation</h3>
+<div class="faqQuestion">Can I validate an XSL stylesheet?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>An XSL stylesheet is an XML document, so it can have a DOCTYPE and be subject to validation, but you probably will have
+ to write a custom DTD for the purpose.</p>
+ <p>The XSLT Recommendation includes a <a href="http://www.w3.org/TR/xslt#dtd">DTD Fragment
+ for XSL Stylesheets</a> with some indications of what you need to do to create a complete DTD for a given
+ stylesheet. Keep in mind that stylesheets can include literal result elements and produce output that is not valid
+ XML.</p>
+ <p>You can use the xsl:stylesheet doctype defined in xsl-html40s.dtd for stylesheets that generate HTML.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-16" class="faqTitle">16. What does the XalanDOMException HIERARCHY_REQUEST_ERR mean?</h3>
+<div class="faqQuestion">What does the XalanDOMException HIERARCHY_REQUEST_ERR mean?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>It means that an attempt was made to add a node to a DOM that would create an invalid structure. For example, text nodes
+ are not allowed as children of the document node.</p>
+ <p>This is a common error when attempting to transform to DOM. Source documents and stylesheets that might produce valid serialized XML
+ might not produce value DOM. The usual suspect is text nodes being generated before the document element is generated.</p>
+ <p>If you think you have seen this error because of a bug in Xalan-C++'s source tree implementation, please post a bug report on Bugzilla, and attach a minimal source document
+ and stylesheet that produce the problem to the bug report.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-17" class="faqTitle">17. Submitting Patches</h3>
+<div class="faqQuestion">Who do I submit patches to?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>Your contributions are much appreciated! You can e-mail your patches to
+ <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a> or raise an issue on the
+ <a href="https://issues.apache.org/jira/browse/XALANC">Jira issue tracking system</a>.</p>
+ <p>The Xalan projects use Jira as the issue tracking system. Any significant bug or feature request is
+ posted to this system. You must subscribe to the system in order to submit patches and raise
+ issues.</p>
+<ul>
+<li>Subscribe to Jira at:
+ <a href="https://issues.apache.org/jira">https://issues.apache.org/jira</a>
+</li>
+<li>Browse the issues at:
+ <a href="https://issues.apache.org/jira/browse/XALANC">https://issues.apache.org/jira/browse/XALANC</a>
+</li>
+</ul>
+ <p>Issues posted to the project on Jira at XALANC are automatically posted to the
+ <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a>
+</p>
+ <p>Our mailing lists are moderated. You should subscribe to the mailing list in order to
+ post a message, otherwise message delivery requires manual intervention or may be dropped.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-18" class="faqTitle">18. Transformation Output Methods</h3>
+<div class="faqQuestion">How do I output a transformation to a DOM, a file, an in-memory buffer, or as input to another transformation? Since the C++
+ language can automatically construct an XSLTResultTarget from any of its constructor's argument types, you usually don't need
+ to create one explicitly.</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>The output parameter of XalanTransformer::transform() is an XSLTResultTarget which has many constructors.</p>
+ <p>Output to a file:</p>
+ <ul>
+ <li>The easiest way is to use a null-terminated string containing the file name to create an XSLTResultTarget. Or, use an
+ instance of std::ofstream. The command line executables, and many of the sample applications use file names, so take a
+ look through the source code for more information.</li>
+ </ul>
+ <p>Output to an in-memory buffer:</p>
+ <ul>
+ <li>Use an instance of std::ostrstream or std::ostringstream to create an XSLTResultTarget. See the StreamTransform sample
+ for more information.</li>
+ </ul>
+ <p>Input to another transformation:</p>
+ <ul>
+ <li>Any of the previous output targets could be used as the input to another transformation, but the FormatterToSourceTree
+ is probably the best for efficiency reasons. See the source code for the TestXSLT command line program for more
+ information.</li>
+ </ul>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-19" class="faqTitle">19. Problems Using Sun's Forte/Workshop Compiler with code containing std::istrstream</h3>
+<div class="faqQuestion">Why won't XSLTInputSource work with std::istrstream on Sun Solaris using Forte/Sun Workshop compiler?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<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>
+</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>The issue is resolved if you use the SunStudio platform for your code development.
+ The Solaris SunStudio is now available from Oracle.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-20" class="faqTitle">20. Modifying an instance of XalanDocument</h3>
+<div class="faqQuestion">My transformation outputs to a XalanDocument (actually XalanSourceTreeDocument underneath) but W3C DOM functions like
+ DOMElement::setAttribute don't work! Am I going crazy or what?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>No, you aren't going crazy. Xalan's default source tree is read-only for efficiency. If you need a DOM that supports
+ modifications, use the Xerces DOM instead. See the TransformToXercesDOM sample for more information.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-21" class="faqTitle">21. Changing Where Error Output is Sent</h3>
+<div class="faqQuestion">XalanTransformer outputs errors to the console. How do I, for example, output error to a file?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>By default, XalanTransformer creates a XalanTransformerProblemListener (a subclass of ProblemListener) that writes
+ output to std::cerr. To change this you can:</p>
+ <ul>
+ <li>Redirect std::cerr from the command line.</li>
+ <li>Call XalanTranformer::setWarningStream with a different std::ostream before calling XalanTransformer::transform.</li>
+ <li>Instantiate your own XalanTransformerProblemListener with a different output stream and call
+ XalanTransformer::setProblemListener() before calling XalanTransformer::transform().</li>
+ <li>Subclass some ProblemListener type and do custom handling of errors (you still then need to tell XalanTransformer
+ instances to use your ProblemListener.)</li>
+ </ul>
+ <p>In most case you probably want to do one of the first two.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-22" class="faqTitle">22. Programmatic Error Information</h3>
+<div class="faqQuestion">How do I programmatically get the file name, line number, and column number for an error in an XML file?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>Create a custom ErrorHandler (a Xerces-C++ class) and call XalanTransformer::setErrorHandler before parsing any sources.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-23" class="faqTitle">23. String Transcoding</h3>
+<div class="faqQuestion">How do I make a char* out of XalanDOMString (or vice-versa)?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>See the static method XalanDOMString::transcode, or the functions TranscodeToLocalCodePage in the API documentation.
+ However, you should be very careful when transcoding Unicode characters to the local code page, because not all Unicode
+ characters can be represented.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-24" class="faqTitle">24. Error Code/Exception Summary</h3>
+<div class="faqQuestion">Is there a table of error codes somewhere? How about a summary of what methods throw which exceptions?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>There isn't, but we're working on it.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-25" class="faqTitle">25. Extension Functions</h3>
+<div class="faqQuestion">The Xalan extension functions (xalan:node-set, etc.) don't work for me. Help!</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>Did you declare the namespace on the xsl:stylesheet or xsl:transform element? It should look like this: </p>
+ <p><xsl:stylesheet version="1.0" xmlns:xalan="http://xml.apache.org/xalan"> ...rest of stylesheet</p>
+ <p>If you did and you still have problems, you might want to ask the mailing list.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-26" class="faqTitle">26. Outputting results to a file on Windows 95/98</h3>
+<div class="faqQuestion">Why can't I ouput my results to a file on Windows 95/98?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>Well, you can, but it doesn't always work. Neither Windows 95 or 98 are supported or tested. There have been reports of
+ problems on it, especially regarding Unicode support. See
+ <a href="http://marc.info/?l=xalan-dev&m=99840914524755&w=2">this post</a>.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-27" class="faqTitle">27. Using format-number and ICU</h3>
+<div class="faqQuestion">Why does Xalan emit a warning when using the XSLT function format-number()?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>Did you build with ICU support? See <a href="usagepatterns.html#icu">Using the International Components for
+ Unicode (ICU)</a>.</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-28" class="faqTitle">28. Perl wrapper for Xalan-C++?</h3>
+<div class="faqQuestion">Is there a Perl wrapper for Xalan-C++?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>There is no Apache Perl wrapper, however Edwin Pratomo has written a wrapper for Xalan-C++ version 1.4 that can be found
+ on CPAN</p>
+</div>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3 id="faq-29" class="faqTitle">29. Missing LocalMsgIndex.hpp file</h3>
+<div class="faqQuestion">Why can't I find the LocalMsgIndex.hpp file?</div>
+<br />
+<hr />
+<div class="faqAnswer">
+<p>The LocalMsgIndex.hpp file is not shipped with the distributions because this file is generated during compile time. This
+ file is created at the start of the build process and customized for the locale and message set you are using.</p>
+ <p>On Windows, the LocalMsgIndex.hpp header is generated by the Localization project. By building any project that has a
+ dependency on the Localization project, will trigger the Message Localization component to built and the LocalMsgIndex.hpp
+ to be generated.</p>
+ <p>On Windows binary distributions, the LocalMsgIndex.hpp file is a member of the "<code>Include</code>" directory.</p>
+ <p>On Unix binary distributions, the LocalMsgIndex.hpp file is a member of the "<code>include/xalanc/PlatformSupport</code>" directory.</p>
+</div>
+<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 - Tue 2012-10-09</div>
+</div>
+</body>
+</html>
diff --git a/docs/xalan/xalan-c/getstarted.html b/docs/xalan/xalan-c/getstarted.html
index 7f6e629..c1568ec 100644
--- a/docs/xalan/xalan-c/getstarted.html
+++ b/docs/xalan/xalan-c/getstarted.html
@@ -1,449 +1,449 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html>
-<head>
-<title>ASF: Getting Started with Xalan-C++</title>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
-</head>
-<!--
- * 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.
- -->
-<body>
-<div id="title">
-<table class="HdrTitle">
-<tbody>
-<tr>
-<th rowspan="2">
-<a href="../index.html">
-<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
-</a>
-</th>
-<th text-align="center" width="75%">
-<a href="index.html">Xalan-C/C++ Version 1.11</a>
-</th>
-</tr>
-<tr>
-<td valign="middle">Getting Started with Xalan-C++</td>
-</tr>
-</tbody>
-</table>
-<table class="HdrButtons" align="center" border="1">
-<tbody>
-<tr>
-<td>
-<a href="http://www.apache.org">Apache Foundation</a>
-</td>
-<td>
-<a href="http://xalan.apache.org">Xalan Project</a>
-</td>
-<td>
-<a href="http://xerces.apache.org">Xerces Project</a>
-</td>
-<td>
-<a href="http://www.w3.org/TR">Web Consortium</a>
-</td>
-<td>
-<a href="http://www.oasis-open.org/standards">Oasis Open</a>
-</td>
-</tr>
-</tbody>
-</table>
-</div>
-<div id="navLeft">
-<ul>
-<li>
-<a href="resources.html">Resources</a>
-<br />
-</li>
-<li>
-<a href="../index.html">Home</a>
-</li></ul><hr /><ul>
-<li>
-<a href="index.html">Xalan-C++ 1.11</a>
-</li>
-<li>
-<a href="whatsnew.html">What's New</a>
-</li>
-<li>
-<a href="license.html">Licenses</a>
-</li></ul><hr /><ul>
-<li>
-<a href="overview.html">Overview</a>
-</li>
-<li>
-<a href="charter.html">Charter</a>
-</li></ul><hr /><ul>
-<li>
-<a href="download.html">Download</a>
-</li>
-<li>
-<a href="buildlibs.html">Build Libraries</a>
-</li>
-<li>
-<a href="install.html">Installation</a>
-</li>
-<li>
-<a href="builddocs.html">Build Documents</a>
-</li></ul><hr /><ul>
-<li>
-<a href="samples.html">Sample Apps</a>
-</li>
-<li>
-<a href="commandline.html">Command Line</a>
-</li>
-<li>
-<a href="usagepatterns.html">Usage Patterns</a>
-</li></ul><hr /><ul>
-<li>
-<a href="programming.html">Programming</a>
-</li>
-<li>
-<a href="extensions.html">Extensions</a>
-</li>
-<li>
-<a href="extensionslib.html">Extensions Library</a>
-</li>
-<li>
-<a href="apiDocs/index.html">API Reference</a>
-</li></ul><hr /><ul>
-<li>
-<a href="faq.html">Xalan-C FAQs</a>
-</li></ul><hr /><ul>
-<li>
-<a href="whatsnew.html#bugs">Bugs</a>
-</li>
-<li>
-<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
-</li>
-<li>
-<a href="secureweb.html">Web Security</a>
-</li>
-</ul>
-</div>
-<div id="content">
-<h2>Getting Started with Xalan-C++</h2>
-<ul>
-<li>
-<a href="#download">Downloading what you need</a>
-</li>
-<li>
-<a href="#path">Setting up the path/library path</a>
-</li>
-<li>
-<a href="#samples">Trying out the samples</a>
-</li>
-<li>
-<a href="#commandline">Performing your own transformations from the command line</a>
-</li>
-<li>
-<a href="#apps">Setting up your own XSLT applications</a>
-</li>
-</ul>
-<p>This section is being rewritten.
-<a href="index.html#getstarted">See: new getting started</a>
-</p>
-<a name="download"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Downloading what you need</h3>
-<p>For Xalan-C++ Version 1.11, we are distributing the following:
-<ul>
-<li>AIX 5.1 32-bit and 64-bit xlC_r builds</li>
-<li>HP-UX 11 32-bit and 64-bit aCC builds</li>
-<li>Red Hat Linux 7.2 32-bit and 64-bit Intel C++ builds</li>
-<li>Solaris 2.7 32-bit and 64-bit Forte C++ builds</li>
-<li>SuSE Linux 8.1 for IA-32 gcc 3.2.2 build </li>
-<li>Windows 32-bit and 64-bit Visual C++ builds</li>
-</ul>
-</p>
-
-<p>As with previous releases, the documentation build containing this User's Guide and API documentation
- will be provided in a separate distribution.</p>
-<p>Please contact us at <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a> if you would like to help provide builds for other platforms.</p>
-<p>If you do not already have it, you must also download the Xerces-C++ version 3.1.1 build as indicated below.</p>
-<table class="note">
-<tr>
-<td class="noteImg">
-<img src="resources/note.gif" alt="note" />
-</td>
-<td class="noteTxt">The Xalan distribution files are in <a href="http://www.apache.org/dyn/closer.cgi/xalan/xalan-c">Xalan-C downloads</a>. The Xerces distribution files are in
- <a href="http://www.apache.org/dyn/closer.cgi/xerces/c">Xerces-C downloads</a>. Xalan documentation is provided in a separate package from the binary
- distribution files. For Windows, documentation is packaged with the file name Xalan-C_1_11_0-docs.zip. For UNIX,
- documentation is packaged with the file name of Xalan-C_1_11_0-docs.tar.gz.</td>
-</tr>
-</table>
-<br />
-<table border="1">
- <tr>
- <th class="content" rowspan="1" colspan="1">Xalan distribution files</th>
- <th class="content" rowspan="1" colspan="1">Xerces distribution files</th>
- <th class="content" rowspan="1" colspan="1">Platform</th>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-aix_510-xlc_60_050623.tar.gz</td>
- <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-aix_510-xlc_60_050623.tar.gz</td>
- <td class="content" rowspan="1" colspan="1">AIX 5.1 (32-bit)</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-aix_510_64-xlc_60_050623.tar.gz</td>
- <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-aix_510_64-xlc_60_050623.tar.gz</td>
- <td class="content" rowspan="1" colspan="1">AIX 5.1 (64 bit)</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1" />
- <td class="content" rowspan="1" colspan="1" />
- <td class="content" rowspan="1" colspan="1">HP-UX 11.0 (32 bit)</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1" />
- <td class="content" rowspan="1" colspan="1" />
- <td class="content" rowspan="1" colspan="1">HP-UX 11.0 (64 bit)</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-redhat_72-icc_71.tar.gz</td>
- <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-redhat_72-icc_71.tar.gz</td>
- <td class="content" rowspan="1" colspan="1">Redhat Linux 7.2 (32-bit)</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-redhat_72_64-ecc_71.tar.gz</td>
- <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-redhat_72_64-ecc_71.tar.gz</td>
- <td class="content" rowspan="1" colspan="1">Redhat Linux 7.2 (64-bit)</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1" />
- <td class="content" rowspan="1" colspan="1" />
- <td class="content" rowspan="1" colspan="1">Solaris 2.7 (32-bit)</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1"> </td>
- <td class="content" rowspan="1" colspan="1" />
- <td class="content" rowspan="1" colspan="1">Solaris 2.7 (64-bit)</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-suse_81-gcc_32.tar.gz</td>
- <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-suse_81-gcc_32.tar.gz</td>
- <td class="content" rowspan="1" colspan="1">SuSE Linux 8.1 (32-bit)</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-windows_2000-msvc_60.zip<br />
-</td>
- <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-windows_nt-msvc_60.zip<br />
-</td>
- <td class="content" rowspan="1" colspan="1">Windows 2000<br />
-</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-windows_2003_64-ecl_71.zip<br />
-</td>
- <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-windows_2003_64-ecc_71.zip<br />
-</td>
- <td class="content" rowspan="1" colspan="1">Windows 2003 Server (64-bit)<br />
-</td>
- </tr>
-</table>
-<p>The compiler version used for each platform is listed in the table below.
- <table border="1">
- <tr>
- <th class="content" rowspan="1" colspan="1">Platform - Operating System</th>
- <th class="content" rowspan="1" colspan="1">Compilers</th>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">AIX 5.1</td>
- <td class="content" rowspan="1" colspan="1">IBM C and C++ for AIX 6.00</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">HP/UX 11.0</td>
- <td class="content" rowspan="1" colspan="1">aCC A.03.52</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Red Hat Linux 7.2</td>
- <td class="content" rowspan="1" colspan="1">Intel C++ Compiler, version 7.1</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Solaris 2.7</td>
- <td class="content" rowspan="1" colspan="1">Sun Workshop 6 update 2</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">SuSE Linux 8.1</td>
- <td class="content" rowspan="1" colspan="1">gcc Compiler, version 3.2.2</td>
- </tr>
- <tr>
- <td class="content" rowspan="1" colspan="1">Windows NT, 2000, and XP</td>
- <td class="content" rowspan="1" colspan="1">Microsoft Visual C++ with SP5 (for 32-bit)<br />
- Intel C++ Compiler, version 7.1 (for 64-bit)</td>
- </tr>
- </table>
-</p>
-<table class="note">
-<tr>
-<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#gnutar">A tar checksum error on Solaris</a>.</td>
-</tr>
-</table>
-<a name="xalandists"></a>
-
-<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>
-<table class="note">
-<tr>
-<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>
-</tr>
-</table>
-
-
-<a name="path"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Setting up the path/library path</h3>
-<ul>
- <li>
-<a href="#windowspath">For Windows</a>
-</li>
- <li>
-<a href="#unixpath">For UNIX</a>
-</li>
-</ul>
-
-<a name="windowspath"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>For Windows</h4>
-<p>To use the Windows binary distribution, you must place the Xalan executables and the Xalan and Xerces libraries on the path:</p>
-<ul>
- <li>Put Xalan-C_1_11_0-<my_Windows_distribution>\bin and xerces-c-3.1.1-<my_Windows_distribution>\bin on the path.</li>
-</ul>
-<p>The Visual C++ Xalan project included with the Windows release knows the relative paths to the Xalan headers and libraries,
- but it does not know where you have unzipped the Xerces distribution. If you plan to use Visual C++ to build Xalan applications
- or <a href="readme.html#jar">rebuild Xalan</a>, you must also provide Visual C++ with access to the Xerces headers
- and libraries.</p>
-<p>Use the Visual C++ Tools menu to open the Options dialog box, go to the Directories tab, and do the following:</p>
-<ul>
- <li>Add the path to xerces-c-3.1.1-<my_Windows_distribution>\include to the list of directories of Include files.</li>
- <li>Add the path to xerces-c-3.1.1-<my_Windows_distribution>\lib to the list of directories of Library files.</li>
-</ul>
-
-
-<a name="unixpath"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h4>For UNIX</h4>
-<p>To use one of the UNIX binary distributions, you must place the Xalan-C++ executable on the path, and the Xalan-C++ and Xerces-C++
- libraries on the library path.</p>
-<p>For the Xalan-C++ AIX distributions:</p>
-<ul>
- <li>Put Xalan-C_1_11_0-<my_AIX_distribution>/bin on the path (PATH).</li>
- <li>Put Xalan-C_1_11_0-<my_AIX_distribution>/lib and xerces-c-3.1.1-<my_AIX_distribution>/lib
- on the library path (LIBPATH), or copy the shared libraries to /usr/lib.</li>
-</ul>
-<p>For the Xalan-C++ HP-UX 11 distributions:</p>
-<ul>
- <li>Put Xalan-C_1_11_0-<my_HPUX_distribution>/bin on the path (PATH).<br />
-<br />
-</li>
- <li>Put Xalan-C_1_11_0-<my_HPUX_distribution>/lib and xerces-c-3.1.1-<my_HPUX_distribution>/lib on the library path
- SHLIB_PATH), or copy the shared libraries to /usr/lib.</li>
-</ul>
-<p>For the Xalan-C++ Solaris distributions:</p>
-<ul>
- <li>Put Xalan-C_1_11_0-<my_Solaris_distribution>/bin on the path (PATH).<br />
-<br />
-</li>
- <li>Put Xalan-C_1_11_0-<my_Solaris_distribution>/lib and xerces-c-3.1.1-<my_Solaris_distribution>/lib on the library path
- (LD_LIBRARY_PATH), or copy the shared libraries to /usr/lib.</li>
-</ul>
-<p>For the Xalan-C++ RedHat and SuSE Linux distributions:</p>
-<ul>
- <li>Put Xalan-C_1_11_0-<my_Linux_distribution>/bin on the path (PATH).</li>
-<li>Put Xalan-C_1_11_0-<my_Linux_distribution>/lib and xerces-c-3.1.1-<my_Linux_distribution>/lib on the library path (LD_LIBRARY_PATH),
-or copy the shared libraries to /usr/lib.</li>
-</ul>
-
-<a name="samples"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Trying out the samples</h3>
-<p>The Xalan-C++ distribution includes a number of basic sample applications. We have precompiled these samples for you so they are ready to run, and you can review the source files to see just how they work. </p>
-<p>To run the samples, do the following:</p>
-<ol>
-<li>Set up your path (see above). In the Windows32 distribution, the sample executables are in
-Xalan-C_1_11_0-<my_Windows_distribution>\bin. In the UNIX distributions, the executables are in Xalan-C_1_11_0-<my_UNIX_distribution>/bin.</li>
-<li>Go to the samples subdirectory containing the sample.</li>
-<li>Run the sample from the command line (in Windows, use the DOS shell).</li>
-<li>Examine the application source files.</li>
-</ol>
-<p>For example, go to the SimpleTransform subdirectory and issue the following command:</p>
-<p>
-<code>SimpleTransform</code>
-</p>
-<p>SimpleTransform uses the foo.xsl stylesheet to transform foo.xml, and writes the transformation result to foo.out. To see how the example works, examine the source files: foo.xml, foo.xsl, foo.out, and SimpleTransform.cpp.</p>
-<p>For more information about the samples, see <a href="samples.html">Xalan-C++ Samples</a>.</p>
-<a name="commandline"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Performing your own transformations from the command line</h3>
-<p>The Xalan executable lets you perform transformations from the command line. The command line for
-most standard transformations is as follows:</p>
-<p>
-<code>Xalan -o <b>
-<i>outputfile</i>
-</b> <b>
-<i>xmlSource</i>
-</b> <b>
-<i>stylesheet</i>
-</b>
-</code>
-</p>
-<p>where <b>
-<i>xmlSource</i>
-</b> is the XML source file name, <b>
-<i>stylesheet</i>
-</b> is the XSL stylesheet file name, and <b>
-<i>outputfile</i>
-</b> is the output file name.</p>
-<p>If you want the output to be displayed on the screen, simply omit the -o flag and <b>
-<i>outputfile</i>
-</b>.</p>
-<p>You can use this utility to try out XSL stylesheets you have written, to make sure they do what you expect with the XML source files they are designed to transform. The utility provides useful messages if the source file or stylesheet is not well formed. If you include a DOCTYPE statement or Schema hint in your XML source files and include the -v flag on the command line, the utility will also let you know whether the XML document is valid (conforms to that DOCTYPE or Schema). For mor [...]
-<a name="apps"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Setting up your own XSLT applications</h3>
-<p>You can start by using your own XML source files and XSL stylesheets with the sample applications, which illustrate a number of usage patterns. For more information on setting up applications, see <a href="usagepatterns.html">Basic Usage Patterns</a>.</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 2012-10-07</div>
-</div>
-</body>
-</html>
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>ASF: Getting Started with Xalan-C++</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
+</head>
+<!--
+ * 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.
+ -->
+<body>
+<div id="title">
+<table class="HdrTitle">
+<tbody>
+<tr>
+<th rowspan="2">
+<a href="../index.html">
+<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
+</a>
+</th>
+<th text-align="center" width="75%">
+<a href="index.html">Xalan-C/C++ Version 1.11</a>
+</th>
+</tr>
+<tr>
+<td valign="middle">Getting Started with Xalan-C++</td>
+</tr>
+</tbody>
+</table>
+<table class="HdrButtons" align="center" border="1">
+<tbody>
+<tr>
+<td>
+<a href="http://www.apache.org">Apache Foundation</a>
+</td>
+<td>
+<a href="http://xalan.apache.org">Xalan Project</a>
+</td>
+<td>
+<a href="http://xerces.apache.org">Xerces Project</a>
+</td>
+<td>
+<a href="http://www.w3.org/TR">Web Consortium</a>
+</td>
+<td>
+<a href="http://www.oasis-open.org/standards">Oasis Open</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div id="navLeft">
+<ul>
+<li>
+<a href="resources.html">Resources</a>
+<br />
+</li>
+<li>
+<a href="../index.html">Home</a>
+</li></ul><hr /><ul>
+<li>
+<a href="index.html">Xalan-C++ 1.11</a>
+</li>
+<li>
+<a href="whatsnew.html">What's New</a>
+</li>
+<li>
+<a href="license.html">Licenses</a>
+</li></ul><hr /><ul>
+<li>
+<a href="overview.html">Overview</a>
+</li>
+<li>
+<a href="charter.html">Charter</a>
+</li></ul><hr /><ul>
+<li>
+<a href="download.html">Download</a>
+</li>
+<li>
+<a href="buildlibs.html">Build Libraries</a>
+</li>
+<li>
+<a href="install.html">Installation</a>
+</li>
+<li>
+<a href="builddocs.html">Build Documents</a>
+</li></ul><hr /><ul>
+<li>
+<a href="samples.html">Sample Apps</a>
+</li>
+<li>
+<a href="commandline.html">Command Line</a>
+</li>
+<li>
+<a href="usagepatterns.html">Usage Patterns</a>
+</li></ul><hr /><ul>
+<li>
+<a href="programming.html">Programming</a>
+</li>
+<li>
+<a href="extensions.html">Extensions</a>
+</li>
+<li>
+<a href="extensionslib.html">Extensions Library</a>
+</li>
+<li>
+<a href="apiDocs/index.html">API Reference</a>
+</li></ul><hr /><ul>
+<li>
+<a href="faq.html">Xalan-C FAQs</a>
+</li></ul><hr /><ul>
+<li>
+<a href="whatsnew.html#bugs">Bugs</a>
+</li>
+<li>
+<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
+</li>
+<li>
+<a href="secureweb.html">Web Security</a>
+</li>
+</ul>
+</div>
+<div id="content">
+<h2>Getting Started with Xalan-C++</h2>
+<ul>
+<li>
+<a href="#download">Downloading what you need</a>
+</li>
+<li>
+<a href="#path">Setting up the path/library path</a>
+</li>
+<li>
+<a href="#samples">Trying out the samples</a>
+</li>
+<li>
+<a href="#commandline">Performing your own transformations from the command line</a>
+</li>
+<li>
+<a href="#apps">Setting up your own XSLT applications</a>
+</li>
+</ul>
+<p>This section is being rewritten.
+<a href="index.html#getstarted">See: new getting started</a>
+</p>
+<a name="download"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Downloading what you need</h3>
+<p>For Xalan-C++ Version 1.11, we are distributing the following:
+<ul>
+<li>AIX 5.1 32-bit and 64-bit xlC_r builds</li>
+<li>HP-UX 11 32-bit and 64-bit aCC builds</li>
+<li>Red Hat Linux 7.2 32-bit and 64-bit Intel C++ builds</li>
+<li>Solaris 2.7 32-bit and 64-bit Forte C++ builds</li>
+<li>SuSE Linux 8.1 for IA-32 gcc 3.2.2 build </li>
+<li>Windows 32-bit and 64-bit Visual C++ builds</li>
+</ul>
+</p>
+
+<p>As with previous releases, the documentation build containing this User's Guide and API documentation
+ will be provided in a separate distribution.</p>
+<p>Please contact us at <a href="mailto:dev@xalan.apache.org">Xalan Development Mailing List</a> if you would like to help provide builds for other platforms.</p>
+<p>If you do not already have it, you must also download the Xerces-C++ version 3.1.1 build as indicated below.</p>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">The Xalan distribution files are in <a href="http://www.apache.org/dyn/closer.cgi/xalan/xalan-c">Xalan-C downloads</a>. The Xerces distribution files are in
+ <a href="http://www.apache.org/dyn/closer.cgi/xerces/c">Xerces-C downloads</a>. Xalan documentation is provided in a separate package from the binary
+ distribution files. For Windows, documentation is packaged with the file name Xalan-C_1_11_0-docs.zip. For UNIX,
+ documentation is packaged with the file name of Xalan-C_1_11_0-docs.tar.gz.</td>
+</tr>
+</table>
+<br />
+<table border="1">
+ <tr>
+ <th class="content" rowspan="1" colspan="1">Xalan distribution files</th>
+ <th class="content" rowspan="1" colspan="1">Xerces distribution files</th>
+ <th class="content" rowspan="1" colspan="1">Platform</th>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-aix_510-xlc_60_050623.tar.gz</td>
+ <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-aix_510-xlc_60_050623.tar.gz</td>
+ <td class="content" rowspan="1" colspan="1">AIX 5.1 (32-bit)</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-aix_510_64-xlc_60_050623.tar.gz</td>
+ <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-aix_510_64-xlc_60_050623.tar.gz</td>
+ <td class="content" rowspan="1" colspan="1">AIX 5.1 (64 bit)</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1" />
+ <td class="content" rowspan="1" colspan="1" />
+ <td class="content" rowspan="1" colspan="1">HP-UX 11.0 (32 bit)</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1" />
+ <td class="content" rowspan="1" colspan="1" />
+ <td class="content" rowspan="1" colspan="1">HP-UX 11.0 (64 bit)</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-redhat_72-icc_71.tar.gz</td>
+ <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-redhat_72-icc_71.tar.gz</td>
+ <td class="content" rowspan="1" colspan="1">Redhat Linux 7.2 (32-bit)</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-redhat_72_64-ecc_71.tar.gz</td>
+ <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-redhat_72_64-ecc_71.tar.gz</td>
+ <td class="content" rowspan="1" colspan="1">Redhat Linux 7.2 (64-bit)</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1" />
+ <td class="content" rowspan="1" colspan="1" />
+ <td class="content" rowspan="1" colspan="1">Solaris 2.7 (32-bit)</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1"> </td>
+ <td class="content" rowspan="1" colspan="1" />
+ <td class="content" rowspan="1" colspan="1">Solaris 2.7 (64-bit)</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-suse_81-gcc_32.tar.gz</td>
+ <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-suse_81-gcc_32.tar.gz</td>
+ <td class="content" rowspan="1" colspan="1">SuSE Linux 8.1 (32-bit)</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-windows_2000-msvc_60.zip<br />
+</td>
+ <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-windows_nt-msvc_60.zip<br />
+</td>
+ <td class="content" rowspan="1" colspan="1">Windows 2000<br />
+</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Xalan-C_1_11_0-windows_2003_64-ecl_71.zip<br />
+</td>
+ <td class="content" rowspan="1" colspan="1">xerces-c-3.1.1-windows_2003_64-ecc_71.zip<br />
+</td>
+ <td class="content" rowspan="1" colspan="1">Windows 2003 Server (64-bit)<br />
+</td>
+ </tr>
+</table>
+<p>The compiler version used for each platform is listed in the table below.
+ <table border="1">
+ <tr>
+ <th class="content" rowspan="1" colspan="1">Platform - Operating System</th>
+ <th class="content" rowspan="1" colspan="1">Compilers</th>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">AIX 5.1</td>
+ <td class="content" rowspan="1" colspan="1">IBM C and C++ for AIX 6.00</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">HP/UX 11.0</td>
+ <td class="content" rowspan="1" colspan="1">aCC A.03.52</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Red Hat Linux 7.2</td>
+ <td class="content" rowspan="1" colspan="1">Intel C++ Compiler, version 7.1</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Solaris 2.7</td>
+ <td class="content" rowspan="1" colspan="1">Sun Workshop 6 update 2</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">SuSE Linux 8.1</td>
+ <td class="content" rowspan="1" colspan="1">gcc Compiler, version 3.2.2</td>
+ </tr>
+ <tr>
+ <td class="content" rowspan="1" colspan="1">Windows NT, 2000, and XP</td>
+ <td class="content" rowspan="1" colspan="1">Microsoft Visual C++ with SP5 (for 32-bit)<br />
+ Intel C++ Compiler, version 7.1 (for 64-bit)</td>
+ </tr>
+ </table>
+</p>
+<table class="note">
+<tr>
+<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#gnutar">A tar checksum error on Solaris</a>.</td>
+</tr>
+</table>
+<a name="xalandists"></a>
+
+<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>
+<table class="note">
+<tr>
+<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>
+</tr>
+</table>
+
+
+<a name="path"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Setting up the path/library path</h3>
+<ul>
+ <li>
+<a href="#windowspath">For Windows</a>
+</li>
+ <li>
+<a href="#unixpath">For UNIX</a>
+</li>
+</ul>
+
+<a name="windowspath"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>For Windows</h4>
+<p>To use the Windows binary distribution, you must place the Xalan executables and the Xalan and Xerces libraries on the path:</p>
+<ul>
+ <li>Put Xalan-C_1_11_0-<my_Windows_distribution>\bin and xerces-c-3.1.1-<my_Windows_distribution>\bin on the path.</li>
+</ul>
+<p>The Visual C++ Xalan project included with the Windows release knows the relative paths to the Xalan headers and libraries,
+ but it does not know where you have unzipped the Xerces distribution. If you plan to use Visual C++ to build Xalan applications
+ or <a href="readme.html#jar">rebuild Xalan</a>, you must also provide Visual C++ with access to the Xerces headers
+ and libraries.</p>
+<p>Use the Visual C++ Tools menu to open the Options dialog box, go to the Directories tab, and do the following:</p>
+<ul>
+ <li>Add the path to xerces-c-3.1.1-<my_Windows_distribution>\include to the list of directories of Include files.</li>
+ <li>Add the path to xerces-c-3.1.1-<my_Windows_distribution>\lib to the list of directories of Library files.</li>
+</ul>
+
+
+<a name="unixpath"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>For UNIX</h4>
+<p>To use one of the UNIX binary distributions, you must place the Xalan-C++ executable on the path, and the Xalan-C++ and Xerces-C++
+ libraries on the library path.</p>
+<p>For the Xalan-C++ AIX distributions:</p>
+<ul>
+ <li>Put Xalan-C_1_11_0-<my_AIX_distribution>/bin on the path (PATH).</li>
+ <li>Put Xalan-C_1_11_0-<my_AIX_distribution>/lib and xerces-c-3.1.1-<my_AIX_distribution>/lib
+ on the library path (LIBPATH), or copy the shared libraries to /usr/lib.</li>
+</ul>
+<p>For the Xalan-C++ HP-UX 11 distributions:</p>
+<ul>
+ <li>Put Xalan-C_1_11_0-<my_HPUX_distribution>/bin on the path (PATH).<br />
+<br />
+</li>
+ <li>Put Xalan-C_1_11_0-<my_HPUX_distribution>/lib and xerces-c-3.1.1-<my_HPUX_distribution>/lib on the library path
+ SHLIB_PATH), or copy the shared libraries to /usr/lib.</li>
+</ul>
+<p>For the Xalan-C++ Solaris distributions:</p>
+<ul>
+ <li>Put Xalan-C_1_11_0-<my_Solaris_distribution>/bin on the path (PATH).<br />
+<br />
+</li>
+ <li>Put Xalan-C_1_11_0-<my_Solaris_distribution>/lib and xerces-c-3.1.1-<my_Solaris_distribution>/lib on the library path
+ (LD_LIBRARY_PATH), or copy the shared libraries to /usr/lib.</li>
+</ul>
+<p>For the Xalan-C++ RedHat and SuSE Linux distributions:</p>
+<ul>
+ <li>Put Xalan-C_1_11_0-<my_Linux_distribution>/bin on the path (PATH).</li>
+<li>Put Xalan-C_1_11_0-<my_Linux_distribution>/lib and xerces-c-3.1.1-<my_Linux_distribution>/lib on the library path (LD_LIBRARY_PATH),
+or copy the shared libraries to /usr/lib.</li>
+</ul>
+
+<a name="samples"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Trying out the samples</h3>
+<p>The Xalan-C++ distribution includes a number of basic sample applications. We have precompiled these samples for you so they are ready to run, and you can review the source files to see just how they work. </p>
+<p>To run the samples, do the following:</p>
+<ol>
+<li>Set up your path (see above). In the Windows32 distribution, the sample executables are in
+Xalan-C_1_11_0-<my_Windows_distribution>\bin. In the UNIX distributions, the executables are in Xalan-C_1_11_0-<my_UNIX_distribution>/bin.</li>
+<li>Go to the samples subdirectory containing the sample.</li>
+<li>Run the sample from the command line (in Windows, use the DOS shell).</li>
+<li>Examine the application source files.</li>
+</ol>
+<p>For example, go to the SimpleTransform subdirectory and issue the following command:</p>
+<p>
+<code>SimpleTransform</code>
+</p>
+<p>SimpleTransform uses the foo.xsl stylesheet to transform foo.xml, and writes the transformation result to foo.out. To see how the example works, examine the source files: foo.xml, foo.xsl, foo.out, and SimpleTransform.cpp.</p>
+<p>For more information about the samples, see <a href="samples.html">Xalan-C++ Samples</a>.</p>
+<a name="commandline"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Performing your own transformations from the command line</h3>
+<p>The Xalan executable lets you perform transformations from the command line. The command line for
+most standard transformations is as follows:</p>
+<p>
+<code>Xalan -o <b>
+<i>outputfile</i>
+</b> <b>
+<i>xmlSource</i>
+</b> <b>
+<i>stylesheet</i>
+</b>
+</code>
+</p>
+<p>where <b>
+<i>xmlSource</i>
+</b> is the XML source file name, <b>
+<i>stylesheet</i>
+</b> is the XSL stylesheet file name, and <b>
+<i>outputfile</i>
+</b> is the output file name.</p>
+<p>If you want the output to be displayed on the screen, simply omit the -o flag and <b>
+<i>outputfile</i>
+</b>.</p>
+<p>You can use this utility to try out XSL stylesheets you have written, to make sure they do what you expect with the XML source files they are designed to transform. The utility provides useful messages if the source file or stylesheet is not well formed. If you include a DOCTYPE statement or Schema hint in your XML source files and include the -v flag on the command line, the utility will also let you know whether the XML document is valid (conforms to that DOCTYPE or Schema). For mor [...]
+<a name="apps"></a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Setting up your own XSLT applications</h3>
+<p>You can start by using your own XML source files and XSL stylesheets with the sample applications, which illustrate a number of usage patterns. For more information on setting up applications, see <a href="usagepatterns.html">Basic Usage Patterns</a>.</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 - Tue 2012-10-09</div>
+</div>
+</body>
+</html>
diff --git a/docs/xalan/xalan-c/index.html b/docs/xalan/xalan-c/index.html
index 852065a..6b7b708 100644
--- a/docs/xalan/xalan-c/index.html
+++ b/docs/xalan/xalan-c/index.html
@@ -1,537 +1,537 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html>
-<head>
-<title>ASF: Xalan-C++ Version 1.11</title>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="stylesheet" type="text/css" href="resources/apache-xalan.css" />
-</head>
-<!--
- * 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.
- -->
-<body>
-<div id="title">
-<table class="HdrTitle">
-<tbody>
-<tr>
-<th rowspan="2">
-<a href="../index.html">
-<img alt="Trademark Logo" src="resources/XalanC-Logo-tm.png" width="190" height="90" />
-</a>
-</th>
-<th text-align="center" width="75%">
-<a href="index.html">Xalan-C/C++ Version 1.11</a>
-</th>
-</tr>
-<tr>
-<td valign="middle">Xalan-C++ Version 1.11</td>
-</tr>
-</tbody>
-</table>
-<table class="HdrButtons" align="center" border="1">
-<tbody>
-<tr>
-<td>
-<a href="http://www.apache.org">Apache Foundation</a>
-</td>
-<td>
-<a href="http://xalan.apache.org">Xalan Project</a>
-</td>
-<td>
-<a href="http://xerces.apache.org">Xerces Project</a>
-</td>
-<td>
-<a href="http://www.w3.org/TR">Web Consortium</a>
-</td>
-<td>
-<a href="http://www.oasis-open.org/standards">Oasis Open</a>
-</td>
-</tr>
-</tbody>
-</table>
-</div>
-<div id="navLeft">
-<ul>
-<li>
-<a href="resources.html">Resources</a>
-<br />
-</li>
-<li>
-<a href="../index.html">Home</a>
-</li></ul><hr /><ul>
-<li>Xalan-C++ 1.11<br />
-</li>
-<li>
-<a href="whatsnew.html">What's New</a>
-</li>
-<li>
-<a href="license.html">Licenses</a>
-</li></ul><hr /><ul>
-<li>
-<a href="overview.html">Overview</a>
-</li>
-<li>
-<a href="charter.html">Charter</a>
-</li></ul><hr /><ul>
-<li>
-<a href="download.html">Download</a>
-</li>
-<li>
-<a href="buildlibs.html">Build Libraries</a>
-</li>
-<li>
-<a href="install.html">Installation</a>
-</li>
-<li>
-<a href="builddocs.html">Build Documents</a>
-</li></ul><hr /><ul>
-<li>
-<a href="samples.html">Sample Apps</a>
-</li>
-<li>
-<a href="commandline.html">Command Line</a>
-</li>
-<li>
-<a href="usagepatterns.html">Usage Patterns</a>
-</li></ul><hr /><ul>
-<li>
-<a href="programming.html">Programming</a>
-</li>
-<li>
-<a href="extensions.html">Extensions</a>
-</li>
-<li>
-<a href="extensionslib.html">Extensions Library</a>
-</li>
-<li>
-<a href="apiDocs/index.html">API Reference</a>
-</li></ul><hr /><ul>
-<li>
-<a href="faq.html">Xalan-C FAQs</a>
-</li></ul><hr /><ul>
-<li>
-<a href="whatsnew.html#bugs">Bugs</a>
-</li>
-<li>
-<a href="http://xalan.apache.org/old/xalan-j/test/run.html#how-to-run-c">Testing</a>
-</li>
-<li>
-<a href="secureweb.html">Web Security</a>
-</li>
-</ul>
-</div>
-<div id="content">
-<h2>Xalan-C++ Version 1.11</h2>
-
-<ul>
-<li>
-<a href="#licenses">Licenses</a>
-</li>
-<li>
-<a href="#getinvolved">Getting Involved</a>
-</li>
-<li>
-<a href="#xsltStandards">XSLT Standards Implemented</a>
-</li>
-<li>
-<a href="#xmlParserLib">XML Parser Library</a>
-</li>
-<li>
-<a href="#securityIssues">Security Issues</a>
-</li>
-<li>
-<a href="#getstarted">Getting Started</a>
-</li>
-<li>
-<a href="#getWhatNeeded">Getting What You Need</a>
-</li>
-</ul>
-<p>The old Xalan-C/C++ 1.10 release can be found at
-<a href="../old/xalan-c/index.html">xml.apache.org/xalan-c</a>.</p>
-
-<a name="whatisxalan"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>What Is Xalan?</h3>
-
-<p>Xalan is an XSLT processor for transforming XML documents
-into HTML, text, or other XML document types.
-It uses for input an XML document and an XSLT stylesheet.
-The engine also supports the entry of top-level stylesheet parameters.
-Documentation exists on how to extend the library with
-your own custom XPath functions.
-</p>
-<p>Xalan-C++ version 1.11 is a robust implementation of the
-W3C Recommendations for
-<a href="http://www.w3.org/TR/xslt">XSL Transformations (XSLT)</a>
-and the
-<a href="http://www.w3.org/TR/xpath">XML Path Language (XPath)</a>.
-It works with the
-<a href="http://xerces.apache.org/xerces-c">Xerces-C++ version 3.1.1</a>
-release of XML parsers.
-The focus for this Xalan release is on bug fixes and
-compatibility with newer development platforms.
-</p>
-<p>The Xalan-C/C++ project creates and distributes a
-standard XSLT library and a simple Xalan command-line
-utility for transforming XML documents.
-</p>
-<p>This project is written in a reduced set of the C++ programming language.
-This makes the library directly usable on numerous platforms.
-A set of 'C' language APIs is also available so that
-XSLT and XPath functionality is easily deployed to 'C' language applications.
-</p>
-<p>
-<a href="samples.html">Sample programs</a> are available
-for you to test and experiment with as you learn the Xalan library.
-</p>
-<p>Some of the <a href="http://www.exslt.org">EXSLT extension functions</a>
-for XPath are available.
-We need to write and validate more of the EXSLT functions.
-Apache also provides some of their own
-<a href="extensionslib.html">XPath extensions</a> for use.
-Documentation and examples are available for you to write
-your own custom <a href="extensions.html">XPath extensions</a>.
-</p>
-<p>There is a library of <a href="extensionslib.html">XPath extensions</a>
-that are provided by the Apache Xalan community.
-</p>
-
-
-<a name="licenses"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Licenses</h3>
-
-<p>The Xalan-C/C++ software conforms to The Apache Software Foundation
-<a href="license.html">License, Version 2.0</a>.
-</p>
-
-
-<a name="getinvolved"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Getting Involved</h3>
-
-<p>You are invited to participate in
-<a href="http://www.apache.org/foundation/getinvolved.html">The Apache Software Foundation</a>.
-You will need to subscribe if you wish to receive mail from the lists.
-Some lists require a subscription in order to post messages.
-</p>
-<p>The <a href="mailto:dev@xalan.apache.org">xalan-dev</a> mailing list
-is used to communicate product development issues with the software development team.
-The xalan-dev messages are
-<a href="http://mail-archives.apache.org/mod_mbox/xalan-dev">archived here</a>
-and on <a href="http://marc.info/?l=xalan-dev">Marc.info</a>.
-</p>
-<p>The <a href="mailto:c-users@xalan.apache.org">xalan-c-users</a> mailing list
-is used to discuss issues regarding the use of the Xalan-C/C++ software and libraries.
-The xalan-c-users messages are
-<a href="http://mail-archives.apache.org/mod_mbox/xalan-c-users">archived here</a>
-and on <a href="http://marc.info/?l=xalan-c-users">Marc.info</a>.
-</p>
-<p>The subversion repository changes are logged on the xalan-commits mailing list and are
-<a href="http://mail-archives.apache.org/mod_mbox/xalan-commits">archived here</a>
-and on <a href="http://marc.info/?l=xalan-cvs">Marc.info</a>.
-</p>
-<p>You can review the project sources and change history in the subversion repository at
-<a href="http://svn.apache.org/viewvc/xalan/c">http://svn.apache.org/viewvc/xalan/c</a>.
-</p>
-<p>You can get a private copy of the subversion snapshot of the development sources at
-<a href="http://svn.apache.org/repos/asf/xalan/c/trunk">http://svn.apache.org/repos/asf/xalan/c/trunk</a>
-using your favorite SVN program.
-</p>
-<p>The JIRA system is used for issue tracking.
-You must create an account before you can post messages and files to the JIRA tracking system.
-You can view the issues at
-<a href="https://issues.apache.org/jira/browse/XALANC">https://issues.apache.org/jira/browse/XALANC</a>.
-</p>
-
-
-<a name="xsltStandards"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>XSLT Standards Implemented</h3>
-
-<p>Xalan-C/C++ implements the following specifications from the World Wide Web Consortium (W3C).
-</p>
-<ul>
-<li>
-<a href="http://www.w3.org/TR/xslt">XSL Transformations (XSLT) Version 1.0</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xpath">XML Path Language (XPath) Version 1.0</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xml-stylesheet">Associating Style Sheets with XML documents 1.0 (Second Edition)</a>
-</li>
-</ul>
-
-<p>The next major release of Xalan-C/C++ will hopefully be compatible with following standards. This added support will require a major version change from 1 to 2.
-</p>
-<ul>
-<li>
-<a href="http://www.w3.org/TR/xslt20">XSL Transformations (XSLT) Version 2.0</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xslt-xquery-serialization">XSLT 2.0 and XQuery 1.0 Serialization</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xpath20">XML Path Language (XPath) Version 2.0 (Second Edition)</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xquery-semantics">XQuery 1.0 and XPath 2.0 Formal Semantics (Second Edition)</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xpath-datamodel">XQuery 1.0 and XPath 2.0 Data Model (XDM) (Second Edition)</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xpath-functions">XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition)</a>
-</li>
-</ul>
-
-
-
-<a name="xmlParserLib"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>XML Parser Library</h3>
-
-<p>Xalan-C/C++ uses the The Apache Software Foundation Xerces-C project that implements parsers for XML 1.0 and XML 1.1.
-The following standards as specified by the
-<a href="http://www.w3.org/TR">World Wide Web Consortium (W3C)</a> are implemented by the
-<a href="http://xerces.apache.org/xerces-c">Xerces-C</a> XML parser library.
-</p>
-<ul>
-<li>
-<a href="http://www.w3.org/TR/xml">Extensible Markup Language (XML) 1.0 (Third Edition) - currently (Fifth Edition)</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xml11">Extensible Markup Language (XML) 1.1 (First Edition) - currently (Second Edition)</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xml-id">xml:id Version 1.0</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xmlbase">XML Base (Second Edition)</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xml-infoset">XML Information Set (Second Edition)</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xml-names">Namespaces in XML 1.0 (Third Edition)</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xml-names11">Namespaces in XML 1.1 (Second Edition)</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xmlschema-1">XML Schema Part 1: Structures Second Edition</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xmlschema-2">XML Schema Part 2: Datatypes Second Edition</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/REC-DOM-Level-1">Document Object Model (DOM) Level 1</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/ElementTraversal">Element Traversal Specification</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/DOM-Level-2-Core">Document Object Model (DOM) Level 2 Core Specification</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/DOM-Level-2-Traversal-Range">Document Object Model (DOM) Level 2 Traversal and Range Specification</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/DOM-Level-3-Core">Document Object Model (DOM) Level 3 Core Specification</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/DOM-Level-3-Val">Document Object Model (DOM) Level 3 Validation Specification</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/DOM-Level-3-LS">Document Object Model (DOM) Level 3 Load and Save Specification</a>
-</li>
-<li>
-<a href="http://www.w3.org/TR/xinclude">XML Inclusions (XInclude) 1.0 (Second Edition)</a>
-</li>
-</ul>
-<p>The Xerces-C/C++ also supports the <a href="http://sax.sourceforge.net/">SAX 1.0 and SAX 2.0</a> projects.
-SAX is primarily Java based. The Xerces-C/C++ project has implemented a SAX C++ API that looks much like the SAX Java API.
-</p>
-<p>Web Services and Web Security recommendations have been developed by the
-<a href="http://www.w3.org">World Wide Web Consortium (W3C)</a> and
-<a href="http://www.oasis-open.org">OASIS-OPEN</a> Advancing open standards for the information society.
-The Xerces-C/C++ has support for custom entity resolvers which are inherited and
-supported by the Xalan-C/C++ library.
-</p>
-
-
-<a name="securityIssues"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Security Issues</h3>
-
-<p>The Xalan-C/C++ library has hooks so that custom entity resolvers can be deployed.
-The entity resolvers are actually interfaces into the Xerces-C/C++ XML Parser Library.
-Use of trusted entity resolvers greatly increases the security of XML based applications.
-</p>
-<p>The Web Services Architecture uses specifications and recommendations
-that are documented by the following organizations.
-</p>
-<ul>
-<li>World Wide Web Consortium (W3C)<br />
- [<a href="http://www.w3.org">http://www.w3.org]</a>]</li>
-<li>Advancing open standards for the information society (OASIS-OPEN)<br />
- [<a href="http://www.oasis-open.org">http://www.oasis-open.org</a>]</li>
-<li>The Sourceforge SAX Project (SAX1, SAX2)<br />
- [<a href="http://sax.sourceforge.net">http://sax.sourceforge.net</a>]</li>
-<li>Internet Engineering Task Force (IETF)<br />
- [<a href="http://www.ietf.org">http://www.ietf.org</a>]</li>
-</ul>
-<p>There are some <a href="secureweb.html">architecture security</a> issues
-that should be addressed by any XML parser or XSLT transformation application.
-Other than validating and cleaning the content of XML elements,
-the access to untrusted external entities is a big problem for security management.
-</p>
-<p>The "Xalan" comman-line transformation program does not deploy
-an OASIS catalog or perform other security measures.
-URLs are resolved using the system directory of the local machine
-and DNS to resolve host locations.
-The "Xalan" program should be used only with
-trusted XSLT stylesheets and XML documents on a trusted computer.
-</p>
-<p>A future release of the "Xalan" command-line transformation program
-may include support for an OASIS entity resolver catalog.
-</p>
-<p>Information on creating Secure Web Service Applications is useful for review.
-This <a href="secureweb.html">security overview document</a> goes beyond the scope of
-XSLT transformations and asks many pertinent security based questions.
-</p>
-
-
-<a name="getstarted"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Getting Started</h3>
-
-<p>The source code and documentation are delivered in separate packages.
-Binary packages comprise the compiled libraries, the Xalan command line utility, and the C/C++ header files.
-The documentation package contains the pre-built documentation.
-The source package contains the sources to build everything.
-</p>
-<p>The current Xalan-C/C++ Version 1.11 is compatible with the stable releases of
-<a href="http://xerces.apache.org/xerces-c">Xerces-C/C++</a> Version 3.0 and newer. The current stable release for Xerces-C/C++ is 3.1.1.
-</p>
-<p>The previous Xalan-C/C++ Version 1.10 works with Xerces-C/C++ Versions 2.7.0 and 2.8.0.
-</p>
-<p>If you are having problems using the product,
-send your comments to the <a href="mailto:c-users@xalan.apache.org">xalan-c-users</a> mail list.
-</p>
-<p>If you think a change needs to be made or have suggestions for future releases,
-send your comments to the <a href="mailto:dev@xalan.apache.org">xalan-dev</a> mail list.
-</p>
-<p>Binary releases are not yet available.
-We would like to distribute Xalan-C/C++ Version 1.11 binary releases
-using the same platforms specified for the compatible Xerces-C binary packages.
-</p>
-
-
-<a name="getWhatNeeded"></a>
-<p align="right" size="2">
-<a href="#content">(top)</a>
-</p>
-<h3>Getting What You Need</h3>
-
-<p>What you need depends whether you plan to
-build from the sources or download prebuilt packages.
-</p>
-<p>The development platform used to build the Xalan-C/C++ (XSLT) library
-should be the same as the platform used to build the Xerces-C/C++ (XML) parser library.
-</p>
-<p>Xalan-C/C++ (XSLT) library requires a working Xerces-C/C++ (XML) parser library.
-The supported versions of Xerces-C/C++ version 3.0 or newer. Version 3.1.1
-is recommended.
-</p>
-<p>If you are ambitious and willing to experiment,
-you can download the bleeding edge development from the
-Apache Software Foundation subversion repositories.
-Use your favorite subversion 'svn' utility for download.
-</p>
-<table border="1">
-<tr>
-<td class="content" rowspan="1" colspan="1">Xalan-C Repository</td>
-<td class="content" rowspan="1" colspan="1">http://svn.apache.org/repos/asf/xalan/c/trunk</td>
-</tr>
-<tr>
-<td class="content" rowspan="1" colspan="1">Xerces-C Repository</td>
-<td class="content" rowspan="1" colspan="1">http://svn.apache.org/repos/asf/xerces/c/trunk</td>
-</tr>
-</table>
-
-<p>The current stable
-<a href="http://xerces.apache.org/xerces-c/download.cgi">Xerces-C/C++ (XML) packages</a>
-are available for download.
... 15092 lines suppressed ...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org