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

CLDR Ticket #8893(accepted tools)

Opened 20 months ago

Last modified 8 days ago

Synchronize bs and bs_Cyrl

Reported by: mark Owned by: emmons
Component: util Data Locale:
Phase: rc Review:
Weeks: Data Xpath:
Xref:

Description

These should be almost identical. When transliterating languages in the former Yugoslavia, they are determinant when going from Cyrl to Latn, and almost determinant from Latn to Cyrl. There are only a few cases where there is a possible issue:

<tRule>Љ} $lower → Lj ; # CYRILLIC CAPITAL LETTER LJE</tRule>
<tRule>Љ → LJ ; # CYRILLIC CAPITAL LETTER LJE</tRule>
<tRule>љ → lj ; # CYRILLIC SMALL LETTER LJE</tRule>
<tRule>Њ} $lower → Nj ; # CYRILLIC CAPITAL LETTER NJE</tRule>
<tRule>Њ → NJ ; # CYRILLIC CAPITAL LETTER NJE</tRule>
<tRule>њ → nj ; # CYRILLIC SMALL LETTER NJE</tRule>
<tRule>Џ} $lower → Dž ; # CYRILLIC CAPITAL LETTER SHA</tRule>
<tRule>Џ → DŽ ; # CYRILLIC CAPITAL LETTER SHA</tRule>
<tRule>џ → dž ; # CYRILLIC SMALL LETTER SHA</tRule>

So only where one happened to have a sequence of, say, "l" + "j" that didn't mean љ that there would be a problem.

Options.

  1. generate bs_Cyrl from bs, like we do for sr, but have a (very short) list of exceptions for where the lj/nj/dž are not right.
  2. prefill bs_Cyrl from bs. That is, always offer cyrillic(bs) as option.
  3. have a test that bs_Cyrl and bs are consistent.

Attachments

Change History

comment:1 Changed 19 months ago by emmons

  • Status changed from new to accepted
  • Component changed from unknown to util
  • Priority changed from assess to major
  • Phase changed from dsub to rc
  • Milestone changed from UNSCH to 29
  • Owner changed from anybody to emmons
  • Type changed from unknown to tools

comment:2 Changed 18 months ago by emmons

  • Milestone changed from 29 to upcoming

Auto move of all 29 -> upcoming

comment:3 Changed 8 days ago by emmons

  • Milestone changed from upcoming to UNSCH
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.