The antialias checkbox is disabled (and selected) for fonts that do not have bitmaps and therefore must be rendered with (antialiased) outlines. Menlo is one such font.
Having recently installed Lion in a VirtualBox, I'm seeing the same problem. I like nice bitmapped fonts for text editing and terminals.
My take on what's going on is that the Antialias text button is actually overloaded with two meanings.
For some bitmapped fonts, it really seems to really turn anti-aliasing on and off. Looking closely at the characters while switching back and forth, you can see that the anti-aliased font is pretty much pixel-for-pixel identical to the bitmapped one, only blurry.
But for some other fonts, it looks as if it selects between an anti-aliased vector font and a hand-made, bitmapped font. E.g. check out Microsoft Sans Serif.
I suspect that the button is disabled in situations when a only a vector font exists.
The ideal situation is when there are separate fonts.
If only a bitmapped font exists, it's okay if the anti-aliasing button works because anti-aliasing a bitmapped font can look passable.
If only a vector font exists, turning off anti-aliasing (especially at those sizes) would look like garbage, so it makes sense to disable the feature.
Sounds like a reasonable hypothesis, anyway.
I'm puzzled, though, why the application does not come configured with a sane default: a good-looking, crisp bitmapped font.
发布评论
评论（3）
对于没有位图的字体，抗锯齿复选框被禁用（并选中），因此必须使用（抗锯齿）轮廓进行渲染。 Menlo 就是这样一种字体。
The antialias checkbox is disabled (and selected) for fonts that do not have bitmaps and therefore must be rendered with (antialiased) outlines. Menlo is one such font.
显然这是 Menlo 的一个已知问题： http:// damieng.com/blog/2009/08/29/first-impressions-of-snow-leopard（搜索Menlo）
只要这不是我的操作系统或配置的问题，那么我感觉好一点关于这个。我想我现在会留在摩纳哥......
Apparently this is a known issue with Menlo: http://damieng.com/blog/2009/08/29/first-impressions-of-snow-leopard (search for Menlo)
As long as it's not an issue with my OS or configuration somehow, then I feel a little better about this. Guess I'll stick to Monaco for now...
最近在 VirtualBox 中安装了 Lion，我遇到了同样的问题。我喜欢用于文本编辑和终端的漂亮位图字体。
我对正在发生的事情的看法是，
Antialias text按钮实际上有两种含义。对于某些位图字体，它似乎确实可以打开和关闭抗锯齿功能。在来回切换时仔细观察字符，您可以看到抗锯齿字体与位图字体几乎逐像素相同，只是模糊。
但对于其他一些字体，它看起来好像是在抗锯齿矢量字体和手工制作的位图字体之间进行选择。例如，查看 Microsoft Sans Serif。
我怀疑在仅存在矢量字体的情况下该按钮被禁用。
理想的情况是有单独的字体。
如果仅存在位图字体，则抗锯齿按钮起作用也没关系，因为对位图字体进行抗锯齿看起来还不错。
如果仅存在矢量字体，则关闭抗锯齿功能（尤其是在这些尺寸下）看起来就像垃圾，因此禁用该功能是有意义的。
无论如何，听起来像是一个合理的假设。
不过，我很困惑，为什么应用程序没有配置合理的默认值：美观、清晰的位图字体。
Having recently installed Lion in a VirtualBox, I'm seeing the same problem. I like nice bitmapped fonts for text editing and terminals.
My take on what's going on is that the
Antialias textbutton is actually overloaded with two meanings.For some bitmapped fonts, it really seems to really turn anti-aliasing on and off. Looking closely at the characters while switching back and forth, you can see that the anti-aliased font is pretty much pixel-for-pixel identical to the bitmapped one, only blurry.
But for some other fonts, it looks as if it selects between an anti-aliased vector font and a hand-made, bitmapped font. E.g. check out Microsoft Sans Serif.
I suspect that the button is disabled in situations when a only a vector font exists.
The ideal situation is when there are separate fonts.
If only a bitmapped font exists, it's okay if the anti-aliasing button works because anti-aliasing a bitmapped font can look passable.
If only a vector font exists, turning off anti-aliasing (especially at those sizes) would look like garbage, so it makes sense to disable the feature.
Sounds like a reasonable hypothesis, anyway.
I'm puzzled, though, why the application does not come configured with a sane default: a good-looking, crisp bitmapped font.