Comment 18 for bug 365065

This happens as the date is recorded as date and time 00:00 local time.
When the time zone changes west, the local shifts backwards and change of
date occurs. As the user has no notion of time, but just date this doesn't
make sense. I can see two way to resolve this: (1) don't change time zones
-- define a time zone per file or account; (2) show and allow for change of
time as well as date, default of 12:00. The default time of 12:00 will at
least allow 12 hours time zone change except for crossing the date line.
The time will show the actual time transactions happened, which may be
different date in a different time zone, but is fine now.

Both (1) and (2) are a possibility as well.

Bug 89439 requests an enhancement of option (2) above.