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 - some messages/labels in bundle files not clear if to be lcoalized | ||
---|---|---|---|
Product: | javaee | Reporter: | Ken Frank <kfrank> |
Component: | Code | Assignee: | Martin Grebac <mgrebac> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | jf4jbug |
Priority: | P2 | Keywords: | I18N |
Version: | 4.x | ||
Hardware: | Sun | ||
OS: | SunOS | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Ken Frank
2005-02-08 05:52:26 UTC
As for 1) - refactoring; you're right that strings that do not contain any other text than just text enclosed with <> should not be translated. Others should be. Should I mark them somehow? How? As for 2) - I removed unused labels (those starting with FMT_...) - bundles starting with OPT_ should be translated, they are shown in tag file wizard - also bundles with ### should be translated, those are generated as comments to listener (when you create listener from wizard) for item 1 - can they be removed from bundle and just handled in code ? If not, then each line needs to have a #NOI18N comment before it or, if all of these can be grouped into one section, and that section clearly marked with some delimiters and #NOI18N and #DO NOT TRANSLATE this section for the values that start with ###, I suggest a comment saying to make sure that no translation happens until after the ###; it may be obvious but it can't hurt, since the lines will end up in some code or script. ken.frank@sun.com It's better to have these strings in bundles, so I created marked section. Fixed in trunk. as to the comment of the ### comments for the TXT_DOC keys, suggest changing comment to something like ###Start translation after the \#\#\# for each of the TXT_DOC keys below since these messages will be inserted into the code All items in this issue have been verified. |