[wp-trac] Re: [WordPress Trac] #3962: WordPress should adjust for
DST ("location" appropriate)
WordPress Trac
wp-trac at lists.automattic.com
Fri Apr 17 11:37:26 GMT 2009
#3962: WordPress should adjust for DST ("location" appropriate)
----------------------------+-----------------------------------------------
Reporter: iacas | Owner: anonymous
Type: task (blessed) | Status: reopened
Priority: high | Milestone: 2.8
Component: Administration | Version: 2.1.2
Severity: normal | Resolution:
Keywords: needs-testing |
----------------------------+-----------------------------------------------
Comment(by sambauers):
I still think the numbered GMT offsets are absolutely not necessary and
are confusing. Also, there aren't any 30 minute or 45 minute offsets as
listed in the old timezone implementation.
There are too many similar options which are completely equivalent or
antiquated. E.g.: UTC, UCT, Universal, GMT, GMT0, GMT+0, GMT-0 are all
equivalent and the GMT options are antiquated.
In the Australia group about half of them are antiquated (and effectively
duplicates) as they are regions rather than cities. A user setting their
timezone in Sydney will have an unnecessary choice between Sydney and NSW.
A user in Broken Hill will possibly be confused between Adelaide, South,
Broken Hill, Yancowinna, Sydney and NSW.
Other continents contain multiple spellings or instances of the same
location - Ulaanbaatar and Ulan Bator - Faroe and Faeroe -
Argentina/Buenos Aires and Buenos Aires.
We may suffer a few complaints if we include the colonial name of the
Indian city Calcutta as well as the modern Kolkata. Same applies if we
have Saigon as well as Ho Chi Minh (Which should be "Thanh Po Ho Chi
Minh").
Antarctica can just be left out completely. (Bases there usually set
themselves to the same time as their supply station, which they would know
without the aid of the individual listings).
A full separate 'Arctic' grouping for the sake of one island is excessive
(they know they follow Norway time anyway).
Basically, we need a set of saner zones for this to not cause issues.
I suggest we create a lookup table (using an array in PHP) which maps a
set of timezones which we specify to ZoneInfo names. This will (for
example) more than halve the zones for Australia and we can deal with some
of the problems here on a case by case basis.
It should be possible to get the community to contribute to sane sets of
local timezones for there region/country.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/3962#comment:65>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list