JDK-8209175 : Handle 'B' character introduced in CLDR 33 JDK update for Burmese (my) locale
- Type: Bug
- Component: core-libs
- Sub-Component: java.util:i18n
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2018-08-09
- Updated: 2020-06-17
- Resolved: 2019-02-26
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.
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 13 |
|---|
13 b10Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
CLDR 32 onwards, B character has been added in date time patterns for Burmese locale(my and my_MM). However, java.text.SimpleDateFormat and in java.time.format.DateTimeFormatter do not support same. To provide full support for 'B' character in the date-time APIs can be put on hold until a strong need arise, but a workaround should be added to handle 'B' character in CLDR data. The LDML specification of 'B' character (day period) suggest that "if translation data is missing for a particular variable dayPeriod in the locale���s language and script, formatting should fall back to using the am/pm values" http://unicode.org/reports/tr35/tr35-dates.html#dayPeriods So a workaround could be added while processing CLDR data where 'B' character fall back to 'a' character.