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

CLDR Ticket #8662(accepted data)

Opened 2 years ago

Last modified 23 months ago

Issue with Character Fallback Substitutions between version 24 and 25

Reported by: roche@… Owned by: pedberg
Component: translit Data Locale:
Phase: rc Review:
Weeks: Data Xpath:
Xref:

Description

There are some differences in character fallback substitutions introduced between version 24 (http://www.unicode.org/cldr/charts/24/supplemental/character_fallback_substitutions.html) and 25 (http://www.unicode.org/cldr/charts/25/supplemental/character_fallback_substitutions.html) ; for example, these two letters have been removed:

0153 œ LATIN SMALL LIGATURE OE Explicit 006F, 0065 oe LATIN SMALL LETTER O, LATIN SMALL LETTER E
0152 ΠLATIN CAPITAL LIGATURE OE Explicit 004F, 0045 OE LATIN CAPITAL LETTER O, LATIN CAPITAL LETTER E

However, they are still listed at:
http://unicode.org/repos/cldr/trunk/common/supplemental/characters.xml

<character value="Œ"><substitute>OE</substitute></character>
<character value="œ"><substitute>oe</substitute></character>

In fact, all "explicit substitutes" derivated from characters.xml (http://unicode.org/repos/cldr/trunk/common/supplemental/characters.xml) appears to be missing.

(see also the discussion in the unicode@… mailing-list)

Attachments

Change History

comment:1 Changed 2 years ago by pedberg

  • Status changed from new to accepted
  • Component changed from unknown to translit
  • Phase changed from dsub to rc
  • Milestone changed from UNSCH to 29
  • Owner changed from anybody to pedberg
  • Type changed from unknown to data

The current direction is to deprecate the character fallbacks and to move relevant character fallback mappings to the transforms (to be handled by the umbrella Any-Latin transform, or the Latin-ASCII transform). There is already another ticket for that, which I will relate to this one.

comment:2 Changed 23 months ago by pedberg

  • Cc mark, sascha added
  • Milestone changed from 29 to upcoming

It is not clear to me what the desired action for this bug is. For the actions described in comment:1 there is supposedly another ticket, but it is not yet added to the Xref field of this one. Moving this one out of 29, since I am not sure what to do with it. Perhaps it should go to Sascha?

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.