On Fri, 27 Aug 2010 11:26:40 -0700, David Bertoni <dbert...@apache.org> wrote: > I have been very busy with work and life, so it's been hard to > contribute like I did when IBM was essentially paying me to work on > Xalan-C.
I can absolutely understand that. > It would be great if some poeple out there who need things to > get moving would help out. I understand that, too. However, my employer wouldn't be happy with me working office-hours to support a third-party dependency - and in my free time, I'd like to work on things unrelated to my work. > I think you'll find the trunk of the SVN repository is up-to-date and > more stable than 1.10. That is usually (and in my case) not an option. I am sure you can imagine the seven kinds of hell you'd get dragged through for using an *unreleased* "development version" of a third-party dependency... > As for using the ICU, the only thing that's broken is using the ICU as > the message loader. You can certainly use ICU integration for everything > else. This can be accomplished by using the -t icu -m inmen option for > runConfigure on the Unix/Linux platforms, and by using the Xalan.dsw > Visual Studio projects and building the "Debug with ICU" or "Release > with ICU" options. There is no added value to using the ICU as the > localization option, since there are no localizations for the Xalan-C > messages, and the only advantage to using the ICU message bundles are > multiple languages in a single message shared library/DLL. Thanks for the info, I will try that. (Nevertheless, it would look very good to have a newer release of Xalan out.) > As for doing a Xalan-C release, the actual knowledge of how to do that > has been lost with people leaving the project... I feel your pain. No, really. Maintaining stuff others have abandoned isn't fun. (I've been doing it for a decade...) Regards, -- Martin Baute so...@rootdirectory.de
