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

CLDR Ticket #8171(closed: fixed)

Opened 4 years ago

Last modified 4 years ago

Duplicate keys in localeDisplayNames.json

Reported by: Daniel Bruhn <dbruhn@…> Owned by: emmons
Component: json Data Locale:
Phase: final Review: pedberg
Weeks: Data Xpath:
Xref:

Description

For each locale, localeDisplayNames.json has duplicate keys. For example, note the multiple instances of 'numbers' in http://www.unicode.org/repos/cldr-aux/json/26/main/af/localeDisplayNames.json :

        types": {
          "numbers": {
            "arab": "Arabies-Indiese syfers",
            "arabext": "Uitgebreide Arabies-Indiese syfers",
            "armn": "Armeense syfers",
            "armnlow": "Armeense kleinletter-syfers",
            "bali": "bali",
            "beng": "Bengaalse syfers"
          },
          "collation": {
            "big5han": "Tradisionele Chinese sorteervolgorde - Groot5"
          },
          "numbers": {
            "brah": "brah"
          },
          "calendar": {
            "buddhist": "Boeddhistiese kalender"
          },
          "numbers": {
            "cakm": "cakm",
            "cham": "cham"
          },

In fact, most of the keys under 'types' have duplicates.

See also: 5477

Attachments

Change History

comment:1 Changed 4 years ago by emmons

  • Owner changed from anybody to emmons
  • Phase changed from dsub to final
  • Priority changed from assess to major
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 27

comment:2 Changed 4 years ago by emmons

  • Status changed from accepted to reviewing
  • Review set to pedberg

comment:3 follow-up: ↓ 4 Changed 4 years ago by pedberg

I am still seeing duplicate keys in the json repo, checking with John

comment:4 in reply to: ↑ 3 Changed 4 years ago by pedberg

  • Status changed from reviewing to closed
  • Resolution set to fixed

Replying to pedberg:

I am still seeing duplicate keys in the json repo, checking with John

John regenerated the repo, looks good now.

View

Add a comment

Modify Ticket

Action
as closed
Next status will be 'new'
Next status will be 'closed'
Author


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

 
Note: See TracTickets for help on using tickets.