This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 79016 - dynamic language (locale) selection
Summary: dynamic language (locale) selection
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: I18N (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Ralph Ruijs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-24 08:13 UTC by cbulcu
Modified: 2011-11-28 09:21 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cbulcu 2006-06-24 08:13:07 UTC
This one is for "dynamic language selection".

This RFE is related to the new internationalization
support in Matisse, which is great. :-)

The current way of generating the internationalization
code is simply calling java.util.ResourceBundle.getBundle(bundle_path).
This is good for static localization. I mean it just
works regardless the system on which the application is installed. 

BUT. If I want to change the language (localization) in my app,
from a menu containing all supported languages, I can't use that
generated code. An idea would be to generate
java.util.ResourceBundle.getBundle(bundle_path, locale) and add that locale
variable to the list of fields of the current class, and maybe a custom
constructor containing a parameter "locale". You may have a better idea though.
That way I just pass the locale to the JDialog's or JFrame's constructor.

These are just ideas. You are the experts though :-)

Also, because it's related to what I've wrote above, is it possible to generate
that bundle code for existing setText() code (not generated one)? There are
cases where the text of a label is changed on the fly.

Keep it up.