Canonicalized timezone name in date-time output is not up to date for a few timezones (e.g. Asia/Kathmandu)
Reported by
szepie...@logicart.pl,
Sep 11 2016
|
||||||
Issue descriptionChrome Version : 9115ecad1cae66fd5fe52bd9120af643384fd6f3-refs/branch-heads/2743@{#728} URLs (if applicable) : Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: N/A Firefox: OK IE: N/A What steps will reproduce the problem? (1) Set your locale to Kathmandu Nepal (2) Run following code in JS console Intl.DateTimeFormat().resolvedOptions().timeZone (3) The result is: "Asia/Katmandu" and should be "Asia/Kathmandu" What is the expected result? What happens instead? Please provide any additional information below. Attach a screenshot if possible.
,
Sep 14 2016
I think *maybe* this is caused by stale ICU data files? Over to jshin@ for a look.
,
Sep 14 2016
Not sure if it helps, here: https://cs.chromium.org/chromium/build/third_party/pytz/zoneinfo/Asia/?sq=package:chromium I found that sources contains both names: Katmnadu and Kathmandu. Similar issue you can experience with Macao / Macau
,
Sep 14 2016
It's due to the way ICU canonicalizes the timezone name. See http://www.icu-project.org/trac/ticket/12044 If the upstream does not fix it in upcoming release (58.x), I'll see what I can do locally. It's not just Kathmandu as seen in the ICU ticket above.
,
Oct 11 2016
It's a bit more complicated. Occasionally, IETF timezone database changes what is canonical among multiple names for a single timezone, but CLDR (that ICU uses) keeps a stable canonical timezone id for a given time zone. However, Asia/Saigon and Asia/Katmandu were deprecated in 1993 (before the CLDR started, I guess). So, I don't know why CLDR has the deprecated names as canonical. I'm waiting for a response from ICU/CLDR folks.
,
May 26 2017
http://unicode.org/cldr/trac/ticket/9892 is where this issue has to be dealt with.
,
Aug 2
https://dxr.mozilla.org/mozilla-central/source/js/src/builtin/intl/TimeZoneDataGenerated.h lists a lot longer list of the difference between ICU/CLDR and IANA. I think we have to handle them on v8's end ourselves because 1) CLDR may not want to change their timezone ids (for stability reasons). Despite that, ICU can override CLDR, but not sure if ICU is willing to. 2) Even if they're willing to, it'll take a while.
,
Aug 2
,
Aug 2
BTW, there are other ids with this issue: e.g. Calcutta vs Kolkata
,
Oct 21
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by krajshree@chromium.org
, Sep 12 2016Labels: -Pri-3 M-55 OS-Linux OS-Mac OS-Windows Pri-2
Status: Untriaged (was: Unconfirmed)
508 KB
508 KB View Download