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

CLDR Ticket #5525(closed enhancement: fixed)

Opened 2 years ago

Last modified 13 months ago

Disambiguation of Islamic calendar variants

Reported by: dan.chiba@… Owned by: yoshito
Component: design Version: svn
Load: Data Locale: n/a
Phase: Review: mark
Weeks: Data Xpath:

ldmlBCP47/key/key[@name="ca"]/type]

Xref:

ticket:5726

Description

In calendar.xml CLDR defines "islamic" and "islamicc" for the astronomical and algorithmic variants respectively.

This is a request to consider adding more Islamic calendar variants or enhance the calendar naming scheme to identify the Islamic calendar variants unambiguously.

The background of this request is that JSR-310 must identify the Islamic dates correctly and this requires identifying the specific variants and distinctively identify each of them.

For example, the Umm Al-Qura calendar and Microsoft's Islamic calendar implementation with the Kuwaiti algorithm are both algorithmic but they are different, so the date information is not interchangeable under "islamicc" between different variants. A date in one variant may correspond to a different date in another variant. So, in terms of ensuring correct exchange of Islamic date information, not identifying the precise variants in the CLDR name space falls short of the use case expectation. We anticipate Islamic end users might have their preferred Islamic calendar variant set in their user profile, or an application may be supporting different variants in producing some output with Islamic date information.

One approach to resolve this variant identification problem is appending a subtag to islamicc/islamic; for example:

islamicc-ummalqura  ... Umm al-Qura
islamicc-kuwaiti    ... Kuwaiti variant
islamicc-famouse    ... Famouse variant
islamicc-<tbd>      ... Other calculation based variants, where <tbd> identifies 
                        a rule based variant
islamic-sa          ... Traditional variant for Saudi Arabia, sighting based
islamic-<tbd>       ... Sighting based variant for other countries, where <tbd> 
                        is a standard region subtag.

Attachments

Change History

comment:1 Changed 2 years ago by mark

  • Owner changed from anybody to yoshito
  • Priority changed from assess to major
  • Status changed from new to assigned
  • Component changed from data-bcp47 to design
  • Milestone changed from UNSCH to 23

Tentative plan

Introduce algorithmic calendar variant key cv

-u-ca-islamic-cv-ummalqura
-u-ca-islamic-cv-ccsa
-u-ca-islamic-cv-msku

we would deprecate islamicc in favor of using cv with tags.

comment:2 Changed 2 years ago by dan.chiba@…

JSR-310 adjusted its identification scheme to match the cv key designation and islamicc deprecation.

Summary of the Hijrah calendar variant identification scheme:
https://github.com/ThreeTen/threeten/issues/118#issuecomment-12301195

The only discrepancy between CLDR and JSR-310 is "ummalqura"(CLDR) vs. "uaq"(JSR-310). It is our understanding that the value is constrained to 8 letters. Would it be possible to shorten "ummalqura" to "uaq" to fit in the limit?

comment:3 Changed 2 years ago by yoshito

  • Review set to mark

Final conclusion:

  • New key "cv" for calendar algorithm variants
  • New types
    • umalqura for Umm Al-Qura
    • caltab for Calendrica tabular (arithmetic)
    • mshijri for Microsoft Hijri calendar
    • rgsa for Saudi Arabia visual sighting

comment:4 Changed 2 years ago by yoshito

Created CldrBug:5671 for cleaning up islamic-civil (islamicc).

comment:5 Changed 2 years ago by pedberg

I noticed that the key for Umm Al-Qura calendar is "umalgura" with a 'g' (G), should be "umalqura" with a 'q' (Q). That needs to be fixed.

comment:6 Changed 2 years ago by pedberg

  • Milestone changed from 23 to 23dres

comment:7 Changed 2 years ago by mark

  • Status changed from assigned to closed
  • Xref set to 5726
  • Resolution set to fixed

Filed 5726 to complete this work, since we retracted due to naming issues.

comment:8 Changed 13 months ago by emmons

  • Milestone 23dres deleted

Milestone 23dres deleted

View

Add a comment

Modify Ticket

Action
as closed
The ticket will be disowned. The resolution will be deleted. Next status will be 'new'
Next status will be 'closed'
Author


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

 
Note: See TracTickets for help on using tickets.