You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by sh...@apache.org on 2012/06/16 05:57:39 UTC
svn commit: r1350856 [8/11] - in /xalan/site: ./ docs/ docs/xalan/
docs/xalan/resources/ docs/xalan/xalan-c/ docs/xalan/xalan-c/resources/
docs/xalan/xalan-j/ stylebook/ stylebook/Xalan-Logos/ stylebook/css/
stylebook/style/ stylebook/style/dtd/ xdocs/...
Added: xalan/site/docs/xalan/xalan-c/usagepatterns.html
URL: http://svn.apache.org/viewvc/xalan/site/docs/xalan/xalan-c/usagepatterns.html?rev=1350856&view=auto
==============================================================================
--- xalan/site/docs/xalan/xalan-c/usagepatterns.html (added)
+++ xalan/site/docs/xalan/xalan-c/usagepatterns.html Sat Jun 16 03:57:36 2012
@@ -0,0 +1,945 @@
+<?xml version="1.0" encoding="ISO-8859-1" 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++ Basic usage patterns</title>
+<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" />
+<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++ Basic usage patterns</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>Usage Patterns<br />
+</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://xml.apache.org/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++ Basic usage patterns</h2>
+<ul>
+ <li>
+<a href="#intro">Introduction</a>
+</li>
+ <li>
+<a href="#xalantransformer">Basic usage pattern with the XalanTransformer C++ API</a>
+</li>
+ <li>
+<a href="#stylepi">Using a stylesheet processing instruction</a>
+</li>
+ <li>
+<a href="#params">Setting stylesheet parameters</a>
+</li>
+ <li>
+<a href="#incremental">Processing output incrementally</a>
+</li>
+ <li>
+<a href="#compiled">Performing a series of transformations</a>
+</li>
+ <li>
+<a href="#dom">Working with DOM input and output</a>
+</li>
+ <li>
+<a href="#xercesdomwrapperparsedsource">Using a Xerces DOM as the source for a Xalan transformation</a>
+</li>
+ <li>
+<a href="#xpath">Working with XPath expressions</a>
+</li>
+ <li>
+<a href="#tracelistener">Using the TraceListener</a>
+</li>
+ <li>
+<a href="#icu">Using the International Components for Unicode (ICU)</a>
+</li>
+ <li>
+<a href="#capi">Basic usage pattern with the XalanTransformer C API</a>
+</li>
+ <li>
+<a href="#cvar">Variations with the XalanTransformer C API</a>
+</li>
+ <li>See also: <a href="extensions.html">Creating and using extension functions</a>
+</li>
+</ul>
+
+<a name="intro">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Introduction</h3>
+<p>To perform a transformation, use one of the <a href="apiDocs/classXalanTransformer.html">XalanTransformer
+ </a> transform() methods. The transformation requires an XML source document and an XSL stylesheet. Both of these objects
+ may be represented by instances of <a href="apiDocs/classXSLTInputSource.html">XSLTInputSource </a>. You can construct
+ an XSLTInputSource with a string (the system ID for a file or URI), an input stream, or a DOM.</p>
+<p>If you are using an XSL stylesheet to perform a series of transformations, you can improve performance by calling transform()
+ with a compiled stylesheet, an instance of <a href="apiDocs/classXalanCompiledStylesheet.html">XalanCompiledStylesheet</a>.
+ If you are transforming an XML source more than once, you should call transform() with a parsed XML source, an instance of
+ <a href="apiDocs/classXalanParsedSource.html">XalanParsedSource</a>. See <a href="#compiled">Performing a series of
+ transformations</a>.</p>
+<p>If you XML source document contains a stylesheet Processing Instruction (PI), you do not need to include a stylesheet object
+ when you call transform().</p>
+<p>The transformation output is represented by an <a href="apiDocs/classXSLTResultTarget.html">XSLTResultTarget</a>, which
+ you can set up to refer to an output stream, the system ID for a file or URI, or a Formatter for one of the various styles of
+ DOM output.</p>
+<p>For detailed API documentation, see <a href="apiDocs/index.html">Xalan-C++ API</a>. For an overview of the command-line
+ utility, see <a href="commandline.html">Command-Line Utility</a>.</p>
+
+
+<a name="xalantransformer">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Basic usage patten with the XalanTransformer C++ API</h3>
+<p>Using <a href="apiDocs/classXalanTransformer.html">XalanTransformer</a> and the C++ API, you can perform one or more
+ transformations as described in the following steps.</p>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">For a working sample that illustrates these steps, see the <a href="samples.html#xalantransform">XalanTransform</a>
+ sample.</td>
+</tr>
+</table>
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>1. Include the required header files.</h4>
+<p>Always start with xalanc/Include/PlatformDefinitions.hpp, the Xalan-C++ base header file. Also include xercesc/util/PlatformUtils.hpp,
+ xalanc/XalanTransformer/XalanTransformer.hpp, and any other header files your particular application requires.</p>
+<blockquote class="source">
+<pre>
+#include <xalanc/Include/PlatformDefinitions.hpp>
+#include <xercesc/util/PlatformUtils.hpp>
+#include <xalanc/XalanTransformer/XalanTransformer.hpp>
+...
+</pre>
+</blockquote>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>2. Define namespaces</h4>
+<p>As of version 1.5, Xalan-C++ now uses C++ namespaces for those platforms which support them. A number of macros are provided to
+ make using the Xalan-C++ (and Xerces-C++) namespaces easier.</p>
+<p>In the following example, the <b>XALAN_USING_XERCES</b> and <b>XALAN_USING_XALAN</b> macros are used to declare that the
+ program is using <b>XMLPlatformUtils</b> and <b>XalanTransformer</b> from the Xerces-C++ and Xalan-C++ namespaces respectively.</p>
+<blockquote class="source">
+<pre>
+XALAN_USING_XERCES(XMLPlatformUtils)
+XALAN_USING_XALAN(XalanTransformer)
+</pre>
+</blockquote>
+
+<p>These macros can be used immediately after the included header files (for global applicability in a given source file) or within
+ functions and methods for local applicability.</p>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">Whilst you can use the standard C++ namespace syntax directly, the Xerces-C++ and Xalan-C++ namespaces are linked to the version
+ number. For example, the Xalan namespace is currently <b>xalanc_1_11</b>. The macros will automatically take care of this
+ when code is re-compiled against a new version of the libraries. Using the namespaces directly will require each namespace
+ related statement be updated by hand.</td>
+</tr>
+</table>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>3. Initialize Xerces and Xalan.</h4>
+<p>Use the static initializers to initialize the Xalan-C++ and Xerces-C++ platforms. You must initialize Xerces-C++ once per process. You
+ may initialize and terminate Xalan-C++ multiple times, but this is not recommended: it is inefficient and is not thread safe.</p>
+<blockquote class="source">
+<pre>
+XMLPlatformUtils::Initialize();
+XalanTransformer::initialize();
+</pre>
+</blockquote>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>4. Create a XalanTransformer.</h4>
+<blockquote class="source">
+<pre>
+XalanTransformer theXalanTransformer;
+</pre>
+</blockquote>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>5. Perform each transformation.</h4>
+<p>You can explicitly instantiate <a href="apiDocs/classXSLTInputSource.html">XSLTInputSource</a> objects for the XML
+ source document and XSL stylesheet, and an <a href="apiDocs/classXSLTResultTarget.html">XSLTResultTarget</a> object
+ for the output, and then call <a href="apiDocs/classXalanTransformer.html">XalanTransformer</a> transform() with those
+ objects as parameters. For example:</p>
+<blockquote class="source">
+<pre>
+XSLTInputSource xmlIn("foo.xml");
+XSLTInputSource xslIn("foo.xsl");
+XSLTResultTarget xmlOut("foo-out.xml");
+int theResult =
+ theXalanTransformer.transform(xmlIn,xslIn,xmlOut)
+</pre>
+</blockquote>
+
+<p>Alternatively, you can call transform() with the strings (system identifiers), streams, and/or DOMs that the compiler needs
+ to implicitly construct the <a href="apiDocs/classXSLTInputSource.html">XSLTInputSource</a> and
+ <a href="apiDocs/classXSLTResultTarget.html">XSLTResultTarget</a> objects. For example:</p>
+<blockquote class="source">
+<pre>
+const char* xmlIn = "foo.xml";
+const char* xslIn = "foo.xsl";
+const char* xmlOut = "foo-out.xml";
+int theResult =
+ theXalanTransformer.transform(xmlIn,xslIn,xmlOut)
+</pre>
+</blockquote>
+<p>Keep in mind that <a href="apiDocs/classXSLTInputSource.html">XSLTInputSource</a> and
+ <a href="apiDocs/classXSLTResultTarget.html">XSLTResultTarget</a> provide a variety of single-argument constructors that
+ you can use in this manner:</p>
+<ul>
+ <li>
+<code>XSLTInputSource(const char* systemID);</code>
+</li>
+ <li>
+<code>XSLTInputSource(const XMLCh* systemID);//Unicode chars</code>
+</li>
+ <li>
+<code>XSLTInputSource(istream* stream);</code>
+</li>
+ <li>
+<code>XSLTInputSource(XalanNode* node);</code>
+<br />
+<br />
+</li>
+ <li>
+<code>XSLTResultTarget(char* fileName);</code>
+</li>
+ <li>
+<code>XSLTResultTarget(XalanDOMString& fileName);</code>
+</li>
+ <li>
+<code>XSLTResultTarget(ostream* stream);</code>
+</li>
+ <li>
+<code>XSLTResultTarget(ostream& stream);</code>
+</li>
+ <li>
+<code>XSLTResultTarget(Writer* characterStream);</code>
+</li>
+ <li>
+<code>XSLTResultTarget(XalanDocument* document);</code>
+</li>
+ <li>
+<code>XSLTResultTarget(XalanDocumentFragment* documentFragment);</code>
+</li>
+ <li>
+<code>XSLTResultTarget(XalanElement* element);</code>
+</li>
+ <li>
+<code>XSLTResultTarget(FormatterListener& flistener);</code>
+</li>
+</ul>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">Each transform() method returns an integer code, 0 for success. If an error occurs, you can use the getLastError() method
+ to return a pointer to the error message.</td>
+</tr>
+</table>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>6. Shut down Xalan.</h4>
+<p>When you shut down Xalan, you may also want to shut down Xerces and ICU support (if enabled). Keep the following considerations
+ in mind:</p>
+<ul>
+ <li>Once you have shut down Xerces, you can no longer make Xalan or Xerces calls in the current process.<br />
+<br />
+</li>
+ <li>Shut down ICU support if you have enabled it (see <a href="#icusupport">enabling ICU support</a>) and if the
+ application is exiting or no longer requires the ICU. The <code>XMLPlatformUtils::Terminate()</code> call does nothing
+ if ICU support has not been enabled.</li>
+ <li>Ensure that there are no Xalan-C++ or Xerces-C++ objects extant at the point of termination. Any deletion of objects after
+ termination could cause errors.</li>
+</ul>
+<p>Use the static terminators.</p>
+<blockquote class="source">
+<pre>
+XalanTransformer::terminate();
+XMLPlatformUtils::Terminate();
+XalanTransformer::ICUCleanUp();
+</pre>
+</blockquote>
+
+
+
+<a name="stylepi">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Using a stylesheet processing instruction</h3>
+<p>If you want to use the stylesheet referred to by a stylesheet processing instruction in the XML document, simply call
+ transform() without the second XSLTInputSource argument. For example:</p>
+<blockquote class="source">
+<pre>
+// foo.xml contains a stylesheet PI
+const char* xmlIn = "foo.xml";
+const char* xmlOut = "foo-out.xml";
+int theResult =
+ theXalanTransformer.transform(xmlIn,xmlOut)
+</pre>
+</blockquote>
+
+
+<a name="params">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Setting Stylesheet Parameters</h3>
+
+<p>An XSL stylesheet can include parameters that are set at run time before a transformation takes place. Traditionally, a top-level parameter value is of text string type. The Xalan library now supports three types of top-level parameters that can be set. One is a text string parameter. Another is a number parameter of floating point type double. The third is a nodeset (XalanNode *) parameter, usually implemented as a parsed document.</p>
+
+<p>Any XObject that is created outside of the transformation can be associated with a top-level parameter. The XalanTransformer has an XObject factory whereby top-level parameters can be owned by the XalanTransformer object.</p>
+
+<p>To set a stylesheet parameter, use the
+<a href="apiDocs/classXalanTransformer.html">XalanTransformer</a> setStylesheetParam() method. The setStylesheetParam() method takes two arguments: the parameter name and the value. The value can be a string type, a number double type, an (XalanNode *) pointer to a nodeset or parsed document, or any XObjectPtr returned from an XObject factory.</p>
+
+<p>Top level parameters are sticky. Once set to an instance of an XalanTransformer object, they can be used for multiple transformations. The XalanTransformer reset() method prepares a transformer for a new transformation. Use the clearStylesheetParams() method to release the top-level stylesheet parameters.</p>
+
+<p>The Xalan command line utility currently supports only a text string value for a top-level stylesheet parameter. The single quotes are required to identify a text string value.</p>
+
+<p>
+<code>Xalan -p param1 "'string expression'"foo.xml foo.xsl</code>
+</p>
+
+<p>If the string expression includes spaces or other characters that the shell intercepts, first enclose the string in single quotes so Xalan-C++ interprets it as a string expression, and then enclose the resulting string in double quotes so the shell interprets it as a single argument.</p>
+
+<p>The <a href="samples.html#usestylesheetparam">UseStylesheetParam</a> sample application supports all three types of top-level stylesheet parameters.</p>
+
+<p>The 'C' language interface XalanCAPI also supports the three types of top-level parameters. The sample program TestCAPIparms.c shows how to use top-level parameters with 'C' language programs.</p>
+
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">The Xalan command line utility should be revised to accommodate the number and nodeset types of top-level stylesheet parameters. Only text string values are currently supported.</td>
+</tr>
+</table>
+
+<p>Top-level stylesheet parameters of nodeset type (XalanNode *) are useful for the merging of multiple XML documents.</p>
+
+
+<a name="incremental">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Processing output incrementally</h3>
+<p>
+<a href="apiDocs/classXalanTransformer.html">XalanTransformer</a> provides a transform() method that sends the output in blocks
+to a callback function, which enables you to begin processing the output while the transformation is still in process:</p>
+<blockquote class="source">
+<pre>
+int
+transform(const XSLTInputSource& xmlIn,
+ const XSLTInputSource& xslIn,
+ void* theOutputHandle,
+ XalanOutputHandlerType theOutputHandler,
+ XalanFlushHanderType theFlushHandler = 0);
+</pre>
+</blockquote>
+<p>For an example, see <a href="samples.html#xalantransformercallback">XalanTransformerCallback</a>.</p>
+
+
+<a name="compiled">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Performing a series of transformations</h3>
+<p>Before Xalan performs a standard transformation, it must parse the XML document and compile the XSL stylesheet into binary
+ representations. If you plan to use the same XML document or stylesheet in a series of transformations, you can improve performance
+ by parsing the XML document or compiling the stylesheet once and using the binary representation when you call transform().</p>
+<p>
+<a href="apiDocs/classXalanTransformer.html">XalanTransformer</a> includes methods for creating compiled stylesheets and
+ parsed XML documents: the compileStylesheet() method returns a pointer to a <a href="apiDocs/classXalanCompiledStylesheet.html">
+ XalanCompiledStylesheet</a>; the parseSource() method returns a pointer to a <a href="apiDocs/classXalanParsedSource.html">
+ XalanParsedSource</a>.</p>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">In the case of failure, both methods return 0.</td>
+</tr>
+</table>
+<p>Example using a XalanCompiledStylesheet to perform multiple transformations:</p>
+<blockquote class="source">
+<pre>
+XalanCompiledStylesheet* compiledStylesheet = 0;
+compiledStylesheet = theXalanTransformer.compileStylesheet("foo.xsl");
+assert(compiledStylesheet!=0);
+theXalanTransformer.transform("foo1.xml", *compiledStylesheet, "foo1.out.");
+theXalanTransformer.transform("foo2.xml", *compiledStylesheet, "foo2.out");
+...
+</pre>
+</blockquote>
+<p>For a working sample, see the <a href="samples.html#compilestylesheet">CompileStylesheet</a> sample.</p>
+<p>Example using a XalanParsedSource for multiple transformations:</p>
+<blockquote class="source">
+<pre>
+XalanParsedSource* parsedXML = 0;
+parsedXML = theXalanTransformer.parseSource("foo.xml");
+assert(parsedXML!=0);
+theXalanTransformer.transform(*parsedXML, "foo1.xsl", "foo-xsl1.out");
+theXalanTransformer.transform(*parsedXML, "foo2.xsl", "foo-xsl2.out");
+...
+</pre>
+</blockquote>
+<p>For a sample that uses both a parsed XML source and a compiled stylesheet, see <a href="samples.html#threadsafe">ThreadSafe
+</a>.</p>
+
+
+<a name="dom">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Working with DOM input and output</h3>
+<p>You can set up an <a href="apiDocs/classXSLTResultTarget.html">XSLTResultTarget</a> to produce a DOM when you perform a
+ transformation. You can also use a DOM as input for a transformation.</p>
+<p>The following code fragment illustrates the procedures for working with DOM output :</p>
+<blockquote class="source">
+<pre>
+
+// Use the Xerces DOM parser to create a DOMDocument.
+
+#include <xercesc/dom/DOMDocument.hpp>
+#include <xercesc/dom/DOMImplementation.hpp>
+
+#include <xalanc/XMLSupport/FormatterToXML.hpp>
+#include <xalanc/XMLSupport/XalanTransformer.hpp>
+
+XALAN_USING_XERCES(DOMDocument)
+XALAN_USING_XERCES(DOMImplementation)
+
+XALAN_USING_XALAN(FormatterToXML)
+XALAN_USING_XALAN(XalanTransformer)
+
+
+ // If you want to produce DOM output, create an empty Xerces Document
+ // to contain the transformation output.
+
+ DOMDocument * theDOM =
+ DOMImplementation::getImplementation()->createDocument();
+
+ // Now create a FormatterListener which can be used by the transformer
+ // to send each output node to the new Xerces document
+
+ FormatterToXercesDOM theFormatter(theDOM);
+
+ // Now do the transform as normal
+ XalanTransformer theXalanTransformer
+ int theResult = theXalanTransformer.transform(
+ "foo.xml",
+ "foo.xsl",
+ theFormatter);
+...
+
+ // After you perform the transformation, the DOMDocument contains
+ // the output.
+</pre>
+</blockquote>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">You can also follow the same process but use a <b>FormatterToDeprecatedXercesDOM</b> if you require a DOM_Document
+ output. However this is discouraged, as support for the deprecated DOM may be removed in future releases of Xalan-C++</td>
+</tr>
+</table>
+<p>If you want to use a Xerces DOM object as input for a transformation without wrapping the DOM in a XercesParserLiaison, see
+ <a href="#xercesdomwrapperparsedsource">passing in a Xerces DOM</a>.</p>
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Limitations</h4>
+<p>Performance is much better when Xalan-C++ uses native source tree handling rather than interacting with the Xerces DOMParser.</p>
+<p>If you are using the deprecated DOM, the Xerces DOMParser by default, creates a DOM_XMLDecNode in the DOM tree to represent
+ the XML declaration. The Xalan bridge for the Xerces DOM does not support this non-standard node type. Accordingly, you must
+ call DOMParser::setToCreateXMLDeclTypeNode(false) <b>before</b> you parse the XML file. If not, the behavior is undefined,
+ and your application may crash.</p>
+
+
+<a name="xercesdomwrapperparsedsource">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Passing in a Xerces DOM to a transformation</h4>
+<p>You may want to use a Xerces DOM that was created without using the XalanTransformer class. As the following code snippet
+ illustrates, you can use <a href="apiDocs/classXercesDOMWrapperParsedSource.html">XercesDOMWrapperParsedSource</a> to
+ pass in a Xerces DOM as the source for an XSL transformation.</p>
+<blockquote class="source">
+<pre>
+#include <xercesc/parsers/DOMParser.hpp>
+#include <xalanc/XalanTransformer/XercesDOMWrapperParsedSource.hpp>
+
+void parseWithXerces(XalanTransformer &xalan,
+ const XSLTInputSource &xmlInput,
+ const XalanCompiledStylesheet* styleSheet,
+ const XSLTResultTarget &output,
+ XMLFileReporter &logFile)
+{
+ XercesDOMParser theParser;
+
+ // Turn on validation and namespace support.
+ theParser.setDoValidation(true);
+ theParser.setDoNamespaces(true);
+
+ // Parse the document
+
+ theParser.parse(xmlInput);
+ DOMDocument *theDOM = theParser.getDocument();
+ theDOM->normalize();
+
+ XercesDOMSupport theDOMSupport;
+ XercesParserLiaison theParserLiaison;
+
+ // Use the DOM to create a XercesDOMWrapperParsedSource,
+ // which you can pass to the transform method.
+ try
+ {
+ const XercesDOMWrapperParsedSource parsedSource(
+ theDOM,
+ theParserLiaison,
+ theDOMSupport,
+ XalanDOMString(xmlInput.getSystemId()));
+
+ xalan.transform(parsedSource, stylesheet, output);
+
+ }
+ catch (....)
+ {
+ ...
+ }
+}
+</pre>
+</blockquote>
+
+
+
+<a name="xpath">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Working with XPath expressions</h3>
+<p>XSL stylesheets use XPath expressions to select nodes, specify conditions, and generate text for the result tree. XPath
+ provides an API that you can call directly. For example, you may want to select nodes programmatically and do your own
+ processing without a stylesheet. Xalan-C++ provides an XPathEvaluator interface to simplify the process of executing XPath
+ expressions.</p>
+<p>For an example that executes XPath expressions against XML source files, see <a href="samples.html#simplexpathapi">
+ SimpleXPathAPI</a> (takes advantage of the XPathEvaluator interface) and <a href="samples.html#xpathwrapper">
+ XPathWrapper</a>.</p>
+
+
+<a name="tracelistener">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Using TraceListener</h3>
+<p>TraceListener is a debugging abstract base class implemented by TraceListenerDefault. You can use TraceListener to trace
+ any combination of the following:</p>
+<ul>
+ <li>Calls to templates</li>
+ <li>Calls to template children</li>
+ <li>Selection events</li>
+ <li>Result tree generation events</li>
+</ul>
+<p>To construct a TraceListener with TraceListenerDefault, you need a PrintWriter and a boolean for each of these four
+ tracing options. You can then use the XSLTEngimeImpl setTraceSelects and addTraceListener methods to add the TraceListener
+ to an XSLTProcessor. See the <a href="samples.html#tracelisten">TraceListen</a> sample application.</p>
+<p>The TraceListen uses TraceListenerDefault to write events to the screen.</p>
+
+
+<a name="icu">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Using the ICU</h3>
+<p>You can use the <a href="http://oss.software.ibm.com/icu/index.html">International Components for Unicode (ICU)</a> to extend support for encoding, number formatting, and sorting.</p>
+<ul>
+ <li>
+<b>Encoding</b>
+ <br /> Xerces-C++ and Xalan-C++ use UTF-16 encoding to work with Unicode data. If you integrate the ICU with Xerces-C++, both
+ Xerces-C++ and Xalan-C++ use ICU support for input and output transcoding.<br />
+<br />
+</li>
+ <li>
+<b>format-number()</b>
+ <br />This XSLT function includes two or three arguments (the third is optional): number, format pattern, and decimal-format
+ name. Xalan-C++ ignores the format pattern and optional decimal-format name. If you install ICU support for format-number(),
+ this function is fully supported with all its arguments.<br />
+<br />
+</li>
+ <li>
+<b>xsl:sort</b>
+ <br />If you install ICU support for xml:sort, Xalan-C++ implements Unicode-style collation.</li>
+</ul>
+
+<p>If you choose to build Xalan with ICU, you will need to rebuild Xerces with ICU as well.</p>
+<p>To get the ICU:</p>
+<ol>
+ <li>Download and unzip the <a href="http://oss.software.ibm.com/icu/download/index.html">International Components for Unicode(ICU) 3.2 source files</a> from the IBM developerWorks open source zone.<br />
+<br />
+</li>
+ <li>Do an ICU build -- see the Windows NT or Unix build instructions in the build_instruct.html that accompanies the download.<br />
+ <b>Important</b> For Windows, define the environment variable ICUROOT and then restart Visual C++ or Visual Studio .NET.
+ in order for the ICUROOT variable to take effect.<br />
+<br />
+</li>
+</ol>
+
+<a name="icusupport">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Enabling ICU support for encoding</h4>
+<p>If you want to enable ICU support for encoding, you must integrate ICU with your Xerces-C++ build. Xerces-C++ uses ICU for input
+ encoding. See <a href="http://xml.apache.org/xerces-c/build.html#BuildICU">Building ICU for Xerces-C++</a>.</p>
+<p>Once you have integrated the ICU with Xerces-C++, Xalan-C++ automatically uses ICU support for output encoding (the xsl:output
+ encoding attribute).</p>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Enabling ICU support for number formatting and sorting</h4>
+<p>If you only want to use the ICU to support number formatting and sorting, you do not need to integrate the ICU with Xalan-C++,
+ but you must do the following in the application where you want to enable ICU support:</p>
+<ol>
+ <li>Define the environment variable ICUROOT.<br />
+<br />
+</li>
+ <li>Substitute ICU support for format-number(), xsl:number, and/or xsl:sort.<br />
+<br />
+</li>
+ <li>Rebuild the Xalan library to include the ICUBridge.</li>
+</ol>
+<p>
+<b>ICUBridge</b>
+</p>
+<p>All Xalan-C++ references to ICU are centralized in the ICUBridge module, which supplies the infrastructure for enabling ICU
+ support for number formatting and sorting.</p>
+<blockquote class="source">
+<pre>
+#include <xalanc/ICUBridge/ICUBridge.hpp>
+#include <xalanc/ICUBridge/FunctionICUFormatNumber.hpp>
+#include <xalanc/ICUBridge/ICUXalanNumberFormatFactory.hpp>
+#include <xalanc/ICUBridge/ICUBridgeCollationCompareFunctor.hpp>
+</pre>
+</blockquote>
+<p>For Windows, do a clean build of the Xalan library using the "XalanICU.dsw" workspace (for Visual C++ users) or
+ "XalanICU.sln" solution (for Visual Studio .NET users).</p>
+<p>For UNIX:</p>
+<ol>
+ <li>Define the XALAN_USE_ICU environment variable.<br />
+<br />
+</li>
+ <li>Set the XALANROOT environment variable to the path to to the ICU root (unless you have copied the ICU library to
+ /usr/lib).<br />
+<br />
+</li>
+ <li>
+<a href="build_instruct.html#unix">Rebuild the Xalan library</a> (libxalan-c.so.111 for Linux, libxalan-c111.so for AIX,
+ libxalan-c.sl.111.0 for HP-UX 11, and libxalan-c1_11.so for Solaris).<br />
+<br />
+</li>
+ <li>Be sure the Xalan library is on the library path (LD_LIBRARY_PATH for Red Hat Linux, LIBPATH for AIX, SHLIB_PATH for
+ HP-UX 11, LD_LIBRARY_PATH for Solaris).</li>
+</ol>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">The command you use for setting environment variables depends on the shell you are using.<br />
+ For Bourne Shell, K Shell, or Bash use <b>export</b> ENVAR="val"<br />
+ For C Shell, use <b>setenv</b> ENVAR "val"<br />
+ where ENVAR is the environment variable name and val is the environment variable
+ setting. You can check the setting of an environment variable with <b>echo</b> $ENVAR<br />To define XALAN_USE_ICU,
+ set its value to "1".
+</td>
+</tr>
+</table>
+<p>
+<b>Number formatting</b>
+</p>
+<p>To enable ICU support for the XSLT format-number() function, do the following:</p>
+<blockquote class="source">
+<pre>
+// Install ICU support for the format-number() function.
+FunctionICUFormatNumber::FunctionICUFormatNumberInstaller theInstaller;
+</pre>
+</blockquote>
+
+<p>
+<b>Sorting</b>
+</p>
+<p>To enable ICU support for xsl:sort, do the following:</p>
+<blockquote class="source">
+<pre>
+// Set up a StylesheetExecutionContextDefaultobject
+// (named theExecutionContext in the following fragment),
+// and install the ICUCollationCompareFunctor.
+ICUBridgeCollationCompareFunctortheICUFunctor;
+theExecutionContext.installCollationCompareFunctor(&theICUFunctor);
+</pre>
+</blockquote>
+
+
+
+<a name="capi">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Basic XalanTransformer usage pattern with the C API</h3>
+<p>We also include a simple C interface for using the XalanTransformer class. See <a href="apiDocs/XalanCAPI_8h.html">
+ XalanTransformer/XalanCAPI.h</a>. The <a href="samples.html#apachemodulexslt">ApacheModuleXSLT</a> sample
+ illustrates the use of this C API.</p>
+<p>Basic strategy:</p>
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>1. Include the XalanTransformer C API header</h4>
+<blockquote class="source">
+<pre>#include <XalanTransformer/XalanCAPI.h></pre>
+</blockquote>
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>2. Initialize Xalan and Xerces</h4>
+<blockquote class="source">
+<pre>XalanInitialize();</pre>
+</blockquote>
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>3. Create a Xalan transformer</h4>
+<blockquote class="source">
+<pre>
+XalanHandle xalan = NULL;
+xalan = CreateXalanTransformer();
+</pre>
+</blockquote>
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>4. Perform each transformation</h4>
+<p> For example:</p>
+<blockquote class="source">
+<pre>
+const char * xmlfilename = "foo.xml";
+const char* xslfilename = "foo.xsl";
+const char* outfilename = "foo.out";
+int theResult = 0;
+theResult = XalanTransformToFile(xmlfilename,
+ xslfilename,
+ outfilename,
+ xalan);
+</pre>
+</blockquote>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">If the XML input file contains a stylesheet processing instruction that you want to use, use an empty XSLTInputSource
+ for the stylesheet argument.</td>
+</tr>
+</table>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>5. Shut down Xalan</h4>
+<blockquote class="source">
+<pre>XalanTerminate();</pre>
+</blockquote>
+
+
+
+<a name="cvar">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Variations with the XalanTransformer C API</h3>
+<p>The <a href="apiDocs/XalanCAPI_8h.html">Xalan C API</a> supports approximately the same set of options as the C++ API.
+ In particular, you can</p>
+<ul>
+ <li>Use stylesheet processing instructions (PI) to indicate the URI of the stylesheet. Supply NULL for the stylesheet argument.<br />
+<br />
+</li>
+ <li>Set stylesheet parameters. Use the SetStylesheetParam() function.<br />
+<br />
+</li>
+ <li>Compile stylesheets. Use the CompileStylesheet() method to compile a stylesheet, and the TransformToFileCSS() or TransformToDataCSS() function to use the compiled stylesheet in a transformation.<br />
+<br />
+</li>
+ <li>Parse XML sources. Use the XalanParseSource() or XalanParseSouceUseXalan() method.<br />
+<br />
+</li>
+ <li>Place the transformation output in a character array. Use the TransformToData() or TransformToDataCSS() function. After you perform the transformation, use the XalanFreeData() function to free memory allocated for the output data.<br />
+<br />
+</li>
+ <li>Send the output to a callback function to process blocks of output data as they arrive.</li>
+</ul>
+<p>For a sample that sends output in blocks to a callback function, see <a href="samples.html#apachemodulexslt">
+ ApacheModuleXSLT</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 - Fri 06/15/2012</div>
+</div>
+</body>
+</html>
Added: xalan/site/docs/xalan/xalan-c/whatsnew.html
URL: http://svn.apache.org/viewvc/xalan/site/docs/xalan/xalan-c/whatsnew.html?rev=1350856&view=auto
==============================================================================
--- xalan/site/docs/xalan/xalan-c/whatsnew.html (added)
+++ xalan/site/docs/xalan/xalan-c/whatsnew.html Sat Jun 16 03:57:36 2012
@@ -0,0 +1,718 @@
+<?xml version="1.0" encoding="ISO-8859-1" 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: What's New in this Release</title>
+<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" />
+<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">What's New in this Release</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>What's New<br />
+</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://xml.apache.org/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>What's New in this Release</h2>
+
+ <ul>
+ <li>
+<a href="#status">Status</a>
+</li>
+ <li>
+<a href="#contact">Getting in Touch</a>
+</li>
+ <li>
+<a href="#history">History of Software Changes</a>
+</li>
+ <li>
+<a href="#bugfix11">Bug Fixes in Release 1.11</a>
+</li>
+ <li>
+<a href="#bugfix10">Bug Fixes in Release 1.10</a>
+</li>
+ <li>
+<a href="#bugs">Bug reporting</a>
+</li>
+ <li>
+<a href="#to-do">To-do tasks for future Xalan-C/C++ releases</a>
+</li>
+ </ul>
+
+<a name="status">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Status</h3>
+
+<p>
+<b>Release notes for Xalan-C/C++ Version 1.11</b>
+</p>
+<p>This is primarily a bug-fix release of version 1.10. Support for number and
+nodeset types for stylesheet top-level parameters has been added. Xerces-C/C++
+versions 3.0 and newer are now supported. Xerces-C/C++ Version 3.1.1 is the
+preferred stable release.
+</p>
+<p>At present, the Xalan-C/C++ Version 1.11 has no binary releases.
+When building Xalan-C/C++ from sources,
+you should use the same platform that was used to
+compile the companion Xerces-C/C++ library.
+</p>
+<p>Binary package releases for Microsoft Windows are being planned.
+</p>
+<p>If you are able to successfully create a new binary package and wish it
+to be included, then we welcome your participation on the
+<a href="mailto:xalan-dev@xml.apache.org">xalan-dev</a> mail list.
+</p>
+<p>Xalan-C/C++ no longer supports Microsoft Studio (VC6). The Microsoft Visual
+Studio .NET platforms (2003, 2005, 2008, and 2010) are supported. This equates
+to compilers (VC71, VC8, VC9, and VC10).
+</p>
+
+
+
+<a name="contact">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Getting in Touch</h3>
+<p>Your feedback is more than welcome. Offers of help are even more so!
+Perhaps you would like to contribute to the ongoing development,
+testing, or documentation of Xalan-C++.
+</p>
+<p>Please email your comments, questions, suggestions, bug reports,
+and offers to help to <a href="mailto:xalan-dev@xml.apache.org">Xalan Development Mailing List</a>.
+</p>
+<p>Your general user comments on Xalan-C++ usage are also welcome on
+<a href="mailto:xalan-c-users@xml.apache.org">Xalan-C/C++ Users Mailing List</a>.
+</p>
+
+
+<a name="history">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Cumulative history of software changes</h3>
+<p>The following sections list the changes in each release since Xalan-C++ version 0.40.0.</p>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 1.11</h4>
+<p>This is a general bug fix release with added stability features.</p>
+<p>Major updates since version 1.10 include:</p>
+<ul>
+ <li>Add support for Xerces-C 3.0 and newer</li>
+ <li>Drop support for Microsoft Studio (VC6)</li>
+ <li>Fix support issues for AIX 5.3</li>
+ <li>Fix support issues for Solaris 2.8</li>
+ <li>Fix support issues for GCC-4.3</li>
+ <li>Add support for Microsoft .NET 2008 (VC9) </li>
+ <li>Add support for Microsoft .NET 2010 (VC10)</li>
+ <li>Add number and nodeset types as top-level stylesheet parameters</li>
+ <li>
+<a href="#bugfix11">Bugs fixed in this release</a>.</li>
+</ul>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 1.10</h4>
+<p>Major updates since version 1.9 include:</p>
+<ul>
+ <li>Support for XML 1.1 and Namespaces in XML 1.1.</li>
+ <li>Added support for IBM XLC 7.0 compiler on AIX.</li>
+ <li>Improved and stabilized C pluggable memory management functionality.</li>
+ <li>Various improvements in Xalan XML serializers for better performance and stability.</li>
+ <li>Upgrade from Xerces-C 2.6 to Xerces-C 2.7.</li>
+ </ul>
+
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 1.9</h4>
+<p>Major updates since version 1.8 include:</p>
+<ul>
+ <li>Pluggable Memory Management. This feature allows applications to maintain precise control over memory allocations. This
+ will allow users, with knowledge of their application's characteristics, to provide a more efficient allocation method
+ than the general purpose procedures provided by the system. for more information on how to use this feature, please see
+ the <a href="programming.html#memory">Pluggable Memory Management</a> section of the Programming page.</li>
+ <li>Improved stability on the execution of large stylesheets and XML documents. Because the current implementation relies on
+ function recursion, certain stylesheets/input documents may cause the program stack to overflow and cause the application
+ to fail. It also may inhibit executing stylesheets that are heavily dependent on recursive functions. This feature will
+ prevent these types of failure. </li>
+ <li>Provided a global option to pool all text node strings. This feature allows developers to set a flag to determine if a
+ parsed source tree will pool the values of all of the text nodes in the XML document. By doing so, this can result in a
+ significant reduction in memory usage, particularly if there are a lot of repeated values in text nodes. Please see
+ the class descriptions for <a href="apiDocs/classXalanSourceTreeDocument.html">XalanSourceTreeDocument</a>,
+ <a href="apiDocs/classXalanDefaultParsedSource.html">XalanDefaultParsedSource</a>, and
+ <a href="apiDocs/classXalanTransformer.html">XalanTransformer</a> in the <a href="apiDocs/index.html">
+ API Reference</a> section for more information.</li>
+ <li>Added support for Microsoft Studio .NET V7.1. Project files for Microsoft Studio .NET V7.1 have been provided under the
+ directory xml-xalan\c\Projects\Win32\VC7.1.</li>
+ <li>Upgrade from Xerces-C 2.5 to Xerces-C 2.6. </li>
+ </ul>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 1.8</h4>
+ <p>Major updates since version 1.7 include:</p>
+ <ul>
+ <li>Upgrade from Xerces-C 2.4 to Xerces-C 2.5. </li>
+ <li>Provide build support for Cygwin and HP-UX 11.00 on Itanium. Although binary distributions are not provided for the Cygwin environment and
+ HP-UX 11.00 on Itanium platform, the build configuration files provided in the source distribution can be used to build on these platforms. </li>
+ <li>Project files for supporting Microsoft Visual Studio .NET. Although a binary distribution for the Microsoft Visual Studio .NET
+ is not provided in this release, Visual Studio solution files are provided in the Windows source distribution for those who choose to build
+ on this platform. Please see <a href="build_instruct.html#dotNet">"Step for doing a Windows Build with Visual Studio .NET"</a>
+ for details.</li>
+ <li>Additional changes to Xerces Deprecated DOM support. This is another step towards phasing out the support for Xerces Deprecated DOM. Users
+ are encouraged to modify their applications to interface with the new Xerces DOM support. For more information on the effects of these
+ changes to your build environment, please see <a href="#xercesdepdom">"Steps for doing a Build with Xerces Deprecated DOM Support"
+ </a>
+</li>
+
+ <li>Implemented optimizations to significantly improve the throughput of the ICU-enabled "format-number" function.</li>
+ <li>Changes in the XML Serializer. The serializer will no longer put a newline after the xml header tag unless indent="yes".</li>
+
+ </ul>
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 1.7</h4>
+ <p>Major updates since version 1.6 include:</p>
+ <ul>
+ <li>Message Localization Support. This feature enables Xalan-C++ to issue diagnostic messages
+ in languages other than the default language (English). In order to utilize this feature,
+ the user must provide a version of the Xalan-C++ message catalog that has been translated in
+ their language of choice. For more information on how to exploit this feature, please see
+ <a href="#locale">Steps for doing a Build with Message Localization Support</a>.</li>
+ <li>Build, packaging, and installation improvements. Changes to the Xalan-C++ makefiles now
+ allow for a more flexible build, packaging, and install process. Each step in a typical
+ build process can be invoked by specifying the appropriate target, for example to build the
+ executable, and/or samples, or install the build at user-specified location. For more
+ information on building Xalan-C++, please see <a href="#unix">Steps for doing a Unix build
+ </a>.</li>
+ <li>Deprecated DOM Support. The XercesBridge classes have been marked deprecated and moved
+ into an exclusive directory within the xalanc/XercesParserLiaison directory called
+ 'Deprecated'. If your application is dependent on these classes to interface with the
+ deprecated Xerces DOM you must alter your include directive with the 'Deprecated' directory.
+ For example:<br />
+<br />
+ <code>#include "xalanc/XercesParserLiaison/XercesDocumentBridge.hpp"</code>
+<br />
+<br />
+ should be changed to:<br />
+<br />
+ <code>#include "xalanc/XercesParserLiaison/Deprecated/XercesDocumentBridge.hpp"</code>
+<br />
+<br />
+</li>
+ <li>Upgrade from Xerces-C 2.3 to Xerces-C 2.4. </li>
+ <li>Porting of ThreadSafe example to UNIX platform.</li>
+ <li>Implementation of EXSLT string extension functions encode-uri() and decode-uri(). </li>
+ <li>Implementation of EXSLT dynamic extension function evaluate(). </li>
+ <li>Implementation of EXSLT date-time extension function date-time().</li>
+ </ul>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 1.6</h4>
+ <p>Major updates since version 1.5 include:</p>
+ <ul>
+ <li>Directory "sane include" reorganization. A new sub-directory called 'xalanc' has been added to the src directory (for source distribution packages) and include directory (for binary distribution packages). New source files which include Xalan headers will need to be modified to include the 'xalanc' prefix in the header path.
+ For example: <br />
+<br />
+ <code>#include <XPath/XObject.hpp></code>
+<br />
+<br />
+ will need to be changed to <br />
+<br />
+ <code>#include <xalanc/XPath/XObject.hpp></code>
+<br />
+<br />
+ For Windows users, all project files have been modified to reflect this change. For UNIX users, please see <a href="#unix">Steps for doing a UNIX build</a> for migration considerations.</li>
+ </ul>
+
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 1.5</h4>
+ <p>Major updates since version 1.4 include:</p>
+ <ul>
+ <li>For Windows, Xalan-C++ is now packaged as a single DLL. The project files to build separate DLLs are now deprecated and will not be maintained.</li>
+ <li>Support for Xerces-C++ DOMNode classes.</li>
+ <li>New sample <b>TransformToXercesDOM</b> that illustrates how to perform a transform resulting in a Xerces-C++ DOMDocument</li>
+ <li>Usage of the Xerces-C++ C++ namespace and creation of Xalan-C++ namespace.</li>
+ </ul>
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 1.4</h4>
+ <p>Major updates since version 1.3 include:</p>
+ <ul>
+ <li>The Xalan-C++ distributions no longer include the Xerces-C++ headers and libraries. Accordingly, you must download the appropriate Xerces-C++ distribution (see <a href="getstarted.html#download">Downloading what you need</a>.</li>
+ <li>64-bit build for HP-11; <a href="#64">untested 64-bit support</a> for Solaris and AIX.</li>
+ <li>New Linux platform and compiler: Redhat 7.2 with gcc 3.1.</li>
+ <li>
+<a href="http://www.stlport.org/">STLport</a> is no longer required on any of our supported platforms.</li>
+ <li>
+<a href="extensionslib.html#exslt">Alpha support for a number of EXSLT functions</a>.</li>
+ <li>
+<a href="samples.html#parsedsourcewrappers">ParsedSourceWrappers</a>, a sample that
+ illustrates how to perform transformations with input in the form of a pre-built
+ XalanDOM or XalanSourceTree.</li>
+ </ul>
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 1.3</h4>
+ <p>Major updates since version 1.2 include:</p>
+ <ul>
+ <li>A new and simplified command-line utility: <a href="commandline.html#xalanexe">the Xalan executable</a>
+</li>
+ <li>New XPath samples exploiting the XPathEvaluator C API and illustrating serialization of an XPath result set: <a href="samples.html#simplexpathcapi">SimpleXPathCAPI</a> and <a href="samples.html#serializenodeset">SerializeNodeSet</a>
+</li>
+ <li>A new <a href="usagepatterns.html#xercesdomwrapperparsedsource">wrapper class</a> that lets you pass in a Xerces DOM as input for a transformation</li>
+ <li>Bug fixes.</li>
+ <li>Changed XPathException to XalanXPathException because of a clash with a new Xerces class of the same name.</li>
+ </ul>
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 1.2</h4>
+ <p>Major updates since version 1.1 include:</p>
+ <ul>
+ <li>
+<a href="extensionslib.html">Introduction of a library of extension functions</a>
+</li>
+ <li>Support for pre-parsed source documents and pre-compiled stylesheets in
+ <a href="apiDocs/classXalanTransformer.html">XalanTransformer</a> and the C API.</li>
+ <li>Support for stylesheet params in <a href="apiDocs/classXalanTransformer.html">XalanTransformer</a>
+ and the C API</li>
+ <li>Support for extension functions in <a href="apiDocs/classXalanTransformer.html">XalanTransformer</a>
+</li>
+ <li>Performance enhancements</li>
+ </ul>
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 1.1</h4>
+ <p>In addition to adding to the list of platforms on which Xalan-C++ builds, our focus for this release has been on bug fixes, performance enhancements,
+ and providing a simplified C++ and C API for performing standard transformations. Major updates since version 1.0 include:</p>
+ <ul>
+ <li>Added HP-UX 11 build.</li>
+ <li>Added Solaris build.</li>
+ <li>Greatly improved performance.</li>
+ <li>Improved conformance to the XSLT specification.</li>
+ <li>Simplified the C++ API and provided a C API for performing standard transformations with the <a href="usagepatterns.html#xalantransformer">XalanTransformer</a> class and associated header files.</li>
+ <li>Added sample illustrating use of XalanTransformer and the new C++ API:
+ <a href="samples.html#xalantransform">XalanTransform</a>.</li>
+ <li>Added sample illustrating use of XalanTransformer, the new C API, and how to run Xalan-C++ and perform transformations on an
+ Apache Web server: <a href="samples.html#apachemodulexslt">ApacheModuleXSLT</a>.</li>
+ <li>Added the <a href="samples.html#streamtransform">StreamTransform</a> sample.</li>
+ <li>Eliminated dependencies on non-public Xerces headers; accordingly can now build with the Xerces distribution.</li>
+ <li>Fixed namespace mapping and inheritance problems.</li>
+ <li>Fixed failure of <copy-of ...> to include CRLFs (if any) in the result.</li>
+ <li>Fixed bug sorting in reverse document order based on position. </li>
+ <li>Fixed <xsl:number> bug with use of letter-value="traditional" for "classical" Greek numbering.</li>
+ <li>Fixed use of <xsl:fallback> within a top-level extension function.</li>
+ <li>Fixed HTML output method bug. The <HEAD> element was not including a <META> tag with the encoding.</li>
+ <li>Fixed bug using key() in match patterns to find descendants.</li>
+ <li>Fixed bug using the id() function in complex match patterns.</li>
+ <li>Fixed problem outputting multiple single-character CDATA sections.</li>
+ <li>Fixed problem outputting whitespace characters.</li>
+ <li>Fixed problem transforming from a stream on UNIX platforms.</li>
+ <li>Fixed a bug with the document() function, which was generating a syntax error if called in the following manner: document(<b>
+<i>string</i>
+</b>,/).</li>
+ <li>Fixed named templates bug accepting global parameter when called with a parameter of the same name that the named template does not
+ recognize.</li>
+ </ul>
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 1.0</h4>
+ <p>Major updates since version 0.40.0 include:</p>
+ <ul>
+ <li>Full support for namespace handling</li>
+ <li>Full implementation of the format-number() function and support for the decimal-format element</li>
+ <li>Integration with the <a href="http://oss.software.ibm.com/icu/index.html">International Components for Unicode (ICU)</a> for number formatting, sorting, and output encoding</li>
+ <li>Support for the exclude-result-prefixes attribute</li>
+ <li>Support for the output encoding attribute</li>
+ </ul>
+
+ <p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h4>Changes for Xalan-C++ version 0.40.0</h4>
+ <p>Major updates since version 0.30.0 include:</p>
+ <ul>
+ <li>Permitting OS file names (as well as URLs) as command-line arguments with TestXSLT</li>
+ <li>Stricter compliance for HTML and XML output</li>
+ <li>Improved handling of relative URI's</li>
+ <li>Improved handling of Import and Include</li>
+ <li>Better namespace handling (although there are still problems here)</li>
+ <li>Support for Document() function</li>
+ <li>Support for XPath predicates</li>
+ <li>ProblemListener with a different output stream and call
+ XalanTransformer::setProblemListener() before calling XalanTransformer::transform().</li>
+ </ul>
+
+
+
+
+
+<a name="bugfix11">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Bug Fixes in Release 1.11</h3>
+<p>The bugs fixed in Xalan-C++ Version 1.11 include:</p>
+<ul>
+<li>XALANC-723 Add Top-Level parameter support for XalanCAPI and UseStylesheetParams sample</li>
+<li>XALANC-721: Upgrade support for MS VS 2010 (VC10)</li>
+<li>XALANC-719: Xerces Parser Liaison - errors on elements with no attributes</li>
+<li>XALANC-716: incorrect buffer-size calculation in XalanUTF16Writer.hpp</li>
+<li>XALANC-715: NULL pointer access crash</li>
+<li>XALANC-713: Build Xalan-C/C++ API Reference Manual using Doxygen 1.7 or newer</li>
+<li>XALANC-710: MS-Studio 2008 Debug Build sends Xalan-C_1D.lib to wrong directory</li>
+<li>XALANC-709: Doxygen bug in XalanQName.hpp</li>
+<li>XALANC-708: Including XalanCAPI.hpp does not import Xerces typedef XMLch</li>
+<li>XALANC-705: Crash with pure virtual function call</li>
+<li>XALANC-703: Compiler errors while building on AIX 5.3</li>
+<li>XALANC-700: Broken output when serializing UTF16 surrogates</li>
+<li>XALANC-699: Compile using Visual C++ 2010 (VC10)</li>
+<li>XALANC-698: Buffer overflow from XalanMessageLoader::load()</li>
+<li>XALANC-690: The document function does not handle fragment IDs in URLs correctly</li>
+<li>XALANC-689: XalanC transformation of a 600 kb file takes 43 seconds</li>
+<li>XALANC-684: XPath single quate-comma bug</li>
+<li>XALANC-683: xsl:number with level any does not always count all of the preceeding nodes in the document</li>
+<li>XALANC-681: NamedNodeMapAttributeList constructor asserts when the provided NamedNodeMap is empty</li>
+<li>XALANC-680: Error in match pattern with // and abbreviated attribute node test</li>
+<li>XALANC-679: Possible wrong evaluation of abbreviated XPath in template match</li>
+<li>XALANC-677: Debug assertion switching to HTML mode when the outputter is producing a DOM</li>
+<li>XALANC-675: No error is reported for an unknown key</li>
+<li>XALANC-675: GCC-4.3 cleanup</li>
+<li>XALANC-673: Assertion failed with XalanDOMString::substr</li>
+<li>XALANC-671: Incorrect handling of default namespace in xsl:element</li>
+<li>XALANC-669: XalanOtherEncodingWriter reports an incorrect error message</li>
+<li>XALANC-667: setUseValidation doesn't work</li>
+<li>XALANC-664: Testing harness writes strings to the output XML in the local code page.</li>
+<li>XALANC-661: PlatformSupport/DoubleSupport.cpp compile error on AIX 5.3</li>
+<li>XALANC-660: Compilation errors in Tests/Performance/TestHarness.hpp on some platforms</li>
+<li>XALANC-659: Unnecessary casting in ReusableArenaBlock</li>
+<li>XALANC-658: Misplaced assert in ReusableArenaAllocator::destroyObject()</li>
+<li>XALANC-657: Add Windows x64 targets to the project files</li>
+<li>XALANC-655: Boolean value incorrectly converted ot string in attribute value templates</li>
+<li>XALANC-653: Xalan-C not including namespace declaration in output</li>
+<li>XALANC-650: XPathProcessorImpl uses XalanDOMString copy constructor instead of referring to an existing instance</li>
+<li>XALANC-648: XalanUTF8Writer::write(const XalanDOMChar*, XalanDOMString::size_type) does not handle surrogates properly</li>
+<li>XALANC-647: XalanOtherEncodingWriter::writeNumericCharacterReference() is inefficient</li>
+<li>XALANC-646: During transcoding XalanC fails to append '0' to the transcoded string </li>
+<li>XALANC-645: Pluggin of DOMStringPrintWriter into FormatterToXML leads to assert</li>
+<li>XALANC-641: Class used as exception needs accessible copy constructor</li>
+<li>XALANC-640: Path problem in Makefile under cygwin</li>
+<li>XALANC-638: Performance test program does not build on HP-UX</li>
+<li>XALANC-635: Build fails on Solaris 2.8</li>
+<li>XALANC-634: Build fails with VC6</li>
+<li>XALANC-633: The processor should ignore xsl:fallback element in LRE </li>
+<li>XALANC-632: @use-attribute-sets attribute has to have no effect on xsl:copy when the context item is a documen node.</li>
+<li>XALANC-631: The next stylesheet crashes XalanC</li>
+<li>XALANC-630: Incorrect cast in XalanUTF16Writer</li>
+<li>XALANC-629: Performance improvements for text node stripping</li>
+<li>XALANC-628: Inconsistent flusing of serializers</li>
+<li>XALANC-627: Broken cast in ElemTemplateElement::findTemplateToTransformChild()</li>
+<li>XALANC-626: Fix copyrights in Apache XalanC source</li>
+<li>XALANC-625: Spurious (though harmless) assert failure in XPath::findNodeSet() when an expression contains an empty node-set enclosed in parenthesis</li>
+<li>XALANC-624: The key() function does not work when the context node is the root node of a result tree fragment obtained through exsl:node-set()</li>
+<li>XALANC-623: Compatibility issues with Xerces-C 3.0</li>
+<li>XALANC-621: Selection of compiler definitions file fails on Linux PPC in client code</li>
+<li>XALANC-618: uninstallExternalFunction can run past the end of the array</li>
+<li>XALANC-617: Leak in XalanTransformer</li>
+<li>XALANC-616: xsl:strip-space element doesn't work proprely</li>
+<li>XALANC-615: Xalan resolves a namespace prefix when it should report an error</li>
+<li>XALANC-614: MsgCreator Makefile needs link option</li>
+<li>XALANC-613: Cannot pass value to stylesheet parameter if parameter name is namespace-qualified</li>
+<li>XALANC-609: Template with built-in template rules for namespaces gives and assert</li>
+<li>XALANC-604: ConstructWithNoMemoryManager has a bug which prevents proper default initialization of built-in types.</li>
+<li>XALANC-603: Source does not compile properly on HP-UX with newer versions of the HP compiler</li>
+<li>XALANC-595: EXSLT date-time function missing + or - before timezone offset</li>
+<li>XALANC-588: Floating point exceptions in DoubleSupport::initialize() on Solaris 10 (x86)</li>
+<li>XALANC-570: Removal of compiler warnings from STLHelper.hpp</li>
+<li>XALANC-535: If an error/warning message contains not-displayable character for the local encoding , no message is shown at all</li>
+<li>XALANC-527: Compiling on Xerces-3.0</li>
+<li>XALANC-480: XML1.1 and Namespaces for XML1.1 support</li>
+<li>XALANC-478: Add support for XMLEntityResolver</li>
+<li>XALANC-432: Minor spelling problems in XalanMsg_en_US.xlf</li>
+<li>XALANC-430: "StylesheetExecutionContext::getVariable(name)" crahes if variable "name" was not found.</li>
+<li>XALANC-421: omit-xml-declaration ignored</li>
+<li>XALANC-416: Wrong access to out-of-scope xsl:variable not detected in certain circumstances</li>
+<li>XALANC-415: Encoding attribute is not returning properly in output XML header</li>
+<li>XALANC-413: Crash while using transform method on MacOSX</li>
+<li>XALANC-412: XalanEXSLTDateTime not threadsafe, crashing application</li>
+<li>XALANC-409: compilation error on g++ on SunOS 2.8</li>
+<li>XALANC-408: runConfigure help does not include new HP platform</li>
+<li>XALANC-407: XalanC output format is not suitable as a document entity</li>
+<li>XALANC-376: Result tree fragment attributes are created without proper namespace and local name </li>
+</ul>
+
+
+<a name="bugfix10">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Bugs Fixed in Release 1.10</h3>
+<p>The bugs fixed in the 1.10 release include:</p>
+<ul>
+ <li>XALANC-572: Compile failure on SuSE80AMD_64b_GCC322 </li>
+ <li>XALANC-569: Compile-time assert on 32-bit Solaris and HPUX due to IEEE754 issue </li>
+ <li>XALANC-568: Pattern "/" does not match the pseudo root document of a node-set obtained from a result-tree fragment via exsl:node-set </li>
+ <li>XALANC-511: Crash during XalanTransformer::initialize on AIX </li>
+ <li>XALANC-554: Xalan-C does not implement erratum 25 </li>
+ <li>XALANC-552: Problems with the new serializers with CDATA and unrepresentable or special characters </li>
+ <li>XALANC-558: Latest source code does not build with the Intel compiler on Windows </li>
+ <li>XALANC-555: XalanEXSLTDateTime.cpp has too many platform-specifc ifdefs </li>
+ <li>XALANC-421: omit-xml-declaration ignored </li>
+ <li>XALANC-529: Xalan-C sometimes creates empty text nodes in RTFs or sends empty characters() events to FormatterListeners </li>
+ <li>XALANC-530: Serializers filter attributes unnecessarily </li>
+ <li>XALANC-245: substring-before and substring-after </li>
+ <li>XALANC-115: Need to catch use of variables in xsl:key attributes </li>
+ <li>XALANC-540: XPath absolute location path does not work when the context node was obtained from a result tree fragment through exsl:node-set() </li>
+ <li>XALANC-544: Assert failure, then crash, during "variable undefined" error recovery in certain circumstances. </li>
+ <li>XALANC-543: Crash when calling a template that wrongly uses xsl:with-param instead of xsl:param to declare its parameter. </li>
+ <li>XALANC-539: XalanMap needs to compact buckets to prevent long search times and ever-increasing memory usage. </li>
+ <li>XALANC-542: XalanDocumentFragmentXNodeSetBaseProxy::dereferenced() is not implemented properly </li>
+ <li>XALANC-538: Better handling for non-existent node test </li>
+ <li>XALANC-541: Fixes for zOS build </li>
+ <li>XALANC-455: Problem when releasing InputSource obtained through an EntityResolver </li>
+ <li>XALANC-535: If an error/warning message contains not-displayable character for the local encoding , no message is shown at all </li>
+ <li>XALANC-532: FormatterToXMLUnicode does not serialize UTF-8 </li>
+ <li>XALANC-536: ElemNumber uses extra temporary strings </li>
+ <li>XALANC-537: XalanC source code quotes incorrectly license protected documents </li>
+ <li>XALANC-526: Use of undefined stricmp breaks compilation on Linux </li>
+ <li>XALANC-513: ICUFormatNumberFunctor has some MemoryManager issues </li>
+ <li>XALANC-507: Safety improvements for XalanVector::insert() </li>
+ <li>XALANC-506: Remove references to stlport directory in Makefile.incl.in </li>
+ <li>XALANC-505: DirectoryEnumerator.hpp will not build on Solaris 10 with Sun Workshop 10 </li>
+ <li>XALANC-502: XalanDOMStringCache has initializer list out of order </li>
+ <li>XALANC-501: Creation of comments and PIs needs to detect illegal values </li>
+ <li>XALANC-500: Remove old "diagnostic" output from StylesheetRoot and XSLTEngineImpl </li>
+ <li>XALANC-497: Local variables or parameters in EXSLT-functions are interpreted as global </li>
+ <li>XALANC-496: Glitches in header files </li>
+ <li>XALANC-493: Problem with XALAN_STATIC_CHECK on HP-UX IA64 </li>
+ <li>XALANC-492: Various pluggable memory management bugs. </li>
+ <li>XALANC-490: XalanFileReporter is inconsistent in its usage of pluggable memory management </li>
+ <li>XALANC-489: XalanMemMgrs has a thread-safety issue </li>
+ <li>XALANC-488: XSLTInputSource does not support pluggable memory management </li>
+ <li>XALANC-487: URISupport does not provide explicit MemoryManager </li>
+ <li>XALANC-485: GCC warns about order of members in initializer list </li>
+ <li>XALANC-484: Remove compiler warnings about placement delete for HP's aCC compiler </li>
+ <li>XALANC-483: XercesParserLiaison does not create Xerces-C DOM instances with namespaces support enabled. </li>
+ <li>XALANC-482: Remove compiler warnings </li>
+ <li>XALANC-470: runConfigure does not pass link options to Makefile for AIX platform </li>
+ <li>XALANC-465: Add alt tag to footer.html page under html/apiDocs tree. </li>
+ <li>XALANC-463: Transforming an XML DOM document encapsulated within an XercesDOMWrapperParsedSource object triggers an invalid heap pointer exception if XSL opens other XML document with 'document()' function. </li>
+ <li>XALANC-460: Linux/xlC port </li>
+ <li>XALANC-448: TestXSLT/process.cpp compilation fails, interface broken in FormatterToText.hpp </li>
+ <li>XALANC-445: generate-id() inserts periods into name which limits usage </li>
+</ul>
+
+
+
+<a name="bugs">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>Bug reporting</h3>
+<p>All known Xalan-C++ bugs are listed in <a href="https://issues.apache.org/jira/browse/XALANC">JIRA (the Apache bug database)</a>. For a list of open bugs with links to each bug
+ report, see <a href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+XALANC+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC">XalanC open bugs</a>. If you find a new bug, please enter a XalanC bug report in this
+ database.</p>
+<table class="note">
+<tr>
+<td class="noteImg">
+<img src="resources/note.gif" alt="note" />
+</td>
+<td class="noteTxt">Before you can enter your first bug report,
+ you must submit your email address to
+ <a href="https://issues.apache.org/jira">JIRA</a>
+ and receive a password.
+</td>
+</tr>
+</table>
+<p>We strongly encourage you write patches for problems you find and
+ submit them to JIRA and the
+ <a href="mailto:xalan-dev@xml.apache.org">xalan-dev</a> mailing list.
+ We review the patches we receive to make sure they do not break something else, and (assuming they do not)
+ include them in our next release.
+ In the interest of fixing bugs, adding enhancements, and
+ addressing outstanding design issues, we sincerely want
+ (and need!) your active participation in the ongoing development of Xalan.
+</p>
+
+
+<a name="to-do">‌</a>
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+<h3>To-do tasks for future Xalan-C/C++ releases</h3>
+<p>Open bugs:</p>
+<ul>
+<li>The namespace axis does not return the default "xml" namespace.</li>
+<li>Does not support case-order and lang attributes in xsl:sort.</li>
+</ul>
+<p>Items to do:</p>
+<ul>
+<li>Add support for new specifications (XPath-20, XSLT-2.0)</li>
+<li>Add transcoding support using Xerces-C modules</li>
+<li>Add XSLT extension elements</li>
+<li>Add more EXSLT extension functions</li>
+<li>Add the EXSLT document extension function</li>
+<li>Add support for user-defined extension modules</li>
+<li>Add support for node-set to be declared as top-level XSLT parameter</li>
+</ul>
+
+<p align="right" size="2">
+<a href="#content">(top)</a>
+</p>
+</div>
+<div id="footer">Copyright © 1999-2012 The Apache Software Foundation<br />Apache, Xalan, and the Feather logo are trademarks of The Apache Software Foundation<div class="small">Web Page created on - Fri 06/15/2012</div>
+</div>
+</body>
+</html>
Added: xalan/site/docs/xalan/xalan-c/xalan-c-unixdist.gif
URL: http://svn.apache.org/viewvc/xalan/site/docs/xalan/xalan-c/xalan-c-unixdist.gif?rev=1350856&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/site/docs/xalan/xalan-c/xalan-c-unixdist.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/site/docs/xalan/xalan-c/xerces-icu.gif
URL: http://svn.apache.org/viewvc/xalan/site/docs/xalan/xalan-c/xerces-icu.gif?rev=1350856&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/site/docs/xalan/xalan-c/xerces-icu.gif
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/site/stylebook/Xalan-Logos/Xalan-Logo-8x15-tm.png
URL: http://svn.apache.org/viewvc/xalan/site/stylebook/Xalan-Logos/Xalan-Logo-8x15-tm.png?rev=1350856&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/site/stylebook/Xalan-Logos/Xalan-Logo-8x15-tm.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/site/stylebook/Xalan-Logos/Xalan-Logo-tm.png
URL: http://svn.apache.org/viewvc/xalan/site/stylebook/Xalan-Logos/Xalan-Logo-tm.png?rev=1350856&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/site/stylebook/Xalan-Logos/Xalan-Logo-tm.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/site/stylebook/Xalan-Logos/Xalan-Logo.sdr
URL: http://svn.apache.org/viewvc/xalan/site/stylebook/Xalan-Logos/Xalan-Logo.sdr?rev=1350856&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/site/stylebook/Xalan-Logos/Xalan-Logo.sdr
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/site/stylebook/Xalan-Logos/Xalan-Logo.txt
URL: http://svn.apache.org/viewvc/xalan/site/stylebook/Xalan-Logos/Xalan-Logo.txt?rev=1350856&view=auto
==============================================================================
--- xalan/site/stylebook/Xalan-Logos/Xalan-Logo.txt (added)
+++ xalan/site/stylebook/Xalan-Logos/Xalan-Logo.txt Sat Jun 16 03:57:36 2012
@@ -0,0 +1,85 @@
+
+The XALAN Logo
+
+Graphic: A stylized version of the African Xalam instrument.
+
+
+
+TEXT FONTS SIZE AND STYLE:
+
+TM (trademark)
+
+ Font: Arial
+ Size: 14pt
+ Style: Bold)
+
+XSLT
+
+ Font: Arial
+ Size: 22pt
+ Style: Bold
+
+Apache Software Foundation
+
+ Font: Arial
+ Size: 18pt
+ Style: Bold
+ Note: 2 space characters between words
+
+Xalan (trademark name)
+
+ Font: Segoe Print
+ Size: 48pt
+ Style: Bold
+
+Xalan-C (trademark name)
+
+ Font: Segoe Print
+ Size: 48pt
+ Style: Bold
+
+Xalan-J (trademark name)
+
+ Font: Segoe Print
+ Size: 48pt
+ Style: Bold
+
+
+INSTRUMENT GRAPHIC (vector equations)
+
+ Vertical Width: 0.75 inch (3/4)
+ HorizontalLength: 3.667 inch (3 2/3)
+
+ Oval on the left,
+ neck and butt on the right.
+
+ Oval Width: 0.75 inch (3/4)
+ Oval Length: 1.583 inch (1 7/12)
+
+ Neck Width: 0.167 inch (1/6)
+
+ Butt Width: 0.25 inch (1/4)
+ Butt Length: 0.417 inch (5/12)
+
+
+Description of instrument logo
+
+ Oval: simulation of a gourd sound chamber
+ With orange gradation hues
+
+ Neck: rectangle simulating a round fingerboard
+ With yellow-green gradation hues
+
+ Butt: rounded rectangle simulating end of neck
+ With olive-green hue
+
+ String Anchor: rounded rectangle on the gourd
+ With olive-green hue
+
+ 2 strings: the full length from Anchor to Butt
+
+ 2 strings: tied to neck, at 1/2 length from Anchor to Butt
+
+ 3 Loose Tie Strings on the Butt, simulating tuning anchors
+
+
\ No newline at end of file
Added: xalan/site/stylebook/Xalan-Logos/Xalan-Trademark.txt
URL: http://svn.apache.org/viewvc/xalan/site/stylebook/Xalan-Logos/Xalan-Trademark.txt?rev=1350856&view=auto
==============================================================================
--- xalan/site/stylebook/Xalan-Logos/Xalan-Trademark.txt (added)
+++ xalan/site/stylebook/Xalan-Logos/Xalan-Trademark.txt Sat Jun 16 03:57:36 2012
@@ -0,0 +1,106 @@
+
+The XALAN Logo - Trademark Description
+--------------------------------------
+
+Prepared By:
+
+ Steven J. Hathaway
+
+ (shathaway@apache.org)
+
+ September 3, 2011
+
+
+
+Prepared for:
+
+ The Apache Software Foundation
+
+--------------------------------------
+
+Graphic: A stylized version of the African Xalam instrument.
+
+Note: the difference in spelling.
+
+ Xalam is the African Musical Instrument
+ Xalan is the Apache Xalan Software Project
+
+
+TEXT FONTS SIZE AND STYLE:
+
+TM (trademark symbol)
+
+ Font: Arial
+ Size: 14pt
+ Style: Bold)
+
+XSLT
+
+ Font: Arial
+ Size: 22pt
+ Style: Bold
+
+Apache Software Foundation (trademark name)
+
+ Font: Arial
+ Size: 18pt
+ Style: Bold
+ Note: 2 space characters between words
+
+Xalan (trademark name)
+
+ Font: Segoe Print
+ Size: 48pt
+ Style: Bold
+
+Xalan-C (trademark name)
+
+ Font: Segoe Print
+ Size: 48pt
+ Style: Bold
+
+Xalan-J (trademark name)
+
+ Font: Segoe Print
+ Size: 48pt
+ Style: Bold
+
+
+INSTRUMENT GRAPHIC (vector equations)
+
+ Vertical Width: 0.75 inch (3/4)
+ HorizontalLength: 3.667 inch (3 2/3)
+
+ Oval on the left,
+ neck and butt on the right.
+
+ Oval Width: 0.75 inch (3/4)
+ Oval Length: 1.583 inch (1 7/12)
+
+ Neck Width: 0.167 inch (1/6)
+
+ Butt Width: 0.25 inch (1/4)
+ Butt Length: 0.417 inch (5/12)
+
+
+Description of instrument logo
+
+ Oval: simulation of a gourd sound chamber
+ With orange gradation hues
+
+ Neck: rectangle simulating a round fingerboard
+ With yellow-green gradation hues
+
+ Butt: rounded rectangle simulating end of neck
+ With olive-green hue
+
+ String Anchor: rounded rectangle on the gourd
+ With olive-green hue
+
+ 2 strings: the full length from Anchor to Butt
+
+ 2 strings: tied to neck, at 1/2 length from Anchor to Butt
+
+ 3 Loose Tie Strings on the Butt, simulating tuning anchors
+
+
\ No newline at end of file
Added: xalan/site/stylebook/Xalan-Logos/XalanC-Logo-tm.png
URL: http://svn.apache.org/viewvc/xalan/site/stylebook/Xalan-Logos/XalanC-Logo-tm.png?rev=1350856&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/site/stylebook/Xalan-Logos/XalanC-Logo-tm.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/site/stylebook/Xalan-Logos/XalanC-Logo.sdr
URL: http://svn.apache.org/viewvc/xalan/site/stylebook/Xalan-Logos/XalanC-Logo.sdr?rev=1350856&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/site/stylebook/Xalan-Logos/XalanC-Logo.sdr
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/site/stylebook/Xalan-Logos/XalanC-Logo8x15-tm.png
URL: http://svn.apache.org/viewvc/xalan/site/stylebook/Xalan-Logos/XalanC-Logo8x15-tm.png?rev=1350856&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/site/stylebook/Xalan-Logos/XalanC-Logo8x15-tm.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/site/stylebook/Xalan-Logos/XalanJ-Logo-tm.png
URL: http://svn.apache.org/viewvc/xalan/site/stylebook/Xalan-Logos/XalanJ-Logo-tm.png?rev=1350856&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/site/stylebook/Xalan-Logos/XalanJ-Logo-tm.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/site/stylebook/Xalan-Logos/XalanJ-Logo.sdr
URL: http://svn.apache.org/viewvc/xalan/site/stylebook/Xalan-Logos/XalanJ-Logo.sdr?rev=1350856&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/site/stylebook/Xalan-Logos/XalanJ-Logo.sdr
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xalan/site/stylebook/Xalan-Logos/XalanJ-Logo8x15-tm.png
URL: http://svn.apache.org/viewvc/xalan/site/stylebook/Xalan-Logos/XalanJ-Logo8x15-tm.png?rev=1350856&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xalan/site/stylebook/Xalan-Logos/XalanJ-Logo8x15-tm.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-cvs-help@xml.apache.org