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

CLDR Ticket #9931(accepted)

Opened 2 years ago

Last modified 3 months ago

Resolve differences between CLDR and Unihan

Reported by: mark Owned by: pedberg
Component: collation Data Locale:
Phase: rc Review:
Weeks: Data Xpath:
Xref:

Description

We would like to use stock kMandarin and kTotalStrokes, where possible.

We are almost there, but there are the following 2 differences. Note: these do not include the extra mappings that we have for non-Unified-Ideographs.

kMandarinOverride.txt
#Code 'Best' Value # Char kMandarin
# the format is like Unihan, with “kMandarin” being the field, and the value being a possible replacement for what is there.
U+5452 kPinyinOverride FU3 # 呒 wǔ

kMandarinAdditions.txt
#Code 'Best' Value # Char
# the format is like Unihan, with “kMandarin” being the field, and the value being a possible replacement for what is there.
U+2B5B8 kMandarin YUAN4 # 𫖸

kTotalStrokesAdditions.txt
(none)

kTotalStrokesOverride.txt
(none)

Attachments

Change History

comment:1 Changed 10 months ago by pedberg

  • Status changed from new to accepted
  • Component changed from unknown to collation
  • Phase changed from dsub to rc
  • Milestone changed from UNSCH to 34
  • Owner changed from anybody to pedberg
  • type changed from unknown to data

comment:2 Changed 10 months ago by pedberg

  • Priority changed from assess to medium

comment:3 Changed 3 months ago by pedberg

  • Milestone changed from 34 to 35
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.