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

CLDR Ticket #9964(new data)

Opened 3 months ago

Move Norther Kurdish (ku/ku_latn/kmr) out of seed

Reported by: federicoleva@… Owned by: anybody
Component: main Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:


#9748, #9460, #9913 contain data that we need added to CLDR for the MediaWiki locale "ku"/"ku-latn". I just added a trusted vetter for ku who is ready to translate all language names etc.

I understand that to add data we first of all need to move ku out of seed. Seeing http://www.unicode.org/repos/cldr/trunk/seed/main/ku.xml , I'll specify below what data is ok and what needs to be added or changed, following the format of http://cldr.unicode.org/index/cldr-spec/minimaldata/form . Then I'll ask our Kurdish translator to correct any mistake.

  1. Administrative / Locale Identifier

0.a) Requester's Name and Email address: Federico Leva and Ghybu

0.b) Locale name: Kurdish (Northern Kurdish/Kurmancî)

0.c) Locale identifier(s):

ku, ku_Latn, ku_TR, kmr

  1. Exemplar Sets

1.a) Main:

as is [see example: https://ku.wikipedia.org/wiki/W%C3%AEk%C3%AEpediya )

1.b) Auxiliary:

<exemplarCharacters type="auxiliary">[á à ă â å ä ã ā æ é è ĕ ë ē í ì ĭ ï ī ñ ó ò ŏ ô ø ō œ ß ú ù ŭ ū ÿ]</exemplarCharacters>

1.c) Index:

as is

1.d) Punctuation:

<exemplarCharacters type="punctuation">[\- ‐ – — , ; \: ! ? . … ' ‘ ’ " “ ” ( ) \[ \] § @ * / \& # † ‡ ′ ″]</exemplarCharacters>

  1. Orientation

2.a) Characters: LTR

2.b) Lines: top-to-bottom

  1. Plural Rules

3.a) What are the plural rules for this language?

Same group as "tr" and "ckb".

  1. Country Data and Default Content

4.a) Is the data in http://www.unicode.org/cldr/charts/latest/supplemental/language_territory_information.html correct for the language and territory?


4.b) What should the default content locale be for the language?

ku_TR / ku_Latn

  1. Romanization: –



Add a comment

Modify Ticket

as new

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

Note: See TracTickets for help on using tickets.