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 94734 - I18N - conversion/validation messages appear in English because jsf-ri-1.2.jar is not localized
Summary: I18N - conversion/validation messages appear in English because jsf-ri-1.2.ja...
Status: VERIFIED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Mark Dey
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2007-02-06 19:56 UTC by bugbridge
Modified: 2007-05-30 17:34 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2007-02-06 19:56:36 UTC
Original status: 1-Dispatched; Suggested Status: NEW

These items should be added to the Keywords: I18N

Description:
Tested build: NB5.5 ML RC1 + VWP Build 061127_7

1. Run the IDE in ja locale
2. Create a Java EE 5 project
3. When doing similar steps in the tutorial "Using Converters",
   the following error message from converter is displayed in English.
   Please see the attached snapshot.

       '1000' could not be understood as a currency value.

       Validation Error: Specified attribute is not between the expected value
       of -237.15 and 1,000.

I found that this message comes from rave2.0/modules/ext/jsf-ri-1.2.jar.

  javax/faces/Messages.properties
  javax.faces.converter.NumberConverter.CURRENCY={2}: ''{0}'' could not be
understood as a currency value.

However, the localized files for ja, zh_CN and pt_BR are not included in this jar.

When we discussed translation of JSF for pt_BR, I heard that the only
jsf-impl.jar needed
to be localized, but localization for jsf-impl.jar and jsf-ri-1.2.jar needs.

AS team should be translating jsf-ri-1.2.jar, so if there are localized files,
please add them to jsf-ri-1.2.jar.
Comment 1 ohsumi 2007-03-29 03:12:10 UTC
As described in CR: 6498945, this problem was fixed in VWP 5.5,
so I close this report.
Comment 2 Ken Frank 2007-05-30 17:34:44 UTC
v.