David Hubbard wrote:
Hi Dave,
I want to go back to the problem with XalanVector.hpp. However one of
the steps I have to
take is to use the ICU. I tried converting icu 3.2.1 to vs 2005 but
there are several unresolved
externals.
This is a known bug with VS2005 and how it converts the project files, as
it loses the dependencies. You can go into the dependencies and update
them pretty easily.
How much effort would it take to upgrade xalan to icu 3.8.1.
I'm not sure. It's a bit of a gnarly problem with the build process, which
is also gnarly in and of itself.
I would be happy to volunteer.
Well, you could review the comments I've made on postings from Ashley Zink
and Michael Ellery. I believe it has to do with the fact that we put a "_"
character in our resource name and also that we put a relative path into
the temporary file XalanMessages_1_10_en_US.lst during the build process.
Dave
