From 95ff5643022e6d08266e59b7c94691bbb4495685 Mon Sep 17 00:00:00 2001 From: Peter Edberg Date: Wed, 4 Oct 2023 17:50:39 -0700 Subject: [PATCH] CLDR-16848 Note parse issues for week of year; update mods for Transforms --- docs/ldml/tr35-dates.md | 4 +++- docs/ldml/tr35.md | 3 ++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/ldml/tr35-dates.md b/docs/ldml/tr35-dates.md index 99e04f38fb5..3288447af46 100644 --- a/docs/ldml/tr35-dates.md +++ b/docs/ldml/tr35-dates.md @@ -1144,7 +1144,9 @@ These values provide territory-specific information needed for week-of-year and … ``` -In order for a week to count as the first week of a new year for week-of-year calculations, it must include at least the number of days in the new year specified by the minDays value; otherwise the week will count as the last week of the previous year (and for week-of-month calculations, `minDays` also specifies the minimum number of days in the new month for a week to count as part of that month). +In order for a week to count as the first week of a new year for week-of-year calculations, the week beginning with `firstDay` must include at least the number of days in the new year specified by the `minDays` value; otherwise the week will count as the last week of the previous year (and for week-of-month calculations, `minDays` also specifies the minimum number of days in the new month for a week to count as part of that month). + +> **Note:** For week-of-year calculations, Gregorian years may have 52 or 53 weeks. Changes in the value of `minDays` or `firstDay` can affect the year to which a date is assigned as well as the number of weeks in a given year; implementations that parse dates using week-of-year formats should be prepared to handle such cases. For example when parsing a date in week 53 of a year for which current values of `minDays` and `firstDay` no longer result in a 53-week year, that date should be treated as in the first week of the following year. The day indicated by `firstDay` is the one that should be shown as the first day of the week in a calendar view. This is not necessarily the same as the first day after the weekend (or the first work day of the week), which should be determined from the weekend information. Currently, day-of-week numbering is based on `firstDay` (that is, day 1 is the day specified by `firstDay`), but in the future we may add a way to specify this separately. The `firstDay` value determined from the region can be overridden by the locale keyword "fw", see [Unicode First Day Identifier](tr35.md#UnicodeFirstDayIdentifier). diff --git a/docs/ldml/tr35.md b/docs/ldml/tr35.md index 7f51d252c17..5b192781633 100644 --- a/docs/ldml/tr35.md +++ b/docs/ldml/tr35.md @@ -5,7 +5,7 @@ |Version|44 (draft)| |-------|----------| |Editors|Mark Davis (markdavis@google.com) and other CLDR committee members| -|Date|2023-10-03| +|Date|2023-10-04| |This Version|https://www.unicode.org/reports/tr35/tr35-68/tr35.html| |Previous Version|https://www.unicode.org/reports/tr35/tr35-67/tr35.html| |Latest Version|https://www.unicode.org/reports/tr35/| @@ -4034,6 +4034,7 @@ Other contributors to CLDR are listed on the [CLDR Project Page](https://www.uni * [General](tr35-general.md#Contents) * Added new section [Unit Identifier Uniqueness](tr35-general.md#Unit_Identifier_Uniqueness), and added a relevant constraint on base_component in the [Syntax](tr35-general.md#syntax) section. + * Several clarifications were added in [Transform Rules Syntax](tr35-general.md#Transform_Rules_Syntax), and a new section [Transform Syntax Characters](tr35-general.md#transform-syntax-characters) was added with a table of the characters. * [Dates](tr35-dates.md#Contents) * New section [First Day Overrides](tr35-dates.md#first-day-overrides): Described the various locale ID elements that affect determination of the first day of the week (for week of year calculations), and the order in which they should be considered. Also noted in [Key/Type Definitions](#Key_Type_Definitions) which keys can affect determination of first day.