|
From: Andy H. <an...@jt...> - 2001-08-20 23:04:20
|
The Xerces Message Loader is used to obtain the text error messages for =
the errors that can occur withing Xerces (mostly parsing error =
messages.) There are several message loader implementations. InMem is =
the simplest, but has no ability to support translated error messages. =
For supporting multiple languages, there are a native Win32 loader (from =
resource files), a UNIXy MsgCatalog loader, and an ICU based one that =
sounds like it's not in good shape.
Probably the thing to do for now is to use one of the others xerces =
message loaders.
Andy Heninger
IBM, Cupertino, CA
hen...@us...
----- Original Message -----=20
From: Stockett, Jeff=20
To: 'ic...@ww...'=20
Sent: Friday, August 17, 2001 3:51 PM
Subject: RE: ICUMsgLoader.cpp: Compile error
Hi Andy,
After finally getting ICU 1.8.1 to build properly on Solaris, I have =
moved on to
XercesC 1.5.1. Unfortunately, the ICUMsgLoader.cpp problem brought up
by HangJun yesterday still exist in XercesC 1.5.1 (the most recent =
stable=20
release).
How does the packageBinaries.pl script fix the problem, if the source =
is
fundamentally broken? [I already checked the equivalent XML4C package
from alphaWorks in hopes that it would have an updated =
ICUMsgLoader.cpp
file, but it is the same.]
I realize we should probably be asking these questions on the =
xercesc-dev
mailing list, but after reviewing the archives there, and seeing the =
question
asked many times with no proper answer, I'm somewhat at a loss.
Is the problem that we should should use "inmem" rather than "icu" for =
the
-m message loader option, and only use "icu" for the -t transcoder =
flags to
runConfigure. This seems to work but I don't know what the =
consequences
of -minmem versus -micu actually are.
Thanks, Jeff
-----Original Message-----
From: Andy Heninger [mailto:an...@jt...]
Sent: Thursday, August 16, 2001 11:43 AM
To: ic...@ww...
Subject: Re: ICUMsgLoader.cpp: Compile error
I don't remember the state of the ICU based message loader in xerces =
1.1, but I don't think it was working. You might look at more recent =
versions of xerces to see if the code is better, or try asking on the =
xerces-c-dev mail list.
Andy Heninger
IBM, Cupertino, CA
hen...@us...
----- Original Message -----=20
From: HangJun=20
To: ic...@ww...=20
Sent: Thursday, August 16, 2001 2:05 AM
Subject: ICUMsgLoader.cpp: Compile error
When compiling the source of Xerces-C =
1.1.0,ICUMsgLoader.cpp
failed,says that "tmpPath" is not defined(see below)
// =
-------------------------------------------------------------------------=
--
// Public Constructors and Destructor
// =
-------------------------------------------------------------------------=
--
ICUMsgLoader::ICUMsgLoader(const XMLCh* const toLoad) :
fBundle(0)
, fBundleType((XMLCh*)toLoad)
{
// Ok, lets try to create the bundle now
UErrorCode err =3D U_ZERO_ERROR;
fBundle =3D new ResourceBundle(tmpPath, err);
********** =20
if (!U_SUCCESS(err))
{
// <TBD> Need to panic again here?
}
}
and i can't find any place definning it, is it a problem,and has =
this problem
fixed?
Any help and suggestions are appericated, thanks in advance!
|