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: | //NOI18n comments are not added to code which should not be internationalized | ||
---|---|---|---|
Product: | guibuilder | Reporter: | Jana Maleckova <janie> |
Component: | Code | Assignee: | issues@guibuilder <issues> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jana Maleckova
2008-07-08 15:51:04 UTC
True, but for whatever reason, doing any change in the form afterwards, or changing the text itself when checking the "Do not..." checkbox will fix the generated code. I was just thinking about situation when I want to internationalize string (via i18n wizard - Tools -> Internationalize)in some custom method which is in a scope of form class but don't want to internationalize string of some swing component (placed in guarded blocks) from whatever reason. But workaround is simple, just skip the string in wizard which should not be internationalized or to switch auto i18n on in form and appropriate comments are automatically set. P4 accepted. But IMHO, scenario described above is handy as well. My point was that the missing NOI18N comment gets fixed once you do one more change in the form - whatever change to regenerate code. That's how it behaves now. So it is very unlikely you'll have a missing NOI18N in the end - unless setting the "Do not..." checkbox is the very last thing you do in the form - and even then it will be missing only for this one property. |