有些程序的字体为什么设置不了？

070 · 发表于 2008-10-7 16:44:34

我的字体是这样设置的。

可是有些地方字体仍然很模糊，很小，比如scim系统托盘的右键菜单，yast和Amarok

该如何设置呢？

meto · 发表于 2008-10-7 18:36:41

我基本都是设置成统一字体的n_n

070 · 发表于 2008-10-7 19:40:36

貌似跟固定字体dpi有关。。。

yourfriend · 发表于 2008-10-7 20:01:42

楼主的显示器是什么牌子型号？
除了控制中心设置字体，还有qt setting 里面的字体。
圆整字体边角用轻微那一个。
字体最好换一个，雅黑不错。

最好设置一下DPI，这要根据你的显示器型号。
我还在/etc/X11/Xresources最后加入的一行

Xft.dpi:96

复制代码

如上设置还不行的话，我这里有个启动次像素平滑的文件，并且我这里设了96dpi

cat /etc/fonts/local.conf
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<match target="pattern" >
<edit name="dpi" mode="assign" >
<double>96</double>
</edit>
</match>
<!--
Using hinting=true, hintstyle=hintfull and antialias=true
is a good default for most fonts.
Match on "pattern" for the default, not on "font" to make
it easier to override the default using FcPatternDel()
and FcPatternAdd...() (see bugzilla #104365).
-->
<match target="pattern">
<edit name="hinting">
<bool>true</bool>
</edit>
<edit name="hintstyle">
<const>hintfull</const>
</edit>
<edit name="antialias">
<bool>true</bool>
</edit>
</match>
<!--
Set autohinter=true as the default, then add exceptions for certain fonts.
Match on "font" here, not on "pattern" because of bug #118131 comment #93.
(If an autohint value is set in pattern, OpenOffice 2.1 will use that even
if there are fontconfig rules matching on "font" which should override it
again). This doesn't cause any problems for Cairo/Gnome (see bug #104365)
because Cairo/Gnome don't try to change the autohint value anyway.
-->
<match target="font">
<edit name="autohint">
<bool>true</bool>
</edit>
</match>
<!--
Switch off the autohinter for PostScript fonts (Type 1 and OpenType CFF)
because using the PostScript hinting usually looks better than using
the autohinter.
-->
<match target="font">
<test name="fontformat">
<string>Type 1</string>
<string>CFF</string>
</test>
<edit name="autohint">
<bool>true</bool>
</edit>
</match>
<!--
TrueType Fonts which have high quality byte code interpreter
instructions can look very good in even in small sizes when using
the byte code interpreter (autohint=false). This is true
both with and without anti-aliasing.
In black and white (antialias=false) the results when rendering
with the byte code interpreter may even look as good as high quality
bitmap fonts.
On the other hand, some low quality TrueType Fonts do not have
byte code interpreter instructions at all or only very bad byte
code and may look better when the autohinter is used.
(See "FreeSans" for example, it looks better with the
autohinter which is especially obvious if anti-aliasing is off).
-->
<!--
Switch off the autohinter for TrueType fonts in order
to use the byte code interpreter.
-->
<match target="font">
<test name="fontformat">
<string>TrueType</string>
</test>
<edit name="autohint">
<bool>true</bool>
</edit>
</match>
<!--
Switch on the autohinter for a few TrueType fonts which
have no byte code or very bad byte code and look better
with the autohinter:
But see also bug #215602 for many fonts the autohinter
seriously distorts the metrics so badly that
even the digits which should be monospaced are not
monospaced at all anymore.
Because of this problem, better don't switch on
the autohinter for
Sazanami
IPA
DejaVu Sans Light
DejaVu Sans Condensed
DejaVu Serif Condensed
FreeSans
FreeSerif
FreeMono
and other fonts with similar problems until this is solved
in the autohinter.
-->
<match target="font">
<test name="fontformat">
<string>TrueType</string>
</test>
<test name="family">
<string>Microsoft YaHei</string>
<string>Vera Sans YuanTi</string>
<string>Vera Sans YuanTi Mono</string>
<string>MS PGothic</string>
<string>MS UI Gothic</string>
<string>MS Mincho</string>
<string>MS PMincho</string>
<string>HGPSoeiKakupoptai</string>
<string>HGSGothicE</string>
<string>HGSGothicM</string>
<string>HGKyokashotai</string>
<string>HGSSoeiKakugothicUB</string>
<string>HGPGothicB</string>
<string>HGPGothicE</string>
<string>HGPGothicM</string>
<string>HGSKyokashotai</string>
<string>HGMaruGothicMPRO</string>
<string>HGPSoeiKakugothicUB</string>
<string>HGMinchoL</string>
<string>HGPMinchoL</string>
<string>HGMinchoB</string>
<string>HGPMinchoB</string>
<string>HGSMinchoB</string>
<string>HGMinchoE</string>
<string>HGPMinchoE</string>
<string>HGSMinchoE</string>
<string>HGSoeiKakugothicUB</string>
<string>HGGyoshotai</string>
<string>HGPGyoshotai</string>
<string>HGSGyoshotai</string>
<string>HGSoeiKakupoptai</string>
<string>HGSSoeiPresenceEB</string>
<string>HGPSoeiPresenceEB</string>
<string>HGGothicB</string>
<string>HGGothicE</string>
<string>HGGothicM</string>
<string>HGSoeiPresenceEB</string>
<string>HGPKyokashotai</string>
<string>HGSSoeiKakupoptai</string>
<string>HGSeikaishotaiPRO</string>
<string>TLKyokashotai</string>
<string>TLMincho</string>
<string>TLPMincho</string>
<string>TLPGothic</string>
<string>TLPKyokashotai</string>
<string>TLMarugothicM</string>
<string>TLGyoshotai</string>
<string>TLPGyoshotai</string>
<string>TLSGyoshotai</string>
<string>TLPMarugothicM</string>
<string>TLSMarugothicM</string>
<string>TLSKyokashotai</string>
<string>TLGothic</string>
</test>
<edit name="autohint">
<bool>true</bool>
</edit>
</match>
<!--
The following rule sets up black and white rendering with
the byte code interpreter for a small list of fonts which
are known to have good byte code and give bitmap quality
results at small sizes.
The pixelsize limit is set to '0' though, which effectively
disables this rule by default because most users don't like
that bitmap look and feel.
If you like a bitmap look and feel of your desktop,
copy this rule into your ~/.fonts.conf file and replace the '0'
with non-zero pixelsize limit. Using '18' as the pixelsize
limit is a good choice if you have the fonts in this list installed
and like a bitmap look and feel.
-->
<match target="font">
<test name="family">
<string>Microsoft YaHei</string>
<string>Vera Sans YuanTi</string>
<string>Vera Sans YuanTi Mono</string>
<string>Andale Mono</string>
<string>Arial</string>
<string>Comic Sans MS</string>
<string>Georgia</string>
<string>Impact</string>
<string>Trebuchet MS</string>
<string>Verdana</string>
<string>Courier New</string>
<string>Times New Roman</string>
<string>Tahoma</string>
<string>Webdings</string>
<string>Albany AMT</string>
<string>Thorndale AMT</string>
<string>Cumberland AMT</string>
<string>Andale Sans</string>
<string>Andy MT</string>
<string>Bell MT</string>
<string>Monotype Sorts</string>
</test>
<test name="pixelsize" compare="less_eq">
<double>0</double>
</test>
<edit name="autohint">
<bool>true</bool>
</edit>
<edit name="antialias">
<bool>true</bool>
</edit>
</match>
<!--
Some CJK fonts require the byte code interpreter to be rendered correctly.
These are composite fonts which store components and composing information
and compose the glyphs on the fly using the hinting instructions.
For all such fonts we switch off the autohinter here.
When "autohint" is set to "false", the byte code interpreter will
be used if it has been enabled at all when compiling freetype2.
The Chinese fonts "MingLiu" and "PMingLiU" used to belong to the fonts
which absolutely require the byte code interpreter to be rendered
correctly.
But apparently the new versions of "MingLiU" and "PMingLiU" from Windows
Vista are rendered correctly without the byte code interpreter.
-->
<match target="font">
<test name="family">
<string>Microsoft YaHei</string>
<string>MingLiU</string>
<string>Vera Sans YuanTi</string>
<string>Vera Sans YuanTi Mono</string>
<string>PMingLiU</string>
</test>
<edit name="autohint">
<bool>true</bool>
</edit>
</match>
<!--
Hinting for CJK fonts in freetype doesn't yet work as well as for Latin fonts.
Recently the autohinter in in freetype has been improved for CJK fonts
a lot but it is still not perfect. Therefore one might want to switch
off the autohinter for CJK fonts.
This can be achieved by using the following rule:
<match target="font">
<test name="lang" compare="contains">
<string>ja</string>
<string>zh</string>
<string>ko</string>
</test>
<edit name="autohint">
<bool>true</bool>
</edit>
</match>
-->
<!--
for some Bengali fonts (e.g. "Mukti Narrow"), the autohinter works well
with the patch from http://www.kde.gr.jp/~akito/patch/freetype2/2.1.7
applied. But for "Likhan" it still doesn't work that well
(look how the "matra" lines at the top line up). Therefore, switch
off the autohinter for the "Likhan" font:
-->
<match target="font">
<test name="family">
<string>Likhan</string>
<string>Microsoft YaHei</string>
<string>Vera Sans YuanTi</string>
<string>Vera Sans YuanTi Mono</string>
</test>
<edit name="autohint">
<bool>true</bool>
</edit>
</match>
</fontconfig>

复制代码

nhadct · 发表于 2008-10-8 22:31:13

这是因为yast之类的程序是由qt设置的，不是由kde控制中心设置。
qt字体以通过命令qtconfig设置，在终端下运行qtconfig，在Font选项卡中可以设置字体，Point size设置字体的大小，默认是6，所以造成yast程序的字体小而且虚，一般改成10就可以了。

注意：yast实际是由root用户允许的，所以设置yast的字体需要root用户执行qtconfig设置。

hrgstephen · 发表于 2008-10-9 09:44:27

如下可改全局字体(包括非 qt 程序如 firefox 及 gimp)：
$su
#vi /etc/fonts/suse-post-user.conf
在<family>serif</family>以及<family>sans-serif</family>中把你要用的字体排到第一位，在<family>monospace</family>中把你要用的等宽字体排到第一位
比如我的：（只加了两个雅黑，用的英文系统，故名字为Microsoft YaHei,米改等宽字体，貌似默认就用的dejavs sans momo）
<alias>
<family>serif</family>
<prefer>
<family>Microsoft YaHei</family>
<family>Times New Roman</family>
<family>Thorndale AMT</family>
.......
</prefer>
</alias>
<alias>
<family>sans-serif</family>
<prefer>
<family>Microsoft YaHei</family>
<family>Arial</family>
<family>Albany AMT</family>
......
</prefer>
</alias>

yourfriend · 发表于 2008-10-9 09:53:04

奇怪kde不把Vera Sans YuanTi Mono 列为等宽字体。gnome中则可以。

snailrun · 发表于 2008-10-10 17:04:00

我碰到过几次是因为显卡驱动没装上

ashizl · 发表于 2008-10-10 21:41:28

Post by nhadct;1891877
这是因为yast之类的程序是由qt设置的，不是由kde控制中心设置。
qt字体以通过命令qtconfig设置，在终端下运行qtconfig，在Font选项卡中可以设置字体，Point size设置字体的大小，默认是6，所以造成yast程序的字体小而且虚，一般改成10就可以了。

注意：yast实际是由root用户允许的，所以设置yast的字体需要root用户执行qtconfig设置。

应该是这样的！

		自动登录	找回密码
密码			注册

有些程序的字体为什么设置不了？

本帖子中包含更多资源

本帖子中包含更多资源

本帖子中包含更多资源