You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hi @gilmoreorless i got a problem with moment-timezone and jdk. The performance of moment-timezone and JDK in processing Asia/Almaty time zones is different. Moment-timezone considers that January in Kazakhstan is in DST, and isDST is true, while JDK is false.
please help me
NOTE: This function is a HACK. moment has no way of knowing if a given time is in actual DST or not. Some time changes in a zone are DST related, some are not, and without complete timezone information it can't know.
Moment currently checks the winter and summer time, and if the offset matches the summer offset (and summer off is different than winter off), then it reports DST. This works in vast majority of cases, but as mentioned above, is not "correct" and won't work for all cases.
Because eastern Kazakhstan had a one-off change of time zone, the naive guessing in Moment is being tripped up and thinks it's a DST shift. Although it's unfortunate, it's not something we're likely to fix, given the maintenance-only status of the project.
Environment
hi @gilmoreorless i got a problem with moment-timezone and jdk. The performance of moment-timezone and JDK in processing Asia/Almaty time zones is different. Moment-timezone considers that January in Kazakhstan is in DST, and isDST is true, while JDK is false.
please help me
but jdk consider it's time is not DST time
Issue description
The text was updated successfully, but these errors were encountered: