JDK-8004278 : Add localized generic time zone names to JRE locale resources
  • Type: Enhancement
  • Component: globalization
  • Sub-Component: translation
  • Affected Version: 8
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2012-12-03
  • Updated: 2013-11-05
  • Resolved: 2013-10-09
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Related Reports
Duplicate :  
Relates :  
Generic time zone names are supported by java.util.spi.TimeZoneNameProvider. Generic names need to be added to JRE locale resources. It won't be simple copy and paste from CLDR resources due to some different naming convention. Localized generic names need to match corresponding standard and daylight saving time names.
Closing as it's a dup.

This is being taken care of as part of JDK-8025051

It was skipped in message drop10, 20 and 30. To be included in message drop40 in 8/22, the file either needs to be in a supported format, or an intermediate file (say .properties format) for translation needs to be created.

We have translation drop scheduled for 1/30. But if the file is not in a format WPTG can handle, it will be skipped...

An example of the different naming conventions is that the long standard name for America/Los_Angeles in CLDR ja locale means "������������������������������" (America Pacific Standard Time). Its JRE name is "������������������" (no "America").