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
I have thought a bit more about it. Regardless of whether the project use backzone or not, Northern Vietnam will still be in a different timezone than Southern Vietnam in timezone database. (Southern Vietnam is always Asia/Ho_Chi_Minh, while Northern Vietnam is either Asia/Hanoi in backzone or Asia/Bangkok in the standard dataset.)
Thus, as the timezone-bondary-buioder's objective is to create a geographical correspondence for the tz database, it seems appropriate to split Vietnam to reflect this difference in tz database.
The tricky thing here is Asia/Hanoi which have more data in the backzone tab and not just simply a link
I'm actually leaning towards using Asia/Bangkok to keep this library compatible with the current tz database. This would be the first area where a timezone identifier from another country will be used, but as you mention, it's probably the right thing to do.
As for geographic boundaries, it looks like the Quang Tri Province was the northernmost province of South Vietnam, so that could be the boundary.
I have thought a bit more about it. Regardless of whether the project use backzone or not, Northern Vietnam will still be in a different timezone than Southern Vietnam in timezone database. (Southern Vietnam is always Asia/Ho_Chi_Minh, while Northern Vietnam is either Asia/Hanoi in backzone or Asia/Bangkok in the standard dataset.)
Thus, as the timezone-bondary-buioder's objective is to create a geographical correspondence for the tz database, it seems appropriate to split Vietnam to reflect this difference in tz database.
As for exactly how to split it into different zone, I guess https://en.wikipedia.org/wiki/Vietnamese_Demilitarized_Zone would be a reasonable starting point.
The text was updated successfully, but these errors were encountered: