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 743916 - cell printed twice
cell printed twice
Status: RESOLVED OBSOLETE
Product: Gnumeric
Classification: Applications
Component: Printing
git master
Other Linux
: Normal normal
: ---
Assigned To: Andreas J. Guelzow
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2015-02-03 10:11 UTC by Frédéric Parrenin
Modified: 2018-05-22 14:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
.xlsx file to reproduce the problem (198.47 KB, application/octet-stream)
2015-02-03 10:11 UTC, Frédéric Parrenin
Details

Description Frédéric Parrenin 2015-02-03 10:11:28 UTC
Created attachment 296003 [details]
.xlsx file to reproduce the problem

Steps to reproduce:
- open the attached .xlsx file
- click on "print preview"
=> the cell containing "5 cm from" is printed on page 1 (on the right) and again on page 7 (on the left).
Comment 1 Andreas J. Guelzow 2015-02-03 15:30:40 UTC
cell H1 (that is the cell containing the text "5 cm from") is only printed once, on the first page. That text also overlaps into cell I1, So the text is also printed when cell I1 is printed, which happens on the next page. If you do not want that to happen just don't have text that overlaps into the next column.

While we could clip the the page frame, I don't think you would necesarily appreciate the text  "5 cm from" being slightly cut off on the first page and you having a few extra black pixels on the second page.
Comment 2 Frédéric Parrenin 2015-02-03 17:32:24 UTC
I would personally prefer the clipping solution than to have duplicated texts.
Then you can still adjust the column width to avoid clipping.
Comment 3 Andreas J. Guelzow 2015-02-03 17:46:32 UTC
Last time we enabled clipping on the page content, printing and previewing became unacceptably slow. Since this is within cairo, we have no control over the speed.

Note that if you had a print area set you probably would not even have noticed.
Comment 4 GNOME Infrastructure Team 2018-05-22 14:16:55 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnumeric/issues/274.