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

CLDR Ticket #8207(accepted)

Opened 4 years ago

Last modified 3 weeks ago

Test 12/24-hour parity in availableFmts items; describe matching algorithm in spec

Reported by: pedberg Owned by: pedberg
Component: other Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:



Follow-on from cldrbug 8002: "12/24h pattern coverage"

Under that ticket, availableFormats items were added to 20 locales for skeletons hmsv, Hmsv, hmv, Hmv, and modern coverage was updated to include these for the next Survey Tool phase to collect data for more locales.

This ticket covers the remaining items from cldrbug 8002: discussion in comment 2 that were not actually completed under that ticket:

  • Spec should describe algorithm for matching requested skeleton to skeletons in data.
  • Should have test of invariant that if we have an availableFormats (and intervalFormats?) item with skeleton for one type of time cycle (12- or 24hour), then we should have an item for the other type of time cycle.
  • Run that test, see how many failures, consult with committee about adding data.


Change History

comment:1 Changed 4 years ago by emmons

  • Owner changed from anybody to pedberg
  • Priority changed from assess to medium
  • Status changed from new to assigned
  • Component changed from test to data-main
  • Milestone changed from UNSCH to 28

comment:2 Changed 4 years ago by markus

  • type set to data

comment:3 Changed 4 years ago by srl

  • Status changed from assigned to accepted

comment:4 Changed 3 years ago by pedberg

  • Milestone changed from 28 to 29

comment:5 Changed 3 years ago by emmons

  • Milestone changed from 29 to upcoming

comment:6 Changed 4 weeks ago by pedberg

  • Milestone changed from upcoming to UNSCH

CLDR 34 BRS closing item, move all upcoming → UNSCH

comment:7 Changed 3 weeks ago by mark

  • Component changed from main to other

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.