Release notes for Xalan-C++ version 1.10
All known Xalan-C++ bugs are listed in JIRA (the Apache bug database). For a list of open bugs with links to each bug
report, see XalanC open bugs. If you find a new bug, please enter a XalanC bug report in this
|Before you can enter your first bug report, you must submit your email address to JIRA and receive a password.|
We strongly encourage you write patches for problems you find and submit them to
email@example.com. 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.
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++.
Please email your comments, questions, suggestions, bug reports, and offers to help to Xalan Development Mailing List.
|Cumulative history of software changes|
The following sections list the changes in each release since Xalan-C++ version 0.40.0.
|Changes for Xalan-C++ version 1.7|
Major updates since version 1.6 include:
- 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
Steps for doing a Build with Message Localization Support.
- 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 Steps for doing a Unix build
- 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.
should be changed to:
- Upgrade from Xerces-C 2.3 to Xerces-C 2.4.
- Porting of ThreadSafe example to UNIX platform.
- Implementation of EXSLT string extension functions encode-uri() and decode-uri().
- Implementation of EXSLT dynamic extension function evaluate().
- Implementation of EXSLT date-time extension function date-time().