Filing an Issue for localized NetBeans

Localization issues

NetBeans 6.0 Localization Bug Dashboard

A localization issue can either be one of the problems listed below, or a  request for enhancement:

1. Incorrect translation or incorrect terminology is being used
2. The translated string is not comprehensible or does not properly navigate the users' operation
3. The English message is displayed instead of a translated one
   
4. The localized product does not work properly, while the English version does function properly. Or, the product behavior seems to be buggy, but it is not clear if this is caused by the translation.

From #1 to #3, most issues are caused by the translated Resource Bundle (Bundle.properties or other resource files). However, it's difficult to detect issues like #4 because you may be not sure if the reported problem is also caused in the English version. To make it clear, the product behavior in both localized and English versions needs to be verified.  Save the evaluator time by validating both English and localized versions. In any case, whether you are able to validate it in English or not, submit the issues. As described below, the evaluator will verify your submitted report. Please submit if you think you are seeing any issues in the localized NetBeans products. Your feedback is always welcome!!

Guideline to select component when filing a localization issue

• When you find any issues like above #1, #2, and #3, submit your bug report on translatedfiles component.
• When you are not sure if the the reported issue is caused by the translation (like #4 above), file your bug report on translatedfiles component first. The evaluator will change the component when the reported issue is not related to the  translation.
• When you are sure the issue being reported is impacts both the translated product and English version, submit issues to the appropriate categories. For example, when you are facing buggy behavior in the IDE's build system, file your bug report under the ant or ide component.

Before reporting bugs

1. Register and log in to Issuezilla
2. Search issues already reported by using Quick links, Query page, or Open localization issues
3. Be sure you've reproduced the issue by using the latest version
4. Enter a new issue as described in Steps to report a bug
   

Steps to report a bug

1. Go to Enter Issue page
2. Select Component "translatedfiles"
3. Select Sub Component "localization", "code", "documentation" or "www" as described below.
4. Select another field as described at The Meaning of Issues Fields
5. Write Summary and Description and follow The Rules to Report New Issue"
6. Click "Submit issue"
7. Click submitted bug report ID in the page, to go back to submitted bug report page again.
8. Enter language name in "Status whiteboard" as described under Fields to be used for localization issues
9. Click "Submit" again

Fields to be used for localization issues

When you file an issue on translatedfiles component, we have following guide lines for some fields.

Subcomponent

Select Subcomponents as follows:

Value	Description
code	Generic product behavior, not sure if it's caused by translation
documentation	Online-help or other documentation embedded in the product
localization	Localization issue like above #1, #2 and #3
www	All web contents in the http://translatedfiles.netbeans.org/

Description

Refer to the The Rules to Report New Issue, and add feature name or product area (e.g. debugger, visual editor for Swing application) in your description.

Status whiteboard

Status whiteboard field is not displayed when entering a new issue, it's displayed only when updating issues already filed. Enter the language name in this field. For example, when you find an incorrect translated message in the Japanese localized IDE, enter 'japanese' (small letter).

Please use one of the following language names. It's important for the language team to agree to use the same language name, so that it is easy to query and search for bugs.

Language name in the Issuezilla	Description
albanian	Albanian
azerbaijani	Azerbaijani
s.chinese	Simplified Chinese
czech	Czech
dutch	Dutch
french	French
german	German
italian	Italian
japanese	Japanese
korean	Korean
b.portuguese	Brazilian Portuguese
russian	Russian
spanish	Spanish
swedish	Swedish

Attachment

For localization issues, a screen shot can be very helpful for the evaluator. Consider attaching the screen image (GIF, JPEG or PNG are preferred), to make a bug report clear. Add a description when you attach the screen shot.