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

CLDR Ticket #5915(closed task: fixed)

Opened 5 years ago

Last modified 5 years ago

each collation rule works on the current state of the tailoring

Reported by: markus Owned by: markus
Component: xxx-spec Data Locale:
Phase: Review: emmons
Weeks: 0.2 Data Xpath:


I presented the following to the "collation subcommittee". Unless they disagree, I will clarify the spec accordingly. I will update this ticket according to replies from the "subcommittee" (on cc here).

I believe the intention is that, logically, each rule works on the current state of the tailoring, including the effects of preceding rules but excluding the effects of following rules.


The LDML spec seems to have the clearest expression of that: "Since resets always work on the existing state, the rule entries must be in the proper order. A character or sequence may occur multiple times; each subsequent occurrence causes a different change."

As a consequence,

&a < u < v < w &ov < x &b < v

should yield the order

oa, ou, x, ow, ob, ov

In particular, the second CE of x should be between u and w.


Change History

comment:1 Changed 5 years ago by emmons

  • Owner changed from anybody to markus
  • Status changed from new to assigned
  • Milestone changed from UNSCH to 24final

comment:2 Changed 5 years ago by markus

  • Status changed from assigned to accepted
  • Review set to emmons

Fixed with ticket:5909 r9304.

comment:3 Changed 5 years ago by emmons

  • Status changed from accepted to closed
  • Resolution set to fixed

Add a comment

Modify Ticket

as closed
Next status will be 'new'
Next status will be 'closed'

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

Note: See TracTickets for help on using tickets.