Closed
Bug 78253
Opened 23 years ago
Closed 23 years ago
TrueType font widths calculated too small in X
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
People
(Reporter: corydodt, Assigned: asa)
References
()
Details
Attachments
(1 file)
94.74 KB,
image/jpeg
|
Details |
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) BuildID: 2001040912 The rendering engine appears to be displaying TrueType fonts at width W and displaying them at width W*(1.2) approximately. The result is that text overlaps at font-change boundaries, and at the screen boundary, truetype fonts spill off the right side, beyond the reach of the scrollbar. This renders many pages completely unreadable. Reproducible: Always Steps to Reproduce: 1. Ensure that you have truetype fonts configured and working. The fonts I'm using were imported from Windows 2000. 2. Load http://galeon.sourceforge.net Actual Results: The text displays overlapping. For example the word "some" and the link "screenshots" are rendered in the same horizontal location, so that the s's almost overlap. On many pages this is completely unreadable. Expected Results: The page should contain readable text. At first I thought it was just the Arial font as described in <a href http://bugzilla.mozilla.org/show_bug.cgi?id=46415>bug 46415</a>. However, I can clearly see that it's not the same thing, because I actually have the ult1mo fonts installed as well; when I remove my TrueType fonts, I can see the tiny, ugly ult1mo fonts instead. So I tried aliasing out my Arial fonts to Georgia fonts; I got overlapping Georgia instead of overlapping Arial. This doesn't happen in Windows 2000 with build id 20010215 and the same fonts.
Comment 2•23 years ago
|
||
Cory Dodt, what version of X are you using? Are you using a font server? There are already some bugs along these lines reported about mozilla and XFree 4.0.3 (note that other versions of XFree work correctly).
XFree 4.0.3, with xfs. I have both the type1 and the freetype font modules loading. Damn, what bug number is that?
Never mind I finally found it myself: bug 59915. Closing as dupe. Looking at the screenshot that was posted there, this is definitely the same problem. *** This bug has been marked as a duplicate of 59915 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•