Bug 1677090 - The Japanese Era name will be changed on 2019-05-01 / component icu / rhel5
Summary: The Japanese Era name will be changed on 2019-05-01 / component icu / rhel5
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: icu
Version: 5.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Mike FABIAN
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1677091 1677092 1677093 1688570
TreeView+ depends on / blocked
 
Reported: 2019-02-14 02:41 UTC by Christian Horn
Modified: 2021-08-30 12:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1677091 1677092 (view as bug list)
Environment:
Last Closed: 2019-09-24 23:40:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2749651 0 Learn more None Does the change of the Japanese Era affect Red Hat Enterprise Linux? 2019-02-14 02:41:51 UTC

Description Christian Horn 2019-02-14 02:41:52 UTC
Description of problem:
The Japanese Era name will be changed on 2019-05-01 / component icu / rhel5
icu code is referring to the japanese era name.

(snippet from the rhel7 icu code)
 364 void IntlCalendarTest::TestJapanese() {
 365     UDate timeA = Calendar::getNow();
 366     
 367     /* Sorry.. japancal.h is private! */
 368 #define JapaneseCalendar_MEIJI  232
 369 #define JapaneseCalendar_TAISHO 233
 370 #define JapaneseCalendar_SHOWA  234
 371 #define JapaneseCalendar_HEISEI 235
 372     
 373     // BE 2542 == 1999 CE
 374     int32_t data[] = { 
 375         //       Jera         Jyr  Gyear   m             d
 376         JapaneseCalendar_MEIJI, 1, 1868, UCAL_SEPTEMBER, 8,
 377         JapaneseCalendar_MEIJI, 1, 1868, UCAL_SEPTEMBER, 9,
 378         JapaneseCalendar_MEIJI, 2, 1869, UCAL_JUNE, 4,
 379         JapaneseCalendar_MEIJI, 45, 1912, UCAL_JULY, 29,
 380         JapaneseCalendar_TAISHO, 1, 1912, UCAL_JULY, 30,
 381         JapaneseCalendar_TAISHO, 1, 1912, UCAL_AUGUST, 1,
 382         
 383         // new tests (not in java)
 384         JapaneseCalendar_SHOWA,     64,   1989,  UCAL_JANUARY, 7,  // Test current era transition (different code path than others)
 385         JapaneseCalendar_HEISEI,    1,   1989,  UCAL_JANUARY, 8,
 386         JapaneseCalendar_HEISEI,    1,   1989,  UCAL_JANUARY, 9,
 387         JapaneseCalendar_HEISEI,    1,   1989,  UCAL_DECEMBER, 20,
 388         JapaneseCalendar_HEISEI,  15,  2003,  UCAL_MAY, 22,
 389         -1,-1,-1,-1,-1,-1,-1,-1,-1,-1
 390     };

Actual results:
No reference to the upcoming era.

Expected results:
The upcoming era name should properly be dealed with.

Additional info:
- https://en.wikipedia.org/wiki/Japanese_imperial_transition,_2019
- the new era name has not yet been announced.
- We also have to modify glibc (for example bz1555189) and openjdk.

Comment 2 Christian Horn 2019-09-24 23:40:08 UTC
While I had created bugzillas for all the affected components and versions,
so we could collect customer requests on these (as comment or with getting
customer center cases mapped), we did not get requests on this one.
Based on lifecycle, chances to get this fixed are low anyway.
Closing this bz.


Note You need to log in before you can comment on or make changes to this bug.