Russian TZ Samara has no offset listed since 2010g
Hello, Europe/Samara has the follow zone.tab definition since 2010g (no offset listed) RU +5312+05009 Europe/Samara Moscow - Samara, Udmurtia It used to be RU +5312+05009 Europe/Samara Moscow+01 - Samara, Udmurtia Samara changed to Moscow but all the other regions are listed with an offset even if +00 (Volgograd, Moscow) while Samara is not. I can not tell by searching the mail archive if the change this way was intentional or not? Thanks - Manpreet
The main issue with this is that applications which display the name by regions, get inconsistent display when showing Europe/Russian Federation regions. Two zones, Volgograd and Moscow, show a +00 offset, Kaliningrad shows and -01 offset and Samara shows no offset. This is confusing to the users. Can we please get this patched in the next release? The patch would be --- a/tzdata2011n/zone.tab 2011-10-28 02:54:04.000000000 -0700 +++ b/tzdata2011n/zone.tab 2011-11-07 13:28:23.000000000 -0800 @@ -334,5 +334,5 @@ RU +5443+02030 Europe/Kaliningrad Moscow RU +5545+03735 Europe/Moscow Moscow+00 - west Russia RU +4844+04425 Europe/Volgograd Moscow+00 - Caspian Sea -RU +5312+05009 Europe/Samara Moscow - Samara, Udmurtia +RU +5312+05009 Europe/Samara Moscow+00 - Samara, Udmurtia RU +5651+06036 Asia/Yekaterinburg Moscow+02 - Urals RU +5500+07324 Asia/Omsk Moscow+03 - west Siberia Thanks - Manpreet On 10/31/11 3:36 PM, "Manpreet Singh" <manprsi2@cisco.com> wrote:
Hello, Europe/Samara has the follow zone.tab definition since 2010g (no offset listed)
RU +5312+05009 Europe/Samara Moscow - Samara, Udmurtia
It used to be
RU +5312+05009 Europe/Samara Moscow+01 - Samara, Udmurtia
Samara changed to Moscow but all the other regions are listed with an offset even if +00 (Volgograd, Moscow) while Samara is not. I can not tell by searching the mail archive if the change this way was intentional or not?
Thanks - Manpreet
Date: Mon, 07 Nov 2011 13:30:47 -0800 From: manprsi2 <manprsi2@cisco.com> Message-ID: <CADD8E07.8DB2%manprsi2@cisco.com> | Can we please get this patched in the next release? Consider it done. No specific plan yet on when that will be, but now that timezone silly season is over for the next few months (I hope), I'd like to catch up on all the other little things that have been left pending over the past month or so. That includes cleaning up the doc, and making source patches that seem like that should be made. Opinions on what those are welcome... (You don't need to repeat the actual change if it has already been on the list, though if it predates the last code release, a pointer to roughly when the idea was previously proposed would help.) kre
participants (2)
-
manprsi2 -
Robert Elz