> On 12/5/2011 5:46 PM, shath...@e-z.net wrote: >> When building the Xalan-C 1.11 sources in SVN repository for ICU >> support, >> should we also link with the Xerces-C 3.1.1 parser library that is >> compiled with ICU support? > We should simply remove the old AllInOneWithICU project files. Here's > how the ICU integration works with Xalan: > > AllInOneWithICU -- uses the ICU for message loading, collation and > support for the format-number() function. > > AllInOne -- uses the ICU for collation and support for the > format-number() function when one of the ".. with ICU" configurations is > selected. > > Someone would need to re-write how we use the ICU for message loading as > the way we were doing it was deprecated and is no longer supported. I > don't think this is very worthwhile since the only advantage to the ICU > message loading over any of the others is that it allows multiple > languages in a single resource file. I can't imagine a practical use > case where Xalan operates in multiple languages in a single invocation, > so it seems like ICU message loading is overkill. > > Dave > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org > For additional commands, e-mail: xalan-dev-h...@xml.apache.org > > Thanks Dave,
Examining the Windows build structure for XalanC-1.11, the AllInOneWithICU project (XalanICU.sln Solution) seems to be broken! The AllInOne project (Xalan.sln Solution) has limited support for ICU, but I have been unable at this time to do any testing. I don't currently have a platform that uses IBM-ICU libraries. I am wondering how well the Xerces_C (parser) with ICU integrates into the Xalan-C (XSLT) platform. Your comments are appreciated. Sincerely, Steven J. Hathaway - Xalan Documentation Project --------------------------------------------------------------------- To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org For additional commands, e-mail: xalan-dev-h...@xml.apache.org
