Bug 53521 - Blurry font in unread column
Summary: Blurry font in unread column
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 54429 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-01-28 17:13 UTC by Malte S. Stretz
Modified: 2007-09-14 12:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Screenshot of the KMail window (59.91 KB, image/png)
2003-01-28 17:15 UTC, Malte S. Stretz 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Malte S. Stretz 2003-01-28 17:13:41 UTC 
Version:           1.5 (using KDE 3.1.0)
Installed from:    SuSE
Compiler:          gcc version 2.95.3 20010315 (SuSE)
OS:          Linux (i686) release 2.4.18

Hmmm... I'm not sure if this bug was already reported before; I think I remember to have read something like this the list but can't find it again...

However, the font for unread messages in the new unread column appears blurry to me for big numbers (in this case 500). I'll attach a screenshot and you'll see what I mean. Looks like the numbers are written twice at different offsets or with a different kerning.

This seems to happen with TTFs only. I don't have AA enabled.

Cheers,
Malte
Comment 1 Malte S. Stretz 2003-01-28 17:15:23 UTC 
Created attachment 821 [details]
Screenshot of the KMail window
Comment 2 Carsten Burghardt 2003-01-28 18:21:29 UTC 
Please try if resizing the column helps. It seems that they overlap.
Comment 3 Malte S. Stretz 2003-01-28 18:59:30 UTC 
No, it doesn't and they don't ;-)
Comment 4 Carsten Burghardt 2003-02-10 22:33:54 UTC 
*** Bug 54429 has been marked as a duplicate of this bug. ***
Comment 5 Malte S. Stretz 2003-02-11 10:31:13 UTC 
Sweeet: The patch in bug 54429 fixes this bug. Thanks, Carsten.
Comment 6 Malte S. Stretz 2003-02-12 18:30:48 UTC 
Don't know if it's important but I can close this bug only as WORKSFORME, not 
FIXED. That's the only reason why I reopen it, don't want to see this fix 
being forgotten in the next release.
Comment 7 Carsten Burghardt 2003-02-12 18:39:56 UTC 
The fix is already committed to 3.1 branch and HEAD