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

CLDR Ticket #3500(closed defect: fixed)

Opened 8 years ago

Last modified 4 years ago

weekData/minDays and weekData/firstDay

Reported by: yoshito Owned by: yoshito
Component: main Data Locale:
Phase: Review: pedberg
Weeks: Data Xpath:










cldrbug:1968 changed minDays value to 4 for all territories.

          <minDays count="4" territories="001" />

          <!-- Note, this firstDay is for the first day of the week in a calendar page view. -->
          <!-- The first workday of the week (after the weekend) is distinct, and can be determined as the day after the weekendEnd day.  -->
          <!-- Currently there is no separate information for the first day of the week in local day-of-week numbering, this is inferred from firstDay.  -->
          <firstDay day="mon"  territories="001" />
          <firstDay day="fri"  territories="MV" />
          <firstDay day="sat"  territories="AE AF BH DJ DZ EG ER ET IQ IR JO KE KW LY MA OM QA SA SD SO SY TN YE" />
          <firstDay day="sun"  territories="AR AS AZ BW CA CN FO GE GL GU HK IL IN JM JP KG KR LA MH MN MO MP MT NZ PH PK SG TH TT TW UM US UZ VI ZW" />
          <firstDay day="sun"  territories="GB" alt="variant" references="Shorter Oxford Dictionary (5th edition, 2002)"/>

Originally, minDays is used for calculating ISO week number. But ISO week number is determined not just minDays, but also firstDay. For territories not using monday as the firstDay will result week number not matching the ISO 8601 week number.

As you can see the comment in the data above, we may need to define first day for week number calculation separated from the current firstDay. (Another option is - we just get rid of minDays if our intent is for providing locale neutral week number rule)


Change History

comment:1 Changed 7 years ago by mark

  • Owner changed from somebody to yoshito
  • Priority changed from assess to major
  • Status changed from new to assigned
  • Component changed from unknown to data
  • Milestone changed from UNSCH to 2.0m2
  • For the ISO calendar, always use 4, and use first day of week = Monday. Document this in the spec. Change Y, w to reflect that they are not necessarily ISO.
  • Recommend that CLDR clients have a way to set the values for constructing the ISO calendar so that Y and w use constants.
  • 4 will continue to be also the default for 001, but we will restore 1 for countries that we know about: US, CA. Others over time.

If in the future, we need a firstDayForCalendarDisplay and/or a minDaysForCalendar display, we can add them, but this ticket doesn't do that.


comment:2 Changed 7 years ago by pedberg

  • Cc pedberg added

comment:3 Changed 7 years ago by pedberg

I added a related ICU ticket: http://bugs.icu-project.org/trac/ticket/8366

comment:4 Changed 7 years ago by pedberg

  • Xref changed from 1968 to #1968 #3662 #1562 #1912 #2472 #3118 #1716 #1900

This also resolves the following tickets:

  • cldrbug 3662: for PT - will not make that change; ticket was already closed as needs-more-info.
  • cldrbug 1562: for various regions - made the changes for GF, GP, MQ, RE proposed there, the others seem less clear. Reassigned to Yoshito.
  • cldrbug 1912: & cldrbug 2472: for AU - made the change requested in those, so they have been closed as duplicates.
  • cldrbug 3118: for BR - made the change requested, so it has been closed as a duplicate.
  • cldrbug 1716: for KR - will not make that change; reassigned to Yoshito to confirm & close.
  • cldrbug 1900: for PK - will not make that change; reassigned to Yoshito to confirm & close.

comment:5 Changed 7 years ago by yoshito

  • Review set to pedberg

comment:6 Changed 7 years ago by pedberg

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

comment:7 Changed 4 years ago by emmons

  • Milestone 2.0m2 deleted

Milestone 2.0m2 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.