[u-ca=japanese]<\/code>. I wanted to ensure that if I were to adopt it, I could continue adhering to ISO 8601 by defining gregorian<\/code> explicitly instead. However, I’ve seen github.com/unicode-org/cldr/blob/c024980f2cb0697d7bc35d1194c356a16b67096f/common/bcp47/calendar.xml#L27C25-L27C32<\/code><\/a>, which provides iso8601<\/code> as a usable alternative, [1]<\/a><\/sup> and searching for that keyword in Google returned results using [u-ca=iso8601]<\/code>, which is even better, so that problem seems solved.<\/p>\n
Advertisement
However, I noticed that I’d also see results for horrific strings like en-u-ca-iso8601-fw-wed<\/code><\/a>! github.com/tc39/proposal-intl-locale-info/issues/30<\/code><\/a> appears to demonstrate that it might be a locale:<\/p>\nnew Intl.Locale(\"en-US-u-ca-iso8601\").weekInfo\n<\/code><\/pre>\n
Advertisement
…however, what locale includes a day of the week? I’ve never seen that in ISO 639.<\/p>\n
\n\n\nstackoverflow.com/questions/25050034/get-iso-8601-using-intl-datetimeformat#comment70898760_25050034<\/code><\/a> ↩︎<\/a><\/p>\n<\/li>\n<\/ol>","upvoteCount":1,"answerCount":2,"datePublished":"2025-02-13T00:06:03.183Z","author":{"@type":"Person","name":"rokejulianlockhart","url":"https://community.spiceworks.com/u/rokejulianlockhart"},"acceptedAnswer":{"@type":"Answer","text":"It’s an region override for setting the first day of the week to Wednesday.<\/p>\n
https://unicode.org/reports/tr35/tr35-dates.html<\/a><\/p>\n\nThe day indicated by firstDay<\/code> 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<\/code> (that is, day 1 is the day specified by firstDay<\/code>), but in the future we may add a way to specify this separately. The firstDay<\/code> value determined from the region can be overridden by the locale keyword “fw”, see [Unicode First Day Identifier]<\/p>\n<\/blockquote>\n(Unicode Locale Data Markup Language (LDML)<\/a>).<\/p>\nhttps://unicode.org/reports/tr35/tr35.html#UnicodeFirstDayIdentifier<\/a><\/p>","upvoteCount":3,"datePublished":"2025-02-13T06:36:19.964Z","url":"https://community.spiceworks.com/t/whats-en-u-ca-iso8601-fw-wed/1174727/2","author":{"@type":"Person","name":"PatrickFarrell","url":"https://community.spiceworks.com/u/PatrickFarrell"}},"suggestedAnswer":[{"@type":"Answer","text":"I’ve recently read the proposed RFC 9557<\/a>, and it defines calendar definitions like [u-ca=japanese]<\/code>. I wanted to ensure that if I were to adopt it, I could continue adhering to ISO 8601 by defining gregorian<\/code> explicitly instead. However, I’ve seen github.com/unicode-org/cldr/blob/c024980f2cb0697d7bc35d1194c356a16b67096f/common/bcp47/calendar.xml#L27C25-L27C32<\/code><\/a>, which provides iso8601<\/code> as a usable alternative, [1]<\/a><\/sup> and searching for that keyword in Google returned results using [u-ca=iso8601]<\/code>, which is even better, so that problem seems solved.<\/p>\nHowever, I noticed that I’d also see results for horrific strings like en-u-ca-iso8601-fw-wed<\/code><\/a>! github.com/tc39/proposal-intl-locale-info/issues/30<\/code><\/a> appears to demonstrate that it might be a locale:<\/p>\nnew Intl.Locale(\"en-US-u-ca-iso8601\").weekInfo\n<\/code><\/pre>\n…however, what locale includes a day of the week? I’ve never seen that in ISO 639.<\/p>\n
\n\n\nstackoverflow.com/questions/25050034/get-iso-8601-using-intl-datetimeformat#comment70898760_25050034<\/code><\/a> ↩︎<\/a><\/p>\n<\/li>\n<\/ol>","upvoteCount":1,"datePublished":"2025-02-13T00:06:03.246Z","url":"https://community.spiceworks.com/t/whats-en-u-ca-iso8601-fw-wed/1174727/1","author":{"@type":"Person","name":"rokejulianlockhart","url":"https://community.spiceworks.com/u/rokejulianlockhart"}}]}}
