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 323315 - font resolution and wysiwyg
font resolution and wysiwyg
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Printing
git master
Other All
: Normal normal
: ---
Assigned To: Andreas J. Guelzow
Jody Goldberg
: 106029 152265 (view as bug list)
Depends on: 153549
Blocks:
 
 
Reported: 2005-12-05 22:02 UTC by Pere Pujal
Modified: 2008-09-02 07:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pere Pujal 2005-12-05 22:02:12 UTC
Please describe the problem:
with the defaults of my xserver and gnumeric I have the same problem as Bug 106029
http://bugzilla.gnome.org/show_bug.cgi?id=106029

A workaround is to set the font resolution to a value a little bigger than the
screen resolution set in gnumeric->file->preferences->window/screen.

Is possible to autodetect the resolution?

Steps to reproduce:
gnome-control-center->Font->Details
Change Resolution to 120 dots per inch
Open gnumeric, type something in various rows and do a print preview.
You can see the text cutted horizontally in gnumeric even if it is
nearly right in preview.
If you autoadjust the height of rows in gnumeric, you get an extra amount of
space in the preview.
Close gnumeric and change resolution to 80dpi
Open gnumeric, type something in various rows and autoadjust the rows.
You can see the text right in gnumeric but cutted in preview.


Actual results:


Expected results:


Does this happen every time?


Other information:
I get the best wysiwyg results adjusting screen resolution in gnumeric to a
value a little smaller than the control-center one.

Control-center  gnumeric
120               114
101                96
Comment 1 Andreas J. Guelzow 2007-11-08 22:49:14 UTC
*** Bug 152265 has been marked as a duplicate of this bug. ***
Comment 2 Andreas J. Guelzow 2007-11-08 22:49:54 UTC
*** Bug 106029 has been marked as a duplicate of this bug. ***
Comment 3 Andreas J. Guelzow 2008-09-02 07:45:39 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.