Thanks to David et al for taking this initiative. In respons to the specific questions posed: - would the preference be to preceed the abbreviations with A, or not? I think the 'A' is most apropriate and is in keeping with my understanding of conventioned followed in Australia. It would also be very easy to deal with in the situation where a programer may want to drop the 'A' - historically, how far back should we apply the patch to the abbreviations. I'm in favour of retro-fitting it to the start of Daylight Savings in Australia (sate-based dependancies taken into account). After all its a bit like BC and AD. If you we're wandering around in 200BC you had no idea it was 200BC but today we would not refer to it as anything else (unless you don't use the christian calendar, of course). ________________________________________ Date: Sun, 07 Apr 2013 21:19:36 -0400 From: David Patte ? <dpatte@relativedata.com> Subject: Re: [tz] Ambiguous abbreviations for Australian timezones when daylight savings is in affect [SEC=UNCLASSIFIED] To: tz@iana.org Message-ID: <51621B28.4030105@relativedata.com> Content-Type: text/plain; charset=UTF-8; format=flowed A group of us from the list have decided to put together a proposed patch to change the Australian abbreviations to S/D abbreviations. We are hoping, that the maintainers of tz decide to implement the patch in the tz database. In the mean time: - would the preference be to preceed the abbreviations with A, or not? - historically, how far back should we apply the patch to the abbreviations. We will submit the patch to the list for review, and hope it is implemented. But if it is not, we have decided to fork tz and provide a new distribution with the new abbreviations applied. David Patte Relative Data, Inc. _______________________________________________