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

CLDR Ticket #10190(accepted data)

Opened 3 months ago

Last modified 2 months ago

Belarusian-Latin/BGN transliteration converts to NFD, but rules are in NFC

Reported by: robert@… Owned by: sascha
Component: translit Data Locale:
Phase: rc Review:
Weeks: Data Xpath:


Description (last modified by fredrik) (diff)

The Belarusian-Latin/BGN transliteration converts to NFD before the rules are applied, but the global filter and the rules are written in NFC.
This causes certain letters to transliterate incorrectly e.g. Ў becomes Ŭ when it should be W instead.

(The same problem exists in some other transliterations where NFD conversion is needlessly inserted.)

Furthermore the letter Ш / ш is missing. (It should transliterate to SH / sh.)


Change History

comment:1 Changed 3 months ago by robert@…

Sorry, I just found bug no. 6691 which is about the NFD issue.

The problem of the missing letter Ш / ш remains.

comment:2 Changed 3 months ago by emmons

  • Status changed from new to accepted
  • Priority changed from assess to medium
  • Phase changed from dsub to rc
  • Milestone changed from UNSCH to 32
  • Owner changed from anybody to sascha
  • Type changed from unknown to data

comment:3 Changed 3 months ago by fredrik

  • Xref set to 6691
  • Description modified (diff)

comment:4 Changed 2 months ago by robert@…

There is also a problem with the rule


The source character should be U+02BC (ref. PCGN https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/499636/ROMANIZATION_SYSTEM_FOR_BELARUSIAN.PDF), but in the rule it is U+2019.

The rules provide output prime and double prime as U+02B9 and U+02BA. In the PCGN standards it is clear that single and double quotation marks U+2019 and U+201D are output instead.

Everything else appears to be correct.


Add a comment

Modify Ticket

as accepted

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

Note: See TracTickets for help on using tickets.