On Jan 18, 2019, at 7:35 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
On 1/18/19 3:39 PM, Deborah Goldsmith via tz wrote:
It seems like the real problem here is gathering the data, and the number of new zones. I don’t think there would be any harm in adding time zones for these resorts.
It's notoriously hard to get reliable data for private time zones, and I'd rather not try. It's painful enough keeping the public time zone info up-to-date. If there's a real call for this data we could put it into 'backzone' or a similar file like that, but I don't want us to worry about maintaining it.
An alternative to adding one zone per resort could be to have Indian/Maldives+30, Indian/Maldives+60, and Indian/Maldives+90. There are already generic TZ settings like TZ='<+06>-6' and TZ='Etc/GMT-6' that support that sort of usage, so we shouldn't need to add specific tzdb entries for it.
It sounds like we'd need some Etc/GMT-630 (or something similar) for "generic half hour offset" cases. paul