Version: (using Devel) Compiler: gcc 4.3.2 OS: Linux Installed from: Compiled sources - Configure Akonadi with an IMAP and Kolab resource. - Launch Kaddressbook - Create or select a dozen of Contacts (so that if you select them all there should be two printed pages) - Go to File menu/Print... - Select 'Print to File (PDF)' - Choose a name and a location for the .PDF file - Click on 'Print' - Check the 'Selected contacts' QToolButton - Click on 'Next'twice - Select 'Detailed Style' from the Print Style combo box - Click on 'Next' - Click on 'Finish' Open the .pdf you've just created. In it, there is a good chance that the last contact of the first page is split between the two pages (some information on the bottom of the first page and the rest on the top of the second one). Ideally, it would be better that the whole contact be pushed onto the next page, if the information about it does not fit within the current page. Trunk, Svn Rev 1024362
I wonder if the switch to HTML makes it impossible to fix this? Tobias, wasn't the benefit of the "hand-written painting code" that it was possible to do proper page breaking?
Hej David, the page breaking was one advantage of the handcoded printing style, however it has a lot of disadvantages as well: - difficult to read/debug code - no support for the following after the usage of QPrinter in KDE - print only a range of pages - print copies - print reverse I can have a look at this again, Qt richtext allows to add css hints to do a page break if possible, it is used by the Mike's Printing Style already.
I can confirm this issue still exists in KDE 4.8.3, and therefore (probably) also in devel. Is somebody willing / able to take a look at this issue? It doesn't seem to make sense to keep a ticket open if nobody's going to pick it up. I'll revisit this issue later, but if nobody's getting ready to work on the issue perhaps it's best to close it off and have it disappear from everyone's radar until the issue gains more traction.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kaddressbook (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.