(*** This bug was imported into bugs.kde.org ***) Package: Konqueror Version: 2.0 Severity: wishlist I would like to make suggestion to organize Font settings in Konqueror (KHTML) by Encoding (and remain previous Font settings as Global/Default) I found that implementation like in Mozilla (or even old Netscape) is very useful. Netscape: --------- Encoding: < > Variable width font: < > Fixed width font: < > Mozilla: ------------------ Fonts for: <Western> Cyrillic etc. Variable width fonts: Serif< > Sans-Serif< > default type: [x] Serif [ ] SansSerif Fixed-width fonts: Monospace < > ------------------ I frequaently switch between sites with different encodings and some fonts which are suitable for Latin (ISO-8859-1) encoding are very bad for Cyrillic (or don't have Cyrillic glyphs at all) This feature will be very useful for countries with different alphabets and simultaneously-used different encodings (like koi-8r CP1251 UTF-8). -- Vadim Plessky http://kde2.newmail.ru (English) http://kde2.newmail.ru/index_rus.html (Russian)
To clarify, it seems that the OP wants each differently encoded bit of text to appear in a different font. I think that the OP is confusing encodings with languages. So far as I know, a webpage can only contain one encoding for the entire document, specified in the page response header like so: Content-Type: text/html; charset=utf-8 Therefore, the bug is invalid. However, it may be nice to have each language displayed in a different font, even if they are in the same encoding. How to implement that is beyond me.
I am updating the title to make it not Konqueror-specific. Also, I suppose that the request could be implemented by checking the unicode codepoints for each character. Neutral characters, such as numbers, would have to either default to a specific font or could take the font of the two non-neutral characters surrounding them. I am very much in favor of this bug as my native language has no folnt which also looks good in English, yet English has no font which good in my native language. I am currently using Microsoft's Tahoma font as a least-worse-case workaround.
Is it a requirement to be able to have them per encoding or just about per script used? In the latter case, it is actually a duplicate of bug 39185.
I would say that bug #39185 is rather a dupe of this one! But as it is further developed, I'll mark this as the dupe. Thanks for taking a look, Christoph! *** This bug has been marked as a duplicate of bug 39185 ***