[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:       mj () m-j-s ! net
Date:       2001-03-16 16:30:22
[Download RAW message or body]

Package: khtml
Version: KDE 2.1.0 
Severity: normal
Installed from:    Red Hat Linux 
Compiler:          gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
OS:                Linux 2.2.17-8smp i686
OS/Compiler notes: 

Environment: KDE 2.1, X11 installed with the standard fonts, no additional fonts or \
utf-8 fonts installed.

As typically X11 installation donīt have any unicode-fonts installed, the things \
below are a real problem.


1. Visit http://axkit.org/ with encoding set to "Auto"
This will display the page using the ugly fixed font, which seems to be the fallback. \
The pageīs mime type is

Content-Type: text/html; charset=utf-8

IMHO khtml should recode utf-8 -> iso-8859-1 (or whatever konqueror is configured to \
use for the fonts) when no fonts with unicode encoding are installed.

2. Now visit http://slashdot.org/
which displays using the *same* ugly fixed font. slashdot's mime type is

Content-Type: text/html

Obviously the missing charset= causes khtml to reuse the charset=utf-8 from \
axkit.org.

Manually switching the encoding of both pages to "iso-8859-1" makes them both use the \
correct font.

And of course accessing slashdot without axkit.org on the way works flawlessly. ;-)

Martin


(Submitted via bugs.kde.org)
(Called from KBugReport dialog)


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