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

CLDR Ticket #9748(accepted data)

Opened 12 months ago

Last modified 6 months ago

Update Kurdish (ku) seed collation

Reported by: rkaldari@… Owned by: markus
Component: collation Data Locale: ku
Phase: rc Review:
Weeks: 0.1 Data Xpath:


The Wikimedia Foundation (in consultation with native Kurdish speakers) would like to propose the following collation data for Kurdish (ku):

[reorder Latn Arab]

# These tailorings are based on the Universal Kurdish Alphabet which
# seeks to accomodate all three major dialects of Kurdish: Northern
# Kurdish (Kurmanji), Central Kurdish (Sorani), and Southern Kurdish
# (Pehlewani).

# Primary differences for Kurmanji letters:

# Primary differences for Sorani and Pehlewani letters:

# The following glyphs are not officially part of the Kurdish Alphabet,
# but are sometimes used to represent distinct "non-Kurdish" sounds in
# Kurdish writing.

# "Éé Íí Úú Ùù" are alternative forms that are used in the Yekgirtú
# variant of the Kurdish-Latin alphabet.


Change History

comment:1 follow-up: ↓ 2 Changed 11 months ago by pedberg

  • Status changed from new to accepted
  • Cc mark, markus, pedberg added
  • Priority changed from assess to major
  • Phase changed from dsub to rc
  • Milestone changed from UNSCH to 31
  • Owner changed from anybody to markus

Currently we have "ku" as a locale in seed, and "ckb" as a locale in main; we do not treat "ku" as the parent of "ckb". We may need to add collation data for these separately. May need some discussion on this.

comment:2 in reply to: ↑ 1 Changed 11 months ago by markus

  • Weeks set to 0.1

Replying to pedberg:

we do not treat "ku" as the parent of "ckb"

And we shouldn't -- ku defaults to Latn, ckb defaults to Arab.

We may need to add collation data for these separately. May need some discussion on this.

We have separate collation data, see source:trunk/seed/collation/ku.xml

This ticket requests an update of the ku seed collation data. This seems reasonable and uncontroversial. When I have time, I will propose merging what we have with this new data.

comment:3 Changed 11 months ago by pedberg

Thanks for investigating, I did not have a chance to look into this in detail before assigning

comment:4 Changed 6 months ago by markus

  • Milestone changed from 31 to 32

Add a comment

Modify Ticket

as accepted

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

Note: See TracTickets for help on using tickets.