![[Unicode]](http://www.unicode.org/webscripts/logo60s2.gif){kind=small}
Modify ↓
CLDR Ticket #7060(accepted unittest)
Add test that collation starred relations only contain NFD-inert characters
| Reported by: | pedberg | Owned by: | markus |
|---|---|---|---|
| Component: | collation | Data Locale: | |
| Phase: | rc | Review: | |
| Weeks: | Data Xpath: | ||
| Xref: |
Description
Follow-on to cldrbug 6738: which established the policy that collation starred relations should only contain NFD-inert characters and fixed the data accordingly; we should add a test for this.
Attachments
Change History
comment:2 Changed 3 years ago by emmons
- Owner changed from anybody to markus
- Priority changed from assess to medium
- Status changed from new to assigned
- Milestone changed from UNSCH to 26dsub
comment:4 Changed 3 years ago by emmons
- Milestone changed from 26dsub to 26dvet
Moving all 26dsub to 26dvet. Please assess the need to complete tickets by 26dvet, which is 2014-06-19
comment:8 Changed 2 years ago by markus
- Type changed from task to unittest
- Component changed from test to collation
comment:11 Changed 22 months ago by emmons
- Milestone changed from 29 to upcoming
Auto move of all 29 -> upcoming
Note: See
TracTickets for help on using
tickets.
The easiest would be to iterate over all tailorings, extract the rule strings (you can leave the white space and comments in but need to unescape \u and \U etc.), and try to build a RuleBasedCollator for each one. If it throws an exception, then something is wrong :-)