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: | I18N - Enable to i18n properties and property editors | ||
---|---|---|---|
Product: | guibuilder | Reporter: | Tomas Pavek <tpavek> |
Component: | Code | Assignee: | issues@guibuilder <issues> |
Status: | NEW --- | ||
Severity: | blocker | Keywords: | I18N |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Tomas Pavek
2001-06-01 08:44:42 UTC
Can this be raised in priority as the more items that can be translated the better for those who will use a localized product ? I don't know alot about this area, but could it be viewed really as a bug that these items are not able to be localized ? ken.frank@sun.com I think it's up to author of the bean to provide localized names and tooltips. Since this is not done for Swing components in JDK (as far as I know), we can provide some alternative in the IDE to do it... But you can hardly say it's our bug. And generally speaking, it is not possible to localize everything around beans this way, we can just hack the "well known" beans like Swing, AWT... Pls give more reason why this is so important. Target milestone -> 3.3.1. Set target milestone to TBD Set target milestone to TBD *** Issue 28768 has been marked as a duplicate of this issue. *** Changing target milestone to future. *** Issue 74570 has been marked as a duplicate of this issue. *** |