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.
Summary: | Could setting up a new locale use a pointer mechanism instead of a copy of the existing bundle, so, for example, if one has US and UK bundles, strings do not have to be changed twice? | ||
---|---|---|---|
Product: | utilities | Reporter: | _ tboudreau <tboudreau> |
Component: | Properties | Assignee: | issues@utilities <issues> |
Status: | CLOSED WONTFIX | ||
Severity: | enhancement | ||
Priority: | P4 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
_ tboudreau
1999-12-01 02:56:57 UTC
Priority is changed to P4 (normal). Changed to enhancement and decreased priority. If I got the point right. The idea is to make possibility to change locales with same language code together if one was changed in another locale with that language code. This seems to be a bit cumbersome cause it's necessary also to have a possibility to have different values in locales with same language code. Thierefore this could be implemented via option, where default would be "don't link" such locales, but user could change it. Umm, you can have Bundle.properties with some keys (defaults for everything), and Bundle_en.properties (defaults for all English-speaking locales), and Bundle_en_US.properties with just US-specific keys. ResourceBundle automatically merges them in the correct way. Why is any support from the properties module needed? I suggest this be marked WONTFIX unless I am missing something. Jesse is right. It's done automatic by java.util.ResourceBundle (see previous and javadoc for ResourceBundle) by using it the correct way. So I close the issue as WONTFIX. Verified. I agree with Jesse. Resolved for 3.4.x or earlier, no new info since then -> closing. |