GNOME Bugzilla – Bug 360896
Printing contacts isn't correctly formatted <~A4
Last modified: 2013-12-22 22:45:31 UTC
Please describe the problem: If I attepmt to print all my contacts to a page size smaller than A4 - e.g. A5 - the formatting fails and the output is unusable. The smaller the paper size, the worse the problem. (Printing to a different format, e.g. 2 sides to a page, fails entirely to produce anything other than a blank page) Steps to reproduce: 1. Open the print dialog from the Contacts view 2. Select a page format smaller than A4, e.g. A5, and print 3. Actual results: The printed output is incorrectly formatted. Expected results: The printed output would be formatted as well as it is for larger paper sizes. Does this happen every time? Yes. Other information: See attachments of the output.
Created attachment 74352 [details] Printed output from Contacts at A5 paper size
Created attachment 74353 [details] Printed output from Contacts at A6 paper size
Valid in 2.22.3
Is this still present in Evolution 2.24?
Caveats: - I don't have a printer available here, so I'm relying on print preview - the print dialog have changed a lot in the last two and a half years, it's not even clear to me how I should force printing to an A5 sheet If I set File -> Page Setup to A5 Then Print... and get a Print Preview (this print dialog doesn't appear to have page size settings any more) Then the preview output is nowhere near as broken as the PDF attachments comment #1 and comment#2 The vertical numeric-alpha index (seen running down the right of the above attachments) is completely missing. Is this a printing error or a feature enhancement of newer Evo versions? ;) While improved, the formatting is still wrong, and overflows the bottom (and sometimes side) of the page. It does this for A4 too, mind, so I'm not sure it's a specific problem with smaller paper sizes. If you can't reproduce I'll try create some test data to make some sample print to PDFs. evolution-2.24.5-1.fc10.i386
*** Bug 475580 has been marked as a duplicate of this bug. ***
This appears to be fixed for me in 3.10.3. Thanks!