[threeten-dev] CLDR Islamic calendar subtag updates

[roger riggs]

Hi Yoshito,

Thank you for the update, it is timely since we will need to stabilize 
the behavior
of the JDK shortly.  I would agree that a single string is more 
convenient for implementations.

With reference to the document:
http://cldr.unicode.org/development/development-process/design-proposals/islamic-calendar-types

1. In the table: "Proposed Calendar Type Value Changes"
     Should there be a row for "islamic-umalqura"? It appears in the xml 
form but not the table.

2. With respect to the simple subtag "islamic",  is an implementation free
      to choose a consistent but arbitrary calendar to identify as "islamic"
      or is it expected that the simple string is not a sufficient 
identifier and is an error?
      (JSR 310 would default to "islamic-umalqura")

3. In Hierarchical Calendar Type Subtags:
     There is mention of a prefix match;  I would assume it only applies
     to matching of complete subtags, not prefixes of arbitrary lengths.
     Also the matching only applies to the lookup of formatting data
     from the calendar type, not of the calendar itself.

4. Is/will the type-subtype syntax be rigorously consistent with BCP47?

Do you have an expectation about when v24 will be finalized?

Thanks, Roger



On 4/16/2013 6:00 PM, yoshito_umaoka at us.ibm.com wrote:
> First of all, sorry for slow update. After CLDR 23 release, we finally had
> chance to discuss about the Islamic calendar subtags in CLDR / Unicode
> locale extension.
>
> There is one major change since I informed our plan in this mailing list.
>
> In the original proposal, we planned to add a new key "cv" for specifying
> calendar algorithm variants. However, some of the CLDR technically
> committee members who are participating CalConnect raised a concern about
> the separation. I think this was also discussed in this list. The CLDR
> TC's latest consensus is to specify the calendar type including small
> algorithm variations by the calendar keyword ("ca") with optional subtags.
> So, "ca-islamic-cv-umalqura" in the previous proposal is changed to
> "ca-islamic-umalqura".
>
> I updated the document -
> http://cldr.unicode.org/development/development-process/design-proposals/islamic-calendar-types
>
> The actual changes in the calendar definition data file with this will be:
>
> <ldmlBCP47>
>      <keyword>
>          <key name="ca" alias="calendar" description="Calendar algorithm
> key">
>              <type name="islamic" description="Islamic calendar"/>
>              <type name="islamic-umalqura" description="Islamic calendar,
> Umm al-Qura" since="24"/>
>              <type name="islamic-tbla" description="Islamic calendar,
> tabular (intercalary years [2,5,7,10,13,16,18,21,24,26,29] Thursday
> epoch)" since="24"/>
>              <type name="islamic-civil" description="Islamic calendar,
> tabular (intercalary years [2,5,7,10,13,16,18,21,24,26,29] Friday epoch)"
> since="24"/>
>              <type name="islamic-rgsa" description="Islamic calendar, Saudi
> Arabia sighting" since="24"/>
>
>              <type name="islamicc" alias="islamic-civil" description="Civil
> (algorithmic) Arabic calendar" deprecated="true"/>
>          </key>
>      </keyword>
> </ldmlBCP47>
>
> Because the threeten-dev community was the original requestor for this,
> I'd like to check with this list before making the change in the CLDR
> repository.
> If you have any major problems with above, please respond to me ASAP.
> We're preparing for opening CLDR survey tool (online tool for collecting
> locale data) for the next major CLDR release. We need to put the new
> subtags into the system soon.
>
> Thanks,
> Yoshito
>
>