changing the language related properties at runtime has no effect on switching
to the appropriate localization bundle, but changing the system local does.
I would like to change localization at runtime without changing setting of the os.
I think this is related to being able to test out ones localized bundles ?
I think java command has locale argument, so wonder if there might be
project properties argument that could be used already ?
Also, since some external processes might depend on the system locale for
how they view the locale, the sense of locale for them will not
be affected by this ( just as starting netbeans using --locale argument might
not apply to them)
Pardon my ignorance, but I don't have a clue what you are trying to describe. Is
not there a special component/subcomponent for I18N things? I know almost
nothing about I18N so I probably can't help you.
Please reassing to proper people (I admit I don't know who is it) and describe
use cases, current NetBeans behaviour, desired behaviour exactly and in details,
thank you. I wonder if something like I feel this is is even implementable?
Again pardon my ignorance but this is how it is...
I'll change it to properties component; there is properties and i18n components
and are related.
(i18n component is not for all things about i18n at all, but about the features in
netbeans that provide user facilities to more easily create and manage bundle files.
You can add required locales as options for VM. In 6.0 you can setup several
launch configuration, each with different languages, and then just select one
configuration to start you application.
To do this just open project properties, go to Run tab, create new run
configuration and add something like this "-Duser.language=de -Duser.country=DE"
as VM options.