#15599 closed bug (fixed)
Update timezone for Turkey
| Reported by: | bitigchi | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta2 |
| Component: | Preferences/Time & Date | Version: | R1/Development |
| Keywords: | timezone | Cc: | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Turkey is in GMt+3 timezone for a while now, but Haiku timezone data is not up-to-date. For time n, it is n-1 for Local Time, n+1 for GMT time.
Change History (6)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
GMT time (UNIX compatible) is confirmed fixed, thanks for the update.
Local time (Windows compatible) is three hours behind though. I don't even know what that local time means, is it supposed to be like that? Seems like it's GMT 0 (although the GMT indicator on Deskbar shows that it's GMT +3)
comment:3 by , 4 years ago
"Local time" mode means the hardware clock is set to the local time, matching Windows behavior. You use this when you run Windows on the same machine and want both OS to show the correct time.
When switching from one to another, you need to re-synchronize the clock using NTP.
"GMT time" means the hardware clock is set to the GMT time, and the OS applies the offset for the local timezone. This is the default in Haiku and also how all other OS except Windows behave.
comment:4 by , 4 years ago
I see, thanks for the explanation! Ticket can be closed (I'd like to do it myself, but I don't see any option).
comment:5 by , 4 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:6 by , 4 years ago
| Milestone: | Unscheduled → R1/beta2 |
|---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
We have updated ICU to version 57.2 and bundled tzdata to 2019c (from 2016f), which should fix this. Please confirm that the results are correct after updating.