Mike Pogue wrote,
> So, in other words, the Xerces-C.DLL, ICU-C.DLL, and
> ICU_CONVERTER_DATA.DLL will all end up in the same directory, and the OS
> will find them without an environment variable hint (or, you can
> separate them, and put them on PATH or LIBPATH). No environment
> variables (e.g. ICU_DATA) are required, and so you can have more than
> one copy of Xerces and ICU on your system (identical copies or not), and
> they don't get mixed up. Installation will also be much simpler (you
> don't have to register the DLL's at install time).
>
> Oh, also, I think they retained ICU_DATA as a compile option, if you
> really want to still do it that way...I'm not sure about this,
> though...Do you think they should retain the environment variable
> (ICU_DATA) way, too?
I believe that ICU plans to have a build time option that switches
between converter data in DLLs and normal data (.cnv) files. If the
normal file approach is used, ICU_DATA (or an equivalent) environment
variable will be available for specifying where the files are located.
But I hope that the DLL approach will become the norm, that the
environment variables are history, and that we can throw away all
of the existing platform-dependent code that searches for converter
files by locating the ICU DLL at runtime.
-- Andy
