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 660027 - Multi-line lines and Multi-page reports are not correctly handled.
Multi-line lines and Multi-page reports are not correctly handled.
Status: RESOLVED OBSOLETE
Product: GnuCash
Classification: Other
Component: Reports
2.4.x
Other All
: Normal normal
: ---
Assigned To: Christian Stimming
gnucash-reports-maint
Depends on: 693363
Blocks:
 
 
Reported: 2011-09-24 18:29 UTC by Colin Scott
Modified: 2018-06-29 23:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Colin Scott 2011-09-24 18:29:43 UTC
It seems to me that report formatting and printing need something of a rethink. Some of the basic formatting is difficult to read, whether displayed or printed, and what is appropriate for a report on the display is really not acceptable in a printed version of the same report.

DISPLAY AND PRINT
=================

1)  Where in any line of a report there is data that is wider than its column, the data is (quite correctly) wrapped into multiple lines.  The height of the line thus becomes equal to the height of the tallest column (a multi-line line!).  However, the text in each column is aligned to the centre of the vertical space, which is difficult to read - all text *should* be aligned to the top of the vertical space.


PRINT ONLY
==========

When printing a report, page breaks seem not to be handled at all.  Thus:- 

2)  When printing, a page break can occur in the middle of a line, leaving the top half of the line text at the bottom of the current page, and the bottom half of the same line text at the top of the next page.  (This effect has certainly been noted in a multi-line line;  I am unaware whether or not it can happen to a singleton line.)

There is a certain minimum amount of page-break handling that any user of printed reports is reasonably going to expect:

3)  The bottom line on every page of a report should include, at the very least, the page number, and preferably also the total number of pages in the report.  Eg "page 3 of 27".

3)  The top line of every page in the report (not just the first page)  should include the report title.

4)  The body of every page in a report (not just the first page) should be headed by the current set of columnar headings.
Comment 1 Geert Janssens 2013-02-21 18:27:43 UTC
I can confirm the symptoms. I have hit those before as well.

I don't know if it will be easy to fix though. Last time I checked this was a problem that originated deeply in the webkit code.
Comment 2 Chris 2017-08-03 10:37:00 UTC
To fix this in pure HTML we just need to encapsulate the table headers and body with THEAD and TBODY. And we add a style rule for <tr> as "page-break-inside: avoid !important;}" It will be fixed if the report is Exported to HTML then printed from a modern browser.

I guess internal report printing will require that webkit or the PDF renderer is upgraded.

I suggest we make necessary modifications anyway in preparation for an eventual Webkit upgrade.

Created PR #167
https://github.com/Gnucash/gnucash/pull/167
Comment 3 John Ralls 2017-08-03 15:48:26 UTC
GnuCash 2.8 will use the WebKit2 API that's their current release.
Comment 4 John Ralls 2017-09-24 22:16:59 UTC
Reassign version to 2.4.x so that individual 2.4 versions can be retired.
Comment 5 John Ralls 2018-06-29 23:01:08 UTC
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=660027. Please continue processing the bug there and please update any external references or bookmarks.