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 62210 - formatted fields sometimes printed as ####
formatted fields sometimes printed as ####
Status: RESOLVED DUPLICATE of bug 152939
Product: Gnumeric
Classification: Applications
Component: Printing
git master
Other All
: Low minor
: ---
Assigned To: Jody Goldberg
Jody Goldberg
: 30236 79376 87936 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2001-10-12 16:45 UTC by Armin van der Togt
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Armin van der Togt 2001-10-12 16:45:59 UTC
I formatted some cells in a sheet as custom so it would show it in red with
minus sign if they were negative, and black without sign if they are
positive. When I let gnumeric resize all columns so the contents fits, and
then I make a print preview some numbers appear as ##### as if they do not
fit in the cell when printing. When I actually print it, the ##### are
still there. I can send an example sheet if nessecary.
Comment 1 Jody Goldberg 2001-10-12 20:58:53 UTC
This stems from differencs between the fonts on the screen and fonts on the
printer.  We'll look at solution during 2.0
Comment 2 Andreas J. Guelzow 2002-04-23 06:39:24 UTC
*** Bug 79376 has been marked as a duplicate of this bug. ***
Comment 3 Andreas J. Guelzow 2002-04-23 21:52:55 UTC
*** Bug 30236 has been marked as a duplicate of this bug. ***
Comment 4 Andreas J. Guelzow 2002-04-23 21:54:09 UTC
Just as a note:  #30236 looks at the same problem but as it appears
theough zooming.
Comment 5 Andreas J. Guelzow 2002-09-26 13:02:26 UTC
*** Bug 87936 has been marked as a duplicate of this bug. ***
Comment 6 Morten Welinder 2004-09-23 16:00:56 UTC
Not precisely a duplicate, but 152939 puts a stake through this problem.


*** This bug has been marked as a duplicate of 152939 ***