[tz] Fw:Time Zone Iran

[Brian Inglis]

On 2023-03-27 01:10, Paul Eggert via tz wrote:
> On 2023-03-26 23:39, Patrick.Stergonschegg at orf.at wrote:
>> I just noticed that the Windows time zone for "UTC +03:30 Tehran" is probably 
>> being computed incorrectly.
>> It seems that DST +1 is being added, although Iranian Government announced 
>> that they will not switch to DST anymore, beginning in 2023.

Only MS Windows Store apps use tzdb/tzdata: native Windows apps use proprietary 
MS registry entries.

> If your MS-Windows host disagrees, perhaps you need to update its tables. I 
> don't know how that works, though.

Current entries are encoded and look like this:

 > reg query "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows 
NT\\CurrentVersion\\Time Zones\\Iran Standard Time" /s

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Iran 
Standard Time
     Display    REG_SZ    (UTC+03:30) Tehran
     Dlt    REG_SZ    Iran Summer Time
     MUI_Display    REG_SZ    @tzres.dll,-430
     MUI_Dlt    REG_SZ    @tzres.dll,-431
     MUI_Std    REG_SZ    @tzres.dll,-432
     Std    REG_SZ    Iran Standard Time
     TZI    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000400030017003B003B00E70300000300030004000000000000000000

for encoding see:
https://learn.microsoft.com/en-us/windows/win32/api/timezoneapi/ns-timezoneapi-time_zone_information#remarks

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Iran 
Standard Time\Dynamic DST
     2004    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000100030017003B003B00E70300000300000003000000000000000000
     2005    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000300030017003B003B00E70300000300020004000000000000000000
     2006    REG_BINARY 
2EFFFFFF00000000C4FFFFFF0000000000000000000000000000000000000000000000000000000000000000
     2007    REG_BINARY 
2EFFFFFF00000000C4FFFFFF0000000000000000000000000000000000000000000000000000000000000000
     2008    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000600030017003B003B00E70300000300050003000000000000000000
     2009    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000100030017003B003B00E70300000300000004000000000000000000
     2010    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000200030017003B003B00E70300000300010004000000000000000000
     2011    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000300030017003B003B00E70300000300020004000000000000000000
     2012    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000400030017003B003B00E70300000300030003000000000000000000
     2013    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000600030017003B003B00E70300000300050004000000000000000000
     2014    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000000030017003B003B00E70300000300060004000000000000000000
     2015    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000100030017003B003B00E70300000300000004000000000000000000
     2016    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000200030017003B003B00E70300000300010003000000000000000000
     2017    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000400030017003B003B00E70300000300030004000000000000000000
     2018    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000500030017003B003B00E70300000300040004000000000000000000
     2019    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000600030017003B003B00E70300000300050004000000000000000000
     2020    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000000030017003B003B00E70300000300060003000000000000000000
     2021    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000200030017003B003B00E70300000300010004000000000000000000
     2022    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000300030017003B003B00E70300000300020004000000000000000000
     2023    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000400030017003B003B00E70300000300030004000000000000000000
     2024    REG_BINARY 
2EFFFFFF00000000C4FFFFFF000009000500030017003B003B00E70300000300040003000000000000000000
     FirstEntry    REG_DWORD    0x7d4
     LastEntry    REG_DWORD    0x7e8

for encoding see:
https://learn.microsoft.com/en-us/windows/win32/api/timezoneapi/ns-timezoneapi-dynamic_time_zone_information#remarks

Due to US sanctions, US produced software is probably currently unlicensed in 
sanctioned countries, and support for those countries is sanctioned, so TZ 
updates for that software is unlikely for sanctioned countries, and it is 
probably illegal to use such software to transact with any sanctioned entities.

Such unsupported updates may have to be provided by entities within the 
sanctioned country, or a neutral third country, and any use of those updates for 
any reason, might be in violation of sanctions imposed or agreed by your 
government, such as those by the EC:

	https://www.consilium.europa.eu/en/press/press-releases/?keyword=Iran

There may be additional constraints on your organization as a public 
broadcaster, so consult your organizations' lawyers, especially if you are a 
journalist, and if not, if possible do not do whatever it is that requires time 
in Iran, as it may be illegal! ;^>

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry