[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Bug#22529: khtml http://axkit.org/ utf-8 encoding problems revisited
From:       Martin Junius <mj () m-j-s ! net>
Date:       2001-03-16 20:23:34
[Download RAW message or body]

Dirk Mueller <mueller@kde.org> writes:

> the problem is that you HAVE a utf8 font installed so it WILL PREFER the 
> utf8 font over the LATIN1 fonts. its very hard for a piece of computer 
> software to JUDGE if the font looks GOOD to the USER. 

OK, got it. So khtml uses probably

-misc-fixed-medium-r-normal--*-*-75-75-c-0-iso10646-1

because that's a unicode font. And the font encoding has priority
over the font name. Right?

As said before, I don't think that this is the right thing <tm> ;-)
The font name should have priority, and that's the way *all* the other
browser are handling it.

More and more sites are using XML or JSP, so we're going to see much
pages with charset=utf-8, which don't display well with konqueror and
the standard X11 fonts.

If you can give me a quick pointer to where this font mapping happens
in the kdelibs/khtml source, I'm willing to look into it and
experiment with alternate schemes.

> > 2. Now visit http://slashdot.org/
> > which displays using the *same* ugly fixed font.
> 
> thats a bug and has been reported several times already, and IIRC from you 
> already too. 

Yep, but I didn't find a easy to reproduce combination of URLs
then. And you closed the bug. ;-)

Anyway, keep up the good work on konqueror/khtml!

Martin

[prev in list] [next in list] [prev in thread] [next in thread]