On 6/22/06, Tom Morris <[EMAIL PROTECTED]> wrote:
I definitely agree. The code is also tagged with a similar "todo". This is really ugly... but I don't know of a "clean" way to recognize every available locale from the bundles. Consider also that Argo could be only partially translated for a language.
Anyway, even reading the files from a property would be an improvement.
Regards, Andrea
> I'll also have to open a defect for a Translator.java
> patch, as long as the locales are statically loaded..
This is definitely broken. Please file a bug report. There's no reason
ArgoUML should know what languages it's been translated into. It should
even be possible to add languages after a release has been completed.
I definitely agree. The code is also tagged with a similar "todo". This is really ugly... but I don't know of a "clean" way to recognize every available locale from the bundles. Consider also that Argo could be only partially translated for a language.
Anyway, even reading the files from a property would be an improvement.
Regards, Andrea
