Date: Sat, 23 Feb 2013 13:00:26 +1100 From: Peter Stagg <P.Stagg@bom.gov.au> Message-ID: <F6B9883A73AC594592041E20C59A484601C3B5A0B6E9@BOM-VMBX-HO.bom.gov.au> | Is their anything I can do or say to bring some clarity to this issue | and perhaps resolve it one way or another? You could look back through the archives of this mailing list so you can see where the issue has been discussed many times before - and in particular note that the web page you referred to in your first message has been pointed out many times before - and see why it is irrelevant. | Part of the reason I'm perusing this is because I know from experience | that this situation frustrates many Australian developers Much of the problem is that what frustrates developers isn't really relevant, as they shouldn't be attempting to use the abbreviations in any way where their being changed would make a difference. What would be relevant would be if the end users were complaining that they we getting shown incorrect values - but that isn't what ever seems to happen, it is only people attempting to misuse those strings for purposes for which they are not suited. If your bureau want to use "correct" abbreviations, they should probably start by contacting the various state government departments that actually define the time zones, and ask them what they believe should be used - as best we have ever been able to tell, there are no defined zone name abbreviations anywhere, just full names, which essentially never have "Australian" in their names (which makes sense, none of the state governments could really define what is Australian time after all) and in most cases, use Summer Time as the name for the time when Standard Time does not apply (not Daylight Savings Time). kre