[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search
 
Modify

CLDR Ticket #7963(accepted data)

Opened 2 years ago

Last modified 18 months ago

Invalid date of the start of Einin Era

Reported by: YOCKOW <for_net_services@…> Owned by: pedberg
Component: supplemental Data Locale:
Phase: rc Review:
Weeks: Data Xpath: /supplementalData/calendarData/calendar[@type="japanese"]/eras/era[@type="141"]
Xref:

Description

Line 4267 in /common/supplemental/supplementalData.xml of v26 is:
<era type="141" start="1293-8-55"/>

Maybe it's a kind of typo, but Einin Era commenced on 5th August in Shō'ō 6 (6th September 1293 in the Julian calendar).

Therefore, valid description is below:
<era type="141" start="1293-8-5"/>


Yet if the Julian calendar is preferred, the line must be
<era type="141" start="1293-9-6"/>
AND other lines in calendar data of the Japanese calendar must be modified.

Attachments

Change History

comment:1 Changed 2 years ago by emmons

  • Owner changed from anybody to pedberg
  • Phase changed from dsub to rc
  • Priority changed from assess to medium
  • Status changed from new to assigned
  • Milestone changed from UNSCH to 27

comment:2 Changed 2 years ago by pedberg

  • Cc yoshito added

Resolve julian vs proleptic gregorian issues for these date specs. Switch to ISO 8601 format too.

Also note, early Japanese calendar eras were based on lunar calendar, the current data may not make sense.

comment:3 Changed 2 years ago by pedberg

  • Milestone changed from 27 to 28

comment:4 Changed 2 years ago by markus

  • Type set to data

comment:5 Changed 2 years ago by srl

  • Status changed from assigned to accepted

comment:6 Changed 23 months ago by markus

  • version 26 deleted

comment:7 Changed 19 months ago by pedberg

  • Milestone changed from 28 to 29

Out of time, look at early in 29 if possible

comment:8 Changed 18 months ago by emmons

  • Milestone changed from 29 to upcoming
View

Add a comment

Modify Ticket

Action
as accepted
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.