Bug 79814 - Wish: Be able to specify separate fonts for different encodings
Summary: Wish: Be able to specify separate fonts for different encodings
Status: RESOLVED DUPLICATE of bug 39185
Alias: None
Product: kcontrol
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Daniel Molkentin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-17 14:38 UTC by Stian Haklev
Modified: 2004-05-24 00:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stian Haklev 2004-04-17 14:38:16 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    Debian testing/unstable Packages
OS:          Linux

My main operating languages are Norwegian and English, yet I frequently use Chinese (simplified) webpages, write and receive email etc. At times, I also use cyrillics. In Firefox it is possible to specify the fonts for all the different encodings separately, ie. gb2312 - please use this font, cyrillics, please use this font... would something like this be possible for Kcontrol (mainly applicable in Konqueror and Kmail for me)? Currently, you can choose only one font - obviously a Chinese font is selected automatically for viewing Chinese fonts, but my system has many Chinese fonts and the one automatically selected is not the one I would like to use. (Regardless of whether there is a hack for this in some conf file somewhere, a much more elegant solution would be to follow Firefox' example). Also, perhaps specify which encodings should be anti-aliased (if I remember correctly, this does not look good on Chinese fonts).
Comment 1 Stian Haklev 2004-05-22 21:18:12 UTC
Deleted in favour of bug 39185.
Comment 2 Datschge 2004-05-24 00:24:03 UTC
It doesn't work but is a duplicate bug. (Changing WORKSFORME to DUPLICATE requires me to reopen this temporarily, sorry.)
Comment 3 Datschge 2004-05-24 00:24:44 UTC
See comment #2.

*** This bug has been marked as a duplicate of 39185 ***