David, I mistyped. I indeed meant XALAN_USE_ICU_MSG_LOADER. I _do_ want XALAN_USE_ICU, but I'm wondering if using XALAN_ICU_MSG_LOADER is Going to cause me to have to supply my own message files (similarly to XERCES_ICU_MSG_LOADER, which I don't want to have to do. If I _don't_ have to do that using the default stuff in the XalanICU.dsw, then well and good. See, I tried changing XALAN_INMEM_MSG_LOADER Using that same workspace/project(s), and had trouble at the end stage link. As for the VC6 workspaces themselves, I'm not really having any trouble with them, since VC7 converts them just fine.
Am I making sense? *chuckle* Rich Stephens Software Developer Optio Software, Inc. Windward Fairways II 3015 Windward Plaza Alpharetta, GA 30005 (770) 576-3561 [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, February 26, 2004 4:40 PM To: [email protected] Subject: RE: Xalan with/without ICU message loader? Hi Rich, You should probably use the latest CVS code, as there are Visual Studio.NET project files that I created. You should have no problem using Xalan with its default message library configuration, which uses a DLL or shared library, not the ICU. As far as the string "XALAN_USE_ICU_TRANSCODER" is concerned -- I can't find that anywhere. Did you mean XALAN_USE_ICU or XALAN_ICU_MSG_LOADER? Dave |---------+-----------------------------> | | Rich Stephens | | | <[EMAIL PROTECTED]| | | ftware.com> | | | | | | 02/26/2004 12:56 | | | PM | | | Please respond to | | | xalan-c-users | |---------+-----------------------------> >--------------------------------------------------------------------------- ----------------------------------------| | | | To: "'[email protected]'" <[email protected]> | | cc: (bcc: David N Bertoni/Cambridge/IBM) | | Subject: RE: Xalan with/without ICU message loader? | >--------------------------------------------------------------------------- ----------------------------------------| I am attempting to build Xalan C++ with MSVC 7. I have already built ICU and Xerces, specifically with the XERCES_USE_ICU_TRANSCODER and XERCES_USE_INMEM_MESSAGELOADER options. I used the INMEM messageloader option because I don't have a need for multi-locale messages from the parser, and don't want to have to supply them myself. The VC6 workspace defines XALAN_USE_ICU_TRANSCODER -- Is this option going to require me to supply my own message lib? If so, I want to build Xalan using the ICU transcoder and the ICU bridge for numeric processing, but NOT the ICU messageloader. Any help as to how to build the Xalan libs in VC7 this way, or whether I even need to, would be appreciated. Rich Stephens Software Developer Optio Software, Inc. Windward Fairways II 3015 Windward Plaza Alpharetta, GA 30005 (770) 576-3561 [EMAIL PROTECTED]
