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

CLDR Ticket #9847(reviewing data)

Opened 8 months ago

Last modified 5 weeks ago

Add yue_Hans locale

Reported by: pedberg Owned by: pedberg
Component: main Data Locale:
Phase: dsub Review: mark
Weeks: Data Xpath:
Xref:

ticket:10124

ticket:10204

ticket:10205

Description

Can probably generate from yue [_Hant], just as we generate sr_Latn from sr [_Cyrl]

Attachments

Change History

comment:1 Changed 7 months ago by emmons

  • Status changed from new to accepted
  • Priority changed from assess to medium
  • Phase changed from dsub to rc
  • Milestone changed from UNSCH to 31
  • Owner changed from anybody to pedberg
  • Type changed from data to tools

comment:2 Changed 7 months ago by mark

Should change the tool slightly.

If the target is empty, transform source
if the target is not, replace if the source changed from the previous version of the source.

comment:3 Changed 4 months ago by pedberg

  • Phase changed from rc to dvet

comment:4 Changed 4 months ago by pedberg

  • Cc mark added

Uses tool tools/java/org/unicode/cldr/tool/CLDRFileTransformer.java

Probably want to add another option to enum PolicyIfExisting {RETAIN, DISCARD, MINIMIZE} for the new behavior.

Do we have access to the previous value of the source? We need something like input.getStringValueForPreviousVersion(xpath);

comment:5 Changed 3 months ago by pedberg

  • Phase changed from dvet to dsub
  • Milestone changed from 31 to 32

comment:6 Changed 5 weeks ago by pedberg

  • Status changed from accepted to reviewing
  • Xref set to 10124 10204 10205
  • Cc emmons added
  • Component changed from unknown to main
  • Priority changed from medium to major
  • Type changed from tools to data
  • Review set to mark

OK, the updates to CLDRFileTransformer.java that will be needed starting at the end of CLDR 32 are now split out into a separate ticket cldrbug 10204: . This ticket covers only the initial addition of the yue_Hans locale, based on transformation from yue_Hant using the Traditional-Simplified transform. This proceeded as follows:

  1. Update CLDRFileTransformer.java to generate yue_Hans from yue[_Hant] using the Traditional-Simplified transform. This generated two files:
    • main/yue_Hans.xml
    • rbnf/yue_Hans.xml
  2. Update main/yue_Hans.xml with selected overrides as follows (based on some discussion with language experts):
    • For the main exemplars, use a set generated by converting the characters in the yue_Hant main exemplars using the Traditional-Simplified transform (this is not just conversion of the text representation of the set; it entails converting each of the characters in the ranges, and then forming new ranges based on the result)
    • For the aux exemplars, start with a set generated by converting the characters in the yue_Hant aux exemplars using the Traditional-Simplified transform, as above. Then remove from that set characters that duplicate ones in the main exemplars, and add simplified characters that are used in the yue_Hans generated data but not present in the exemplar set.
    • For the index and punctuation exemplars, just copy from zh[_Hans_CN]
    • For number systems, number symbols and formats, copy from zh[_Hans_CN]
    • For currency symbols for CNY and JPY, copy from zh[_Hans_CN]
    • For date formats, copy from zh[_Hans_CN], but retain the date symbols (e.g. era and month names) transformed from yue_Hant
  3. Add empty locales for the following
    • yue_Hans_CN
    • yue_Hant
    • yue_Hant_HK
  4. Remove the empty locale for yue_HK, which is replaced by the newly added yue_Hant_HK
  5. Update the default content locales, adding yue_Hans_CN, and replacing yue_HK with yue_Hant and yue_Hant_HK

Note that support for yue collation is covered by a separate ticket cldrbug 10124:

I have also filed cldrbug 10205: to update the languagePopulation data for yue in CN to reflect that it is mostly yue_Hans.

View

Add a comment

Modify Ticket

Action
as reviewing
Author


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

 
Note: See TracTickets for help on using tickets.