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

CLDR Ticket #6614(accepted data)

Opened 4 years ago

Last modified 2 years ago

combined collation rules for bs/hr/sr

Reported by: markus Owned by: markus
Component: collation Data Locale: bs, hr, sr
Phase: rc Review:
Weeks: 0.1 Data Xpath:
Xref:

Description

The Bosnian, Croation and Serbian collation tailorings are script-specific, Latn vs. Cyrl. This seems like a mistake: Since the two scripts are used interchangeably, I think we should use tailorings that apply to both scripts at the same time.

The only issue would be the script reordering. Currently we put either Latn or Cyrl first. We could see if one of the two might be acceptable for both (and maybe preferable, making the language sort the same way regardless of the selected script), otherwise we could follow the <import> of the rules with <settings> to override the reordering.

Attachments

Change History

comment:1 Changed 4 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 25rc

comment:2 Changed 4 years ago by markus

  • Milestone changed from 25rc to 26rc

comment:3 Changed 3 years ago by markus

  • Milestone changed from 26rc to 27rc

comment:4 Changed 3 years ago by markus

  • Phase set to rc
  • Milestone changed from 27rc to 27

comment:5 Changed 3 years ago by markus

  • Milestone changed from 27 to 28

comment:6 Changed 3 years ago by markus

  • Type changed from enhancement to data

comment:7 Changed 3 years ago by srl

  • Status changed from assigned to accepted

comment:8 Changed 3 years ago by markus

  • version 24 deleted

comment:9 Changed 2 years ago by markus

  • Milestone changed from 28 to 29

comment:10 Changed 2 years ago by emmons

  • Milestone changed from 29 to upcoming

Auto move of all 29 -> upcoming

View

Add a comment

Modify Ticket

Action
as accepted
Author


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

 
Note: See TracTickets for help on using tickets.