Hi all ! I am thinking about design of message localization . Apparently , Xalan need a similar system, like has Xerces for the last 3 years. Xerces implements 3 types of local messages : "inMemory", "Resource file string" for Win32 and with ICU service. Actually, there exists 4th , "Message Catalog" but I'm still trying to activate it. I'd be happy to know your opinions about next issues: 1. Do we really need an implementation of "resourceString" for Win32 in parallel with "inMemory" ? Those message services are very similar. 2. If an user uses Xalan as dll (.so) it seems to be a problem to find a message file on the disk. For this purpose Xerces requires in run time an environmental variable, XERCESROOT to be defined . Does it mean, that we moving toward creating an installation procedure for Xalan? 3. Xerces has a great utility: a small program, that given xml file with all system messages for specific localization, creates .hpp and other files, used during compilation of all project. Should we start to collect utilities for Xalan too? Thanks for your responses Dmitry
