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

CLDR Ticket #8651(accepted data)

Opened 3 years ago

Last modified 3 years ago

Please add a Dhivehi collation tailoring to CLDR

Reported by: martin Owned by: emmons
Component: collation Data Locale: dv
Phase: rc Review:
Weeks: 0.2 Data Xpath:

Description (last modified by martin) (diff)

Currently the diacritics are being treated as primary, rather than secondary. This rule should fix the problem:

& [last primary ignorable] << ަ << ާ << ި << ީ << ު << ޫ << ެ << ޭ << ޮ << ޯ
<< ް

Many thanks.

Note: The original rule to ignore the hyphen has now been removed from this request.


Change History

comment:1 Changed 3 years ago by markus

  • Cc srl, emmons added
  • Data Locale set to dv
  • Weeks set to 0.2
  • Phase changed from dsub to rc
  • Description modified (diff)

Is there a reference, or a standard, or a common dictionary, or a phonebook, or... something that we can use to determine that that is the right behavior, as opposed to the DUCET?

What are you intending with the last line of the proposed rules? That's an unbalanced quoting apostrophe, i.e., a syntax error. Are you trying to make the ASCII hyphen-minus ignorable? What does that have to do with Divehi?



Note that, as long as the "main" dv locale data is in "seed" (source:trunk/seed/main/), the collation dv data would also be in "seed". That means that for use in ICU you would have to generate and add this separately.

comment:2 Changed 3 years ago by emmons

  • Owner changed from anybody to emmons
  • Priority changed from assess to medium
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 28

comment:3 Changed 3 years ago by martin

  • Description modified (diff)

comment:4 Changed 3 years ago by markus

  • Cc markus added

comment:5 Changed 3 years ago by emmons

  • Milestone changed from 28 to UNSCH

Per e-mail from Martin: ...

John, Markus,

We have heard back from the linguist. The position regarding what is deemed to be the 'official' Dhivehi collation sequence seems to be rather confused. As per the email below, our linguist is making enquiries to the Dhivehi Language Academy to get clarification on this.

That being the case, I wonder whether the ticket should be changed to Unscheduled? It would seem best not to implement the request until the Language Academy has confirmed that the requested collation order is to be preferred.

JCE: Moving to UNSCH.


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.