On Thu, 2006-12-21 at 17:51 -0800, Thomas Russ wrote: > At a more fundamental level, though, internationalization > for Vassal is a bit tougher to realize, since > most of the actual text you would encounter > comes from the modules rather than the engine > itself. I don't think it would be nearly as > useful to have the main menu items, say, in > French and then all of the reports from the > pieces in English.
The ResourceBundle example I sent before includes a hint at a possible solution: The key names in the properties files include namespaces. Replace myapp.Prompt1 with moduleName.whatever. I am sure there would be a set of keys that were the same module to module, relating to certain traits? If the module loader finds a properties file, add it as a specific module bundle, provided the keys are properly named in a module namespace or something. The ListResourcesBundle class can get you the ability to find what keys are in the bundles, as lists of String-Object pairs. > Now, that could be handled by resource files as > well, but managing that would require some more > work on the editor code in Vassal so that strings > would be stored in resource files with the > appropriate locale encoding. And module namespace keynames and such. All sounds about right. -- Exile In Paradise Serving coffee on aircraft causes turbulence.
