It’s better. It picks up a spanish VASSAL properties file in my home dir and offers spanish as a language preference on the ‘jump right in’ screen. (I don’t know Spanish, just using it as an example)
But the workflow doesn’t really make sense for module translations where the language is not one of the ‘Big 5’.
- Imagine I have a Spanish computer and start playing vassal with no Spanish VASSAL translation. Everything is in English, Ok I cope with that.
My friend sends me an English module that has a Spanish translation.
What do I expect to happen? Well, since my XP locality is set to Spanish, I would expect to load up the module and see the Spanish translation.
What actually happens? I load up the Spanish module and I see English??? I have to then go to Edit Preferences, change my preferred language from English to Spanish (which was not on the list before loading the module), save the preferences, quit out of Vassal, restart Vassal, play the module.
If my Locality is language X/country Y and I load a module that includes a translation for X or X/Y, then the translation process should be automatic and transparent, regardless of what the preferred current language is. I have already specified my preference in the XP Regional control panel, why do I have to tell Vassal as well?
- Country specific module translations does not seem to work either. Try creating a new module with a Spanish/Spain translation instead of a Spanish/ translation. It does not get picked.
It looks like you are only generating and saving Language level locales into the preferences, Resouces locale and setting them as the Java locale, so this line
countryBundle = languageBundle + “_” + Resources.getLocale().getCountry();
in Localization() can never load a country bundle.
University of Western Sydney
Messages mailing list
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)