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 71153 - Internationalization from the ground up
Summary: Internationalization from the ground up
Status: RESOLVED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
: 32126 (view as bug list)
Depends on:
Blocks: 32121
  Show dependency tree
 
Reported: 2006-01-09 03:42 UTC by _ tboudreau
Modified: 2006-10-23 16:40 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 2006-01-09 03:42:26 UTC 
If I use the I18N module to internationalize a form, or internationalize my 
text w/ the property editor, still new strings I edit inline in the form 
editor will be hardcoded.  If the rest of the UI is internationalized, new 
strings should automatically be also.

(of course this is not so easy with the I18N module separate...)

And if we're going to go that far, why not forget about ever hard-coding 
strings, and just always generate a properties file by default and never 
hardcode strings at all?  Or at least make doing that the default.

Not an easy problem, but the ease of use of the current internationalization 
support is terrible.  Transparent internationalization would have the greatest 
ease of use.
Comment 1 Tomas Pavek 2006-01-09 09:56:33 UTC 
*** Issue 32126 has been marked as a duplicate of this issue. ***
Comment 2 Jan Stola 2006-06-02 12:58:20 UTC 
The support for automatic I18N has been already implemented.
Select the root node of the Inspector and see the I18N section
in the property sheet.