> That list cant be right - it's missing BST (British Summer Time = GMT+1) for > starters. But if I print [NSTimeZone localTimeZone] on the Mac in front of > me then it tells me that it is in "BST", so preseuably OSX is quite happy > to take that ?
That's what I got returned on Mac OS-X and OpenStep by [NSTimeZone abbreviationDictionary] The file in /NextLibrary/Frameworks/Foundation.framework/Resources/TimeZoneInfo/Abbreviation.table says the same. I think, the important thing is that it is somewhat defined. Below are the comments from the OpenStep abbreviation file. Looks like I have to see how to use the locations instead of abbreviations. At least now I know why I use UTC, whenever possible :-) /* The issue of time zone abbreviations is a mess, since the most common abbreviations are not unique (there is no one-to-one mapping between time zone names and abbreviations, nor the reverse). Here, we arbitrarily pick a few. In general it is better NOT to use a time zone abbreviations in input or display, since what "CST" in a formatted GMT date would likely indicate a different date to a user in Chicago, U.S.A. than to one in Sydney, Australia. */ Georg _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-gnustep
