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

CLDR Ticket #10989(accepted)

Opened 9 months ago

Last modified 4 weeks ago

Fix the Core data page and coverageLevel

Reported by: mark Owned by: mark
Component: other-supplemental Data Locale:
Phase: dvet Review:
Weeks: Data Xpath:
Xref:

Description

I was looking at the following to answer someone's question about creating a new locale.

http://cldr.unicode.org/index/cldr-spec/minimaldata

  1. That page is a bit out of date.

For example, the "minimal data commitment" corresponds to the "basic" level instead of the (former) "minimal" level.

  1. It is not in alignment with the coverage level, however. I think we should change the coverageLevel and/or the information in that page to align. For one thing, that lets us mechanically test whether people are meeting their commitments. It also lets us have more meaningful charts.

I have a proposed disposition at

https://docs.google.com/spreadsheets/d/1hCMYTfVxmzCLcUogmna7bcO61JlyiIfyMDNXKowEzJk/edit?usp=sharing

  1. Once we have that alignment, we can add some samples of data to http://cldr.unicode.org/index/cldr-spec/minimaldata

Attachments

Change History

comment:1 Changed 9 months ago by mark

  • Owner changed from anybody to mark
  • Priority changed from assess to major
  • type changed from unknown to data
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 34

comment:2 Changed 7 months ago by mark

  • Phase changed from dsub to rc

comment:3 Changed 4 months ago by mark

  • Phase changed from rc to dsub
  • Milestone changed from 34 to 35

comment:4 Changed 5 weeks ago by mark

  • Component changed from unknown to locale-create

comment:5 Changed 4 weeks ago by mark

  • Component changed from locale-create to other-supplemental

comment:6 Changed 4 weeks ago by mark

  • Phase changed from dsub to dvet

Moving to dvet, because this is more targeted at new locales

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.