> 1) Do i have to build ICU sources, if i want to use Number formatting ONLY? > > Note: Documentation reference from apache site > " Enabling ICU support for number formatting and sorting > 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++"
That's a documentation bug. It should say: "If you only want to use the ICU to support number formatting and sorting, you do not need to integrate the ICU with Xerces-C++." The previous paragraph explains that you can rebuild Xerces-C++ with ICU integration to use the ICU for transcoding. > 2) Do i have to set ICUROOT env variable, if i have to build Xalan sources > with ICU support, apart from setting XALAN_USE_ICU? The ICUROOT environment variable is for the ICU itself, regardless of whether or not you're using it with Xalan. See the ICU documentation for more information. Xalan will also use the ICUROOT to find the header files. > Because, assuming that i dont need to build ICU, if i go ahead and build > Xalan, it gives me the following error > > "ICUBridge/ICUBridge.cpp", line 71: Error: Could not open include file > <unicode/coll.h>. > "ICUBridge/ICUBridge.cpp", line 72: Error: Could not open include file > <unicode/dcfmtsym.h>. > "ICUBridge/ICUBridge.cpp", line 73: Error: Could not open include file > <unicode/decimfmt.h>. If you're building on a Unix-based platform, installing the ICU copies the ICU header to /usr/local/include. If you then set ICUROOT to that path and build Xalan, the compiler will find the header files, and the linker will find the shared libraries. If you're building on Windows, then you will need to build the ICU in a directory that is at the same level as the Xerces and Xalan directories. This is explained on the same page you're quoting. Dave
