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 4826 - 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?
Summary: Could setting up a new locale use a pointer mechanism instead of a copy of th...
Status: CLOSED WONTFIX
Alias: None
Product: utilities
Classification: Unclassified
Component: Properties (show other bugs)
Version: 3.x
Hardware: All All
: P4 enhancement (vote)
Assignee: issues@utilities
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1999-12-01 02:56 UTC by _ tboudreau
Modified: 2003-07-01 14:20 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ tboudreau 1999-12-01 02:56:57 UTC 
PROBLEM: Love the resource bundle module.

However, if you set up an alternate
locale under one of these, it does a
copy of all your defined strings, so
that the new locale has a copy of
them.

In our case, we are using en_US as
our default locale, so almost all the
strings will be the same in the en_UK
locale. However, as this copy has been

made, if I want to change a String in
both locales, I must change it twice.

Better behaviour would be for the
en_UK locale to use the deafult
*unless* I have specified a different
string (so a pointer mechanism
rather than a copy mechanism).
Comment 1 Marek Grummich 2000-07-25 09:08:59 UTC 
Priority is changed to P4 (normal).
Comment 2 Peter Zavadsky 2001-01-16 10:58:59 UTC 
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.
Comment 3 Jesse Glick 2001-03-26 16:29:14 UTC 
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.
Comment 4 Peter Zavadsky 2001-03-27 08:02:49 UTC 
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.
Comment 5 pfelenda 2002-10-18 09:29:45 UTC 
Verified. I agree with Jesse.
Comment 6 Quality Engineering 2003-07-01 14:20:15 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.