Apache OpenOffice (AOO) Bugzilla – Issue 35616
Posterized printing skips pages
Last modified: 2013-08-07 15:40:43 UTC
Open the posted bugdoc and print it on an A4-printer with the option posterize. You get 4 pages and only 2 contain something. The lower parts of the doc are not printed at all.
Created attachment 18436 [details] bugdoc
It is a regression to OOo 1.1.x
set to prio4
Adapted target.
*** Issue 51118 has been marked as a duplicate of this issue. ***
*** Issue 54568 has been marked as a duplicate of this issue. ***
JA->THB: as it is a regression I cannot accept it to be retargeted to 'later'. Reset priority as well as it is a loss of functionality.
retargeted due to resource constraints
Resource contraints or not, it is a significant defect and loss of functionality that is seriously damaging to some of us. There is absolutely no work-around for the broken posterize feature. I used to use OO to print posters, diagrams, signs. Now I have to revert all the way back to OO 1.X! It was broken in 2.0, broken in 2.0.1, and still broken in 2.0.2! At the VERY least, if it doesn't work, then the option should at least be coded to print a popup box saying "this feature is currently not working correctly" or something. Otherwise it wastes hours of users time (and paper, and ink) while he/she tries 100 different variations to try and figure out what is wrong.
Additional comments: I have an A4 and A3 printer (Xerox Work Pro C2128). Printing a posterized (A1) document to it, selecting printer paper A3 expected 4 sheets of A3 paper to be printed Actually got one sheet of A3, some sheets of A4, but with bits missing (becuase the sheet "should have" covered an A3 area. Trying it to A4 works better in that there are no missing gaps, but I haven't get a complete document yet
*** Issue 59483 has been marked as a duplicate of this issue. ***
*** Issue 79244 has been marked as a duplicate of this issue. ***
Hi, there is a target of 3.0 set, but I see no activity? Add me to CC.
I believe this was finally fixed in OO 2.2.0 or 2.3.0 (I skipped over some versions), that is why you haven't heard much about it. I would want someone else to verify, though. While waiting for this issue to be fixed, in 2.2.0 a *much* more serious printing issue appeared that hurts us even more :( (issue 83388)
*** Issue 88488 has been marked as a duplicate of this issue. ***
Let me clarify. I did not try his test document (because there was no need). However, tiled printing *was* very much broken, and in the manner described (two or top pages print something, lots of blank other pages or pages with gibberish, no matter what type of tiling I used and no matter which printer). At some point between 2.2 and 2.3 it was fixed for me. I print large diagrams and had to transfer them over to ancient OO install to print them. I can now print them fine, I just don't know exactly when it was fixed. We do not, however, use an A4 printer. Everything is either US letter or US tabloid sized, usually printed tiled across 4 such pages (2x2).
I think a form of simple wizard for this feature would be nice, i.e. one that lets you specify when creating your document how many pages to split it into. Either that or one that lets you split page print/export after you have made the document. Would it also be possible to create the wizard in such a way that you could scale (for example) an A4 sized page up to two A4 pages to make an A3 poster? The diagram sort of shows what the wizard would need to do.
Created attachment 53066 [details] Poster Wizard diagram
reassigned
NOT reproducible with posterize.sxd on HP OJ6110 with - "Ooo 3.1.1 WIN XP DE[OOO310m19 (Build 9420)]" - "Ooo-Dev 3.2.1 multilingual version German UI WIN XP: [OOO320m16 (Build 9497)]" - "2.4.1 Multilingual version German UI WIN XP: [680m17(Build9310)]" - "1.1.4 (German) WIN XP: [645m52 (Build 8824)]" May be the problem only appears under particular conditions?
From my point of view, this now appears to work correctly in OOo 3.2, although my test printer is now an HP C6180
*** Issue 111788 has been marked as a duplicate of this issue. ***
from the comments I think this issue is closed. Please feel free to reopen if it still is an issue for you.
closing