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

CLDR Ticket #10416(accepted)

Opened 18 months ago

Last modified 3 months ago

Conflicting definitions of 12/24 hour preference

Reported by: c960657-unicode.org@… Owned by: pedberg
Component: docs-spec Data Locale:
Phase: spec-beta Review:
Weeks: Data Xpath:


The spec seems to contradict itself on how to determine the locale’s preference for 12-hour versus 24-hour clock.

Part 2, section 2.5 references the <hours preferred=“…”> element:

The preference of 12 hour versus 24 hour for the locale can be derived from the Time Data. If the hour symbol is "h" or "K" then the format is 12 hour; otherwise it is 24 hour.

Part 2, section 2.6.2 references the <timeFormatLength type="short"> element:

[…] the locale's actual preference for 12-hour or 24-hour time cycle is determined from the hour character used in the locale's standard short time format

Section 2.5 was changed in http://unicode.org/cldr/trac/changeset/11418. I assume section 2.6.2 should be changed accordingly.


Change History

comment:1 Changed 15 months ago by mark

  • Owner changed from anybody to pedberg
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 32

comment:2 Changed 14 months ago by pedberg

  • Milestone changed from 32 to 33

comment:3 Changed 10 months ago by pedberg

  • Phase changed from dsub to spec-beta

comment:4 Changed 9 months ago by pedberg

The key issues is whether the hour cycle preference is fundamentally based on language or region. What should it be for de_US, for example?

In any case we should handle this consistently.

comment:5 Changed 9 months ago by zbraniecki@…

What should it be for de_US, for example?

Mozilla's position is that it is part of the regional preferences and as such should stick to the region.

If the user of the US region wants a different hour cycle that is a manual override of this particular settings.

Language defines things like word for April or Thursday, region defines things like date pattern, hour cycle, first day of the week and so on.

comment:6 Changed 9 months ago by fredrik

Just to add a data point, as a Swedish expat in the US, I still keep and prefer 24-hour clock on my devices. (I do find it practical to have miles and Fahrenheit set rather than km and Celsius, as it makes a clear reference to other local info.)

comment:7 Changed 9 months ago by pedberg

  • Priority changed from assess to major
  • Milestone changed from 33 to 34

Some discussion in TC 2018-03-07. Need bigger discussion on this. Pref is definitely a combination of lang & region. May need to change the current supplemental structure and it hierarchy. Using short date to get pref prevents consideration of day periods since we don't use those in short formats (?), that may be a problem. Need also to consider locales for which we have specific data, vs ones for which we don't.

comment:8 Changed 3 months ago by pedberg

  • Milestone changed from 34 to 35

comment:9 Changed 7 weeks ago by mark

  • Component changed from datetime to docs-spec

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.