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 777881 - Tops of letters cut off in block text
Tops of letters cut off in block text
Status: RESOLVED DUPLICATE of bug 757392
Product: GIMP
Classification: Other
Component: Tools
2.8.18
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2017-01-29 01:04 UTC by bachigaiheart
Modified: 2017-03-08 19:31 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Text in AR DECODE font (75.04 KB, image/png)
2017-01-29 01:04 UTC, bachigaiheart 		Details

Description bachigaiheart 2017-01-29 01:04:33 UTC 
Created attachment 344469 [details]
Text in AR DECODE font

Similar to a bug already reported, but I find when using font 'AR DECODE' in block and block with italics the tops of some letters are cut off. The first letter used is ok until you add more letters. Thanks for reading.
Comment 1 Jehan 2017-02-02 14:42:12 UTC 
Yes this is similar to bug 776518. There is likely a problem in how we compute the box around letters.

In the other bug, I was noticing that when playing with resolution, I could sometimes make the problem disappear.
Could you tell us what is your current PPI resolution, and if changing it affects the issue somehow?
Comment 2 bachigaiheart 2017-02-02 17:14:37 UTC 
(In reply to Jehan from comment #1)
> Yes this is similar to bug 776518. There is likely a problem in how we
> compute the box around letters.
> 
> In the other bug, I was noticing that when playing with resolution, I could
> sometimes make the problem disappear.
> Could you tell us what is your current PPI resolution, and if changing it
> affects the issue somehow?

Hi, I have tried changing ppi from 72 to 300, but unfortunately it has not helped the issue. Thanks.
Comment 3 Michael Natterer 2017-03-08 19:31:33 UTC 
I'm pretty sure it's bug 757392.

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