After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 237319 - Disjoint months in leap years on calendar printouts
Disjoint months in leap years on calendar printouts
Status: RESOLVED DUPLICATE of bug 223466
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-01-28 15:18 UTC by Kim van der Riet
Modified: 2003-01-29 17:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kim van der Riet 2003-01-28 15:18:40 UTC
Package: Evolution
Priority: Normal
Version: 1.0.8
Synopsis: Disjoint months in leap years on calendar printouts
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar

Description:
Description of Problem:
Printouts of leapyears show disjointed months (gaps between months) on
the small "summary" month displays. This affects the year printout
(which is composed entirely of the summary-style months), and all other
printouts in the small summary sections above the main calendar body.
This can also be seen in the print-preview.

Steps to reproduce the problem:
1. Using the "Go-To" button select January 1 of a leap year (e.g.
2000).
2. From the menu, select File/Print. On the Print dialog, select the
"Selected year" option.
3. Either Print or Preview.

Actual Results:
For year 2000:
- Jan 31 is on a Monday, but Feb 1 is on a Wednesday.
- Feb 29 is on a Wednesday (should be Tuesday), but Mar 1 is on a
  Tuesday.
- All months after February are 1 day early.

Expected Results:


How often does this happen?
Every time.

Additional Information:




Unknown reporter: kimp@vanderriet.com, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Gerardo Marin 2003-01-29 17:20:20 UTC
This is fixed in 1.2

*** This bug has been marked as a duplicate of 223466 ***