>> That's how it should treat those messages.
>> (Whether or not it takes them as GMT and converts it to local or simply
>> treats it as local is another discussion - I'm not sure which one is
>> right).
>
>I fail to see the distinction between the two discussions, but oh well
>(we're storing the date as an epoch offset and timezone, so we have to
>consider it to be either GMT or local -- there's no such thing as "no
>timezone").
You _could_ add a flag that means "No time zone data" and display something
appropriately, but is that really worth it? I dunno.
>> Well, my only point is that the textual time zones (other than the ones
>> listed above) are right now entirely arbitrary
>
>"Entirely" arbitrary? No, clearly there've been accepted conventions,
>immaterial of whether they've been officially approved in a standard.
_Are_ there any such conventions? I'm not sure. It seems like people
just made them up - they don't even seem to be consistant.
Anyway, just my $0.02.
--Ken
