Release notes for Xalan-C++ version 1.0
| |
| |
Open bugs:
- Problems mapping namespaces from the stylesheet to the source document, and elements do not inherit namespaces correctly
- <xsl:copy-of ...> within an attribute element does not include CRLFs (if any) in the result.
- If you use <xsl:output method="HTML"> to generate HTML with a <HEAD> element, the <HEAD> element fails to include a <META> tag (with the encoding).
- <xsl:number> does not support letter-value="traditional" for "classical" Greek numbering.
- Unable to sort in reverse document order based on position.
- Does not support six or more digits of numerical precision after the decimal.
- <xsl:fallback> within a top-level function is not recognized and does not throw an error.
- The document() function generates a syntax error if called in the following manner: document(string,/).
- Problems using key() in match patterns to find descendants. For example, key('mykey','Introduction')//p finds all p elements, not just those that match the criteria.
- The id() function doesn't work in some complex match patterns.
- In some cases, output a single CDATA section in multiple single-character CDATA sections.
- Minor problems outputting whitespace characters.
|
|
| |
| |
If you want to rebuild Xalan-C++ (to produce a debug build, for example), you need the following:
- The Xalan-C++ source files
- The Xerces-C++ header and (for Windows) .lib files
- (Optional) The ICU header and (for Windows) .lib files
The Xalan-C++ source files are in the distribution.
The required Xerces-C++ files are in the Xerces-C++ binary distributions.
For information on using the International Components for Unicode (ICU), see
Using the ICU.
 | If you are not rebuilding with the ICU, you do not need the ICU header or .lib files. |
To rebuild the Windows32 release, use the Microsoft Visual C++ 6.0 project files. To rebuild
the Linux or AIX release, use the make file in the root of the source directory. The builds look
for Xerces-C++ and ICU in directories parallel to the
xml-xalan directory.
|
| |
Important We have set up the Visual C++ projects and the Linux and AIX make files to look for Xerces in a directory structure that results from downloading xml-xerces/c from the Apache XML CVS repository and building with the Visual C++ project files or the Linux make file. This structure parallels the Xalan-C++ source tree and build structure.
If you are using a Xerces-C++ binary distribution, you must either modify the Xalan-C++ project files or makefile, or rearrange the build directory structure as indicated in the following illustration.
For Linux and AIX, the XERCESROOT environment variable points to the Xerces-C root directory. For Windows, the Xerces-C root directory must be named xml-xerces, and it must be at the same level as the Xalan-C++ root directory. For all environments, the ICU root directory must be named icu, and it must be at the same level as the Xalan-C++ root directory.
 | Keep in mind that at any given point in time the Xalan-C++ and Xerces-C++ source trees in the Apache XML repository may not be consistent. When we release a version of Xalan-C++ we certify that it is compatible with a given release of Xerces-C++. To be safe, stick with distributions that we certify to be compatible. Reminder: Xalan-C++ version 1.0 is compatible with Xerces-C++ version 1.3.0.
Xalan-C++ version 1.0 has been tested with International Components for Unicode(ICU) 1.6 source files. You may be able to use newer ICU releases as they appear. |
|
 |  |  |  | Steps for doing a Windows build |  |  |  |  |
| |
- Rearrange the Xerces-C++ binary distribution as indicated above so the headers are in
the xml-xerces/c/src tree and xml-xerces is at the same level as the xml-xerces root
directory.
- (Optional) If you are rebuilding the ICUBridge, install the ICU so the icu root directory
is at the same level as the xml-xerces root directory (see Using the ICU.
If you want TestXSLT to use ICU support for number formatting and sorting, install the ICU,
uncomment the #define XALAN_USE_ICU statement in process.cpp, and use the Visual C++
Project Dependencies command to add ICUBridge to the list of TestXSLT dependencies (see Enabling ICU support for TestXSLT).
- Use Visual C++ to open the Xalan workspace from the xml-xalan\c\Projects\Win32\VC6.
- Select Project Dependencies and check
- Use Visual C++ to rebuild everything or specific dynamic link libraries and executables of
interest.
|
 |  |  |  | Steps for doing a Linux or AIX build |  |  |  |  |
| |
- Rearrange the Xerces-C++ binary distribution as indicated above so the headers are in the
xerces-c_x_y_z-platform/c/src tree, and set the XERCESCROOT environment variable
to the complete path to xerces-c_x_y_z-platform.
- Set the XALANCROOT environment variable to the complete path to the root of the Xalan-C++
distribution.
- AIX only: Download STLport and set the STLPORTROOT environment
variable to the complete path to the STLPort distribution.
(This step is not required for Linux because The Linux GNU compiler includes the STL (Standard Template
Library.)
- (Optional) If you are including the ICUBridge, install the ICU (see Using the ICU) and use the shell to define XALAN_USE_ICU.
If you are using Bourne Shell, K Shell, or Bash:
export XALAN_USE_ICU "1"
If you are using C Shell:
setenv XALAN_USE_ICU="1"
- Change directory to xml-xalan/c/src in the Xalan-C++ distribution.
- Use the chmod +x command to set the executable flags for conf* and
runConfigure.
chmod +x runConfigure
chmod +x conf*
- Run the runConfigure utility with at least the platform flag (Linux) or the platform, C compilier, and C++ compiler flags (AIX) as indicated below.
Linux: runConfigure -p linux
AIX: runConfigure -p aix -c xlc_r -x xlC_r
To see the other runConfigure flags you may include, use the help flag:
runConfigure -h
- Purge the previous build:
make clean
- Run the new build:
make
or
make targ
where targ is ommitted or is all (rebuild all), lib (the XSLT libary), or
TestXSLT (the TestSXSLT executable). ICUBridge is included in the build of TestXSLT if XALAN_USE_ICU is
defined.
 | The command you use for setting environment variables depends on the shell you are
using.
For Bourne Shell, K Shell, or Bash use export ENVAR "val"
For C Shell, use setenv ENVAR="val"
where ENVAR is the environment variable name and val is the environment variable
setting. You can check the setting of an environment variable with echo $ENVAR |
|
|
| |
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.
|
|