搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Why isn't the correct timezone used when printing a calendar?

  • 2 个回答
  • 2 人有此问题
  • 10 次查看
  • 最后回复者为 Matt

more options

I have correctly set up my timezone in Options, Calendar, to my timezone (GMT-0400, also known as Eastern) and the calendar entries appear correctly with the correct time when viewed in the program. But when attempting to print the calendar, and only when using "Monthly Grid" or "Weekly Planner" layout, the entries appear at the 4 hours later, presumably GMT times. This does not happen in the "List" print layout. I'm using the latest version of Thunderbird (45.2.0) with the integrated Lightning add-on it comes with (also the latest). I'm on Windows 7 64bit, and the timezone is correctly set up on the OS settings too.

I have correctly set up my timezone in Options, Calendar, to my timezone (GMT-0400, also known as Eastern) and the calendar entries appear correctly with the correct time when viewed in the program. But when attempting to print the calendar, and only when using "Monthly Grid" or "Weekly Planner" layout, the entries appear at the 4 hours later, presumably GMT times. This does not happen in the "List" print layout. I'm using the latest version of Thunderbird (45.2.0) with the integrated Lightning add-on it comes with (also the latest). I'm on Windows 7 64bit, and the timezone is correctly set up on the OS settings too.
已附加屏幕截图

所有回复 (2)

more options

New flaw found. Even though the ics file that imported the entire contents of the calendar has these entries:

BEGIN:VTIMEZONE TZID:America/Detroit

it seems ALL calendar entries were defaulted to GMT. This was not visible except when printing in the above layout formats ONLY, so I'd still think this is a bug.

more options

If I recall correctly ical files, like mail represent time in UTC with offsets.

I would be more inclined to check your computer has the correct timezone, or that the printer does.

This old bug does sound like what your saying. https://bugzilla.mozilla.org/show_bug.cgi?id=1151011 But it was fixed 12 months ago.