Xerces C++: Since some platforms are senstive to the order in which message sets are added to a message catalog file (i.e. they want them to be in order), I made some small changes to the NLSXlat program that spits out the various message formats. The formatter for the message catalog format now also spits out a small header file XMLMsgCat_Ids.hpp, that holds some constants which have the set ids that were used to generate the .Msg file. This will allow the msgcat loader to not to have to have hard coded numbers and allows the formatter for the msgcat format to just spit them out with a sequential id that it just bumps up for each set that it has to pump out. I've checked these files in, which Arundhati requested, and she will update the message catalog loader to use these new ids instead of hard coded numbers. So, if you check out now before she does this, you might get incorrect messages from the message loader. She will hopefully do this change today since it should be quite simple to do. The current contents of the new hpp file is: const unsigned int CatId_XML4CErrs = 1; const unsigned int CatId_XML4CValid = 2; const unsigned int CatId_XML4CExcepts = 3; and the new .msg file is now checked in with the message sets in this order. ---------------------------------------- Dean Roddey Software Weenie IBM Center for Java Technology - Silicon Valley [EMAIL PROTECTED]
