Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 183252 - Text spacing wrong around underlined characters
Text spacing wrong around underlined characters
Product: Fedora
Classification: Fedora
Component: pango (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Behdad Esfahbod
Depends On:
  Show dependency treegraph
Reported: 2006-02-27 15:03 EST by Rudi Chiarito
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-07-11 10:29:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Screenshot with overlapping glyphs (39.24 KB, image/png)
2006-02-27 15:03 EST, Rudi Chiarito
no flags Details

  None (edit)
Description Rudi Chiarito 2006-02-27 15:03:39 EST
Description of problem:
Something seems to be wrong with text rendering. I didn't notice this on FC4. It
might have something to do with Cairo. I am setting the component to Cairo, but
feel free to reassign as necessary.

I am attaching a picture which shows how glyphs touch each other. It happens
around underlined keyboard shortcut characters. Look for example at the text
'Subpixel'. I am using Nimbus Sans, but I have seen the same with other fonts as

Version-Release number of selected component (if applicable):

This is a FC4 system updated to FC5T3 and then today's Rawhide updates.
Comment 1 Rudi Chiarito 2006-02-27 15:03:40 EST
Created attachment 125342 [details]
Screenshot with overlapping glyphs
Comment 2 Rudi Chiarito 2006-02-27 15:22:22 EST
Comment on attachment 125342 [details]
Screenshot with overlapping glyphs

It's an image, not text
Comment 3 Matthias Clasen 2006-06-20 01:15:34 EDT
Reassigning pango bugs to Behdad.
Comment 4 Rudi Chiarito 2006-07-11 10:29:37 EDT
Seems to be fixed in Raw Hide now, can't tell which version of which package
solved the issue.

Note You need to log in before you can comment on or make changes to this bug.