Closed
Bug 93207
Opened 23 years ago
Closed 18 years ago
[xlib] xlib mix build text appears really bad :-(
Categories
(Core Graveyard :: GFX: Xlib, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: timeless, Assigned: roland.mainz)
References
()
Details
Attachments
(6 files)
the dom stuff works great (albeit slowly), but the text just isn't readable :-(
picture.
Comment 2•23 years ago
|
||
Comment 3•23 years ago
|
||
it looks perfectly fine here.
You need to install some non-suck fonts, I guess.
I suggest Microsoft Web Fonts pack from http://www.microsoft.com/typography or
something like that.
martin: this is a xlib bug, not GTK.
GTK screenshots don't do any good here.
Comment 8•23 years ago
|
||
How does gtk-mozilla or ns 4.x look like on mix?
Maybe attach from xlsfonts run from mix would help.
Comment 10•23 years ago
|
||
I think mix misses some fonts and substitute fonts sucks. I guess this is
wontfix/invalid.
Try installing some more fonts.
Reporter | ||
Comment 11•23 years ago
|
||
Reporter | ||
Comment 12•23 years ago
|
||
nc4 looks much better than gtk or xlib on the same xserver. I know mix's font
selection sucks, but i don't see a reason we shouldn't be able to render the
page as nicely as nc4 (or at least as nicely as gtk).
Blocks: 79119
Assignee | ||
Comment 13•23 years ago
|
||
I'll hope bug 94327 ("When there are multiple fonts with different foundry names
but the same family name moz should pick the best fit based on width, weight and
available size") will fix this ...
Depends on: 94327
Summary: xlib mix build text appears really bad :-( → [xlib] xlib mix build text appears really bad :-(
Assignee | ||
Comment 14•23 years ago
|
||
bug 94327 was checked in yesterday.
timeless:
Do you still have font problems on the XMIX Xserver ?
Comment 15•18 years ago
|
||
Gtk1/xlib widget code has been removed on trunk.
-> WONTFIX
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•