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

CLDR Ticket #9353(accepted tools)

Opened 2 years ago

Last modified 13 months ago

Logical groups for flexible date formats

Reported by: mark Owned by: emmons
Component: datetime Data Locale:
Phase: rc Review:
Weeks: Data Xpath:


  1. We should ensure that when we have dateFormatItem id=X, then we have intervalFormatItem id=X, and vice versa, so that we are sure that they are in sync. This is only the core formats: y+ M+ E+ d+ h+ m+ s+
  1. We should have finer-grained groups for the date formats. That way we don't need to have ALL of the dateFormatItems or intervalItems present when just one is changed. But we will ensure that we have all of them that share at least two fields. For it is the relation between two fields that causes mis-syncs.

Basically two paths are in the same group when their keys overlap by two fields


  • in same group

<dateFormatItem id="Ehms">E h:mm:ss a</dateFormatItem>
<intervalFormatItem id="Hm">...

  • in different group

<dateFormatItem id="Ehms">E h:mm:ss a</dateFormatItem>
<dateFormatItem id="MMMd">MMM d</dateFormatItem>

For the stock formats, use the imputed field

<timeFormatLength type="full">...<pattern>h:mm:ss a z</pattern>

=> id="hmsz"

(All of this is taking alternate forms into account, like H~h)


Change History

comment:1 Changed 2 years ago by emmons

  • Status changed from new to accepted
  • Component changed from unknown to datetime
  • Priority changed from assess to major
  • Phase changed from dsub to rc
  • Milestone changed from UNSCH to upcoming
  • Owner changed from anybody to emmons
  • Type changed from unknown to tools

comment:2 Changed 13 months ago by emmons

  • Milestone changed from upcoming to UNSCH

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.