个人觉得XFT2是firefly的精华

monte

其他的都是次要的

kazuyuki

但好像没有那个包需要安装xft2啊.我只用kde,安装了Xfree,Qt,fontconfig后就能很好地显示中文了.xft2到底又什么用?能说明一下吗?

Jockey

最初由 kazuyuki 发表
但好像没有那个包需要安装xft2啊.我只用kde,安装了Xfree,Qt,fontconfig后就能很好地显示中文了.xft2到底又什么用?能说明一下吗?

fontconfig和xft的关系，你不知道么？我也不清楚:p

zzswang

最初由 kazuyuki 发表
但好像没有那个包需要安装xft2啊.我只用kde,安装了Xfree,Qt,fontconfig后就能很好地显示中文了.xft2到底又什么用?能说明一下吗?

好像xft是为了补充XFree86的,如果自己升级了加过patch的xFree就不用xft了

Jockey

看看fontconfig.org官方的解释：

About Xft

The current version of Xft (2.0) provides a client-side font API for X applications. It uses Fontconfig to select fonts and the X protocol for rendering them. When available, Xft uses the Render extension to accelerate text drawing. When Render is not available, Xft uses the core protocol to draw client-side glyphs. This provides completely compatible support of client-side fonts for all X servers.

Drawing anti-aliased text with the core protocol involves fetching pixels from the destination, merging in the glyphs and shipping them back. This can be a performance problem when the latency between client and server is high. Drawing non-AA text with the core protocol can be done by just sending the glyphs from the client to the server. This eliminates any latency effects and makes rendering speed depend only on bandwidth. Careful protocol selection can make the bandwidth scale linearly with the pixel size of the glyphs, so performance is acceptable, even with relatively large glyphs.

When using legacy X servers (those without Render support) across a network, disabling anti-aliased text will improve text performance so that applications are reasonably usable even if completely dependent on client-side fonts.

Jockey

看看fontconfig.org官方的解释：

About Xft

The current version of Xft (2.0) provides a client-side font API for X applications. It uses Fontconfig to select fonts and the X protocol for rendering them. When available, Xft uses the Render extension to accelerate text drawing. When Render is not available, Xft uses the core protocol to draw client-side glyphs. This provides completely compatible support of client-side fonts for all X servers.

Drawing anti-aliased text with the core protocol involves fetching pixels from the destination, merging in the glyphs and shipping them back. This can be a performance problem when the latency between client and server is high. Drawing non-AA text with the core protocol can be done by just sending the glyphs from the client to the server. This eliminates any latency effects and makes rendering speed depend only on bandwidth. Careful protocol selection can make the bandwidth scale linearly with the pixel size of the glyphs, so performance is acceptable, even with relatively large glyphs.

When using legacy X servers (those without Render support) across a network, disabling anti-aliased text will improve text performance so that applications are reasonably usable even if completely dependent on client-side fonts.

kazuyuki

那是不是在firefly套件中装了xft2就可以不要装xfree的升级了?

monte

我就是这样的