Microsoft Entourage Time Zones

[Mark D. Sugi]

When one creates a calendar event in Entourage 2004 for OS X (v11.1.0), one
has the option of setting the time zone.

My computer is on Central European Time (CET). The event is occurring at
11:20 PM on the East Coast of the United States, that is, Eastern Standard
Time (EST).

The event shows up in the calendar view (monthly view for example) as 5:20
AM the next day, because CET is EST +6h. Only when I change the time zone on
the event to CET does it show up as 11:20 PM on the previous day.


What¹s the problem with this? For international users or business travelers,
this presents a relatively interesting dilemma for scheduling. It¹s possible
that I am failing to understand this correctly, so please correct me if I am
incorrect.

I am on the East Coast, in EST. I have an event on the East Coast tomorrow.
I schedule it, EST event time zone and EST computer clock. OK.

I am on the East Coast, in EST. I have an event in Rome tomorrow. I schedule
it, CET event time zone and EST computer clock. When I arrive in Rome
tomorrow and set my computer clock to CET, the event jumps ahead 6 hours and
I allow myself to sleep in (assuming I¹m stupid, and I am.)

I am in Rome, in CET. I have an event next month on the East Coast. I
schedule it, EST event time zone and CET computer clock. I arrive 6 hours
early when I get back.

Capisce? My suggestion is to keep the SET time zones for the event
regardless of what the computer clock is doing. Thus, the sophisticated user
can set events according to time zone and change her clock upon arriving at
the destination instead of months in advance to plan.

Grazie.

 

[Matthew Smith]

When one creates a calendar event in Entourage 2004 for OS X (v11.1.0), one
has the option of setting the time zone.

My computer is on Central European Time (CET). The event is occurring at
11:20 PM on the East Coast of the United States, that is, Eastern Standard
Time (EST).

The event shows up in the calendar view (monthly view for example) as 5:20
AM the next day, because CET is EST +6h. Only when I change the time zone on
the event to CET does it show up as 11:20 PM on the previous day.


What¹s the problem with this? For international users or business travelers,
this presents a relatively interesting dilemma for scheduling. It¹s possible
that I am failing to understand this correctly, so please correct me if I am
incorrect.

I am on the East Coast, in EST. I have an event on the East Coast tomorrow.
I schedule it, EST event time zone and EST computer clock. OK.

I am on the East Coast, in EST. I have an event in Rome tomorrow. I schedule
it, CET event time zone and EST computer clock. When I arrive in Rome
tomorrow and set my computer clock to CET, the event jumps ahead 6 hours and
I allow myself to sleep in (assuming I¹m stupid, and I am.)

I am in Rome, in CET. I have an event next month on the East Coast. I
schedule it, EST event time zone and CET computer clock. I arrive 6 hours
early when I get back.

Capisce? My suggestion is to keep the SET time zones for the event
regardless of what the computer clock is doing. Thus, the sophisticated user
can set events according to time zone and change her clock upon arriving at
the destination instead of months in advance to plan.

I am not following this.

I am on the East Coast, in EST. I have an event in Rome tomorrow. I schedule
it, CET event time zone and EST computer clock. When I arrive in Rome
tomorrow and set my computer clock to CET, the event jumps ahead 6 hours and
I allow myself to sleep in (assuming Im stupid, and I am.)

If your computer is set to EST and you create an event with Rome time
which is at 18:00, it will appear in your calendar as 12:00. Once you
arrive in Rome you change your clock to Rome time. The event will be
displayed at 18:00. Are you saying you want to see it while your
computer is set to EST at 18:00? That doesn't make sense. Try adding a
flight from Sydney to Los Angeles, where the flight arrives after it
leaves. Changing time zone means that things will move in the calendar.

If that is not what you are talking about then it wasn't obvious.