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 581350 - zoom values in status bar use unavailable unicode character (windows GTK+ engine)
zoom values in status bar use unavailable unicode character (windows GTK+ eng...
Status: RESOLVED DUPLICATE of bug 63633
Product: GIMP
Classification: Other
Component: User Interface
2.6.6
Other All
: Normal trivial
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2009-05-04 18:32 UTC by Henry
Modified: 2009-05-04 23:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Henry 2009-05-04 18:32:37 UTC
Please describe the problem:
The zoom values in the status bar show the hexadecimal value of an unavailable unicode character instead of a small empty space between the number and percent sign, unless Lucida Sans Unicode font is defined as the Windows desktop font, which contains a full unicode character set. No other standard fonts in Windows contain the character.

Steps to reproduce:
1. standard installation of GIMP with "MS-Windows engine for GTK+"
2. start GIMP and open a file
3. strange character between number and percent, instead of white space


Actual results:


Expected results:
Do not use a character for white space that is normally not in any Windows font

Does this happen every time?
Yes. Also on all other Windows XP systems checked.

Other information:
Workaround is to install GIMP in windows without the MS-Windows engine for GTK+
 - choose "Customize" when installing Gimp
 - uncheck "MS-Windows engine for GTK+"
The problem is not present if the Windows look-and-feel is not installed.
Comment 1 Michael Schumacher 2009-05-04 23:39:52 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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