JDK-8217366 : ZoneStrings are not populated for all the Locales
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 11,13
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-01-18
  • Updated: 2019-10-04
  • Resolved: 2019-01-23
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.
JDK 11 JDK 13
11.0.5-oracleFixed 13 b06Fixed
Related Reports
Relates :  
JDK-8218948 - SimpleDateFormat :: format - Zone Names are not reflected correctly during run time
Relates :  
JDK-8220037 - Inconsistencies of generated timezone files between Windows and Linux
Description
It's observed that only the Zone strings for the Locale "en" OR "en_US" are populated, for other Locales zone strings are not populated.
Comments
Fix request (11u): Requesting backport for consistency with Oracle 11.0.5. Patch applies cleanly and will be tested at SAP.
04-07-2019
Confirmed that passing the no inheritance marker to dfs.getZoneStrings() is the only issue that is causing failures in JCK's SimpleDateFormat tests in non en/en_US locales.
19-01-2019
There are short names filled with "no inheritance marker" (3 consecutive U+2205), which should be converted to GMT format.
18-01-2019