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 702096 - Unable to display Wingdings in Text Tool
Unable to display Wingdings in Text Tool
Status: RESOLVED DUPLICATE of bug 675781
Product: GIMP
Classification: Other
Component: Tools
2.8.4
Other Windows
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-06-12 14:15 UTC by northpolelars
Modified: 2013-06-12 20:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description northpolelars 2013-06-12 14:15:30 UTC
I'm not a graphics guy, but trying to create a simple icon for work. I want to use one of the Wingdings characters and specify a color. The character is not displaying in Wingdings, but Sans.

Steps to re-create the issue:

* File -> New...
* Set Width 20, Height 20 
* Open Advanced Options, change Fill With to Transparency
* Click OK
* In the Toolbox, click on the Text Tool.
* Type in Windgings in the font field, set size to 19. Justify Center.
* Click the color button and set the color.
* Open Character Map in Windows, set Wingdings as the font, and select the character you want to copy, in my case Ý, and click Copy.
* Click in the 20x20 area of the new icon (with the Text Tool still highlighted)
* Type Ctrl-V to past the character into the field.

The character displays as Ý, not the round circle with the up arrow. 

Also oddly, the text cannot be moved with the Move Tool, but only by dragging the 4 corners of the text object around. 

Thanks,
Larry

PS. Running Windows 7 Enterprise 64 bit Service Pack 1 on Intel Core i7 with 8GB RAM.
Comment 1 Michael Schumacher 2013-06-12 20:57:54 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 bug 675781 ***