I think the pitfalls are human interface problems rather than technical issues.
Good. That’s what I thought too. It’s not even a difficult challenge. Un*x and its friends have been converting the displayed time of their filesystems from an internal format to local time since eons back. Stuff like Outlook/Exchange convert times from its calendar to and from local time so that you can schedule meetings around the world without having to figure out any offsets.
Of
A time zone is more than just an offset; you need to specify the daylight >savings time rules as well.
You don’t say! TZ for each association and a TZ for each user. As it’s fashionable to speek likes meerkats… simples!
Stuff like Outlook/Exchange convert times from its calendar to and
from local time so that you can schedule meetings around the world
without having to figure out any offsets.
They don’t get it quite right though. In my local time zone, 2009-10-25 01:30 occurs twice. I just created an Outlook/Exchange appointment for that time, and it didn’t ask me which one I meant. I don’t know which one it chose.
Canada had its first SOTA activation yesterday. I was on the air from 1600 UTC to 1915 UTC, had too many things scheduled that day. Rain made me postpone this activation.
HA7UG was the very first SOTA contact in VE land at 1610 UTC, 20m CW. Tnx to all who called.
In reply to VA2SG:
I took my rig and key to work and listened to no avail. With 3 assocations on the east coast I think I should install it permenently.
Much praise on your success, JP.
Stu- KI6J
In reply to G0AZS:
I did bring the yellow box and made 1 QSO on 30 meters with it. It just GOT to take part of it hi! … and drains battery less than the 817…