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

CLDR Ticket #6009(closed task: fixed)

Opened 5 years ago

Last modified 4 years ago

Change coverage for time formats

Reported by: mark Owned by: pedberg
Component: survey Data Locale:
Phase: Review: emmons
Weeks: Data Xpath:


paths for time formats should be suppressed except in Gregorian. (see #5986)


Change History

comment:1 Changed 5 years ago by pedberg

  • Status changed from new to accepted
  • Component changed from unknown to survey
  • Priority changed from assess to major
  • Milestone changed from UNSCH to 24dsub2
  • Owner changed from anybody to pedberg
  • Type changed from unknown to task

comment:2 Changed 5 years ago by pedberg

  • Review set to emmons

The standard time formats already only appeared in Gregorian, so the changes needed were for availableFormats and intervalFormats items. In coverageLevels.xml:

  • Split %timeFormatItems out of %dateFormatItems and updated both - for example, %dateFormatItems had EEEd and yQ which we do not use at all, and lacked EEEE entries important in CJK locales; %timeFormatItems lacked the E(H|h)ms? items.
  • For gregorian only , added coverage for the %timeFormatItems (they are removed from other calendars due to the split)
  • Delete the level-80 availableFormats catchall for generic calendar, would pick up the times items, and it is no longer necessary with the %dateFormatItems update
  • Split %intervalFormatItems into %intervalFormatDateItems and %intervalFormatTimeItems; %intervalFormatTimeItems is only used with gregorian, %intervalFormatDateItems is used with gregorian and generic (as %intervalFormatItems formerly was).

comment:3 Changed 5 years ago by emmons

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

comment:4 Changed 4 years ago by emmons

  • Milestone 24dsub2 deleted

Milestone 24dsub2 deleted


Add a comment

Modify Ticket

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

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

Note: See TracTickets for help on using tickets.