Jeffrey Harris wrote:

Basically, on Windows, do we use the Win32 timezone definitions (good,
consistent human readable names for timezones, variable cross platform
behavior), or a zoneinfo database (then it's unclear what human readable
label to use for the local timezone, since Windows' label for local time
won't uniquely match an entry in the zoneinfo database).



I think we do need a list of human-readable timezones in the current language, and I don't think we want to be maintaining that list ourselves.. hence it would be best if we could rely on the system for this list. Seems like the tricky part is mapping any particular system timezone into a language that we can understand. I mean, do we, chandler, need to know or deal with daylight savings? Can we just initialize python's timezone object to from the system data?

When you say "variable cross platform behavior" what exactly do you mean? If the same information can be culled from each system, then we should be pretty consistent across platforms, even if Windows describes a particular timezone with different english text (which would be fine IMO)

Of course, I have no idea how ICU handles timezones, and it might be helpful to understand what we can get from it.

Alec

For Cosmo I don't think you need to worry about the local timezone, so
you should probably use a zoneinfo db.

Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to