Not too sure if this has been asked before with specifics to Locally Available fonts.
不太确定之前是否曾询问过本地可用字体的细节。
I'm loading two font stacks on my local development site
我在我的本地开发站点上加载了两个字体堆栈
// font stacks - http://cssfontstack.com/
"Arial", "Helvetica Neue", Helvetica, sans-serif;
"Georgia", Cambria, Times New Roman, Times, serif;
The Arial font stack behaves as expected however the Georgia font stack skips Georgia and Cambria on Chrome. Firefox displays both exactly as expected. Both fonts exist on my local machine... Does anyone have any reasons why this would be happening?
Arial字体堆栈的行为与预期的一样,但Georgia字体堆栈在Chrome上跳过Georgia和Cambria。 Firefox完全按预期显示。这两种字体都存在于我的本地机器上......有没有人有任何理由为什么会发生这种情况?
1 个解决方案
#1
0
I think you see result of Issue 421305 @ Chromium http://code.google.com/p/chromium/issues/detail?id=421305
我想你看到了问题421305 @ Chromium的结果http://code.google.com/p/chromium/issues/detail?id=421305
scottmg@chromium.org says: "If DirectWrite fails to enumerate the system font collection (corrupt font, etc.), or we exceed 1750 fonts, we abort and load a very small set that does not include Verdana or Georgia. Obviously this is a hack. Shrikant has a patch out to fix this properly. In the interim, the only quick fixes are to reduce the number of fonts in %WINDOWS%\Fonts below 1750, or go to chrome://flags and disable DirectWrite."
scottmg@chromium.org说:“如果DirectWrite无法枚举系统字体集合(损坏的字体等),或者我们超过1750种字体,我们会中止并加载一个不包括Verdana或Georgia的非常小的集合。显然这是一个hack.Shrikant有一个补丁来正确解决这个问题。在此期间,唯一的快速修复方法是减少1750以下%WINDOWS%\ Fonts中的字体数量,或者转到chrome:// flags并禁用DirectWrite。“
The problem affects Chrome 38 and AFAIK last Opera with webkit core too... confirmed are issues with Georgia, Verdana, Tahoma, Calibri, Trebuchet and other locally hosted fonts.
这个问题影响了Chrome 38和AFAIK上一次使用webkit核心的Opera ...确认是Georgia,Verdana,Tahoma,Calibri,Trebuchet和其他本地托管字体的问题。
It should be fixed in Chrome 39+
它应该在Chrome 39+中修复
#1
0
I think you see result of Issue 421305 @ Chromium http://code.google.com/p/chromium/issues/detail?id=421305
我想你看到了问题421305 @ Chromium的结果http://code.google.com/p/chromium/issues/detail?id=421305
scottmg@chromium.org says: "If DirectWrite fails to enumerate the system font collection (corrupt font, etc.), or we exceed 1750 fonts, we abort and load a very small set that does not include Verdana or Georgia. Obviously this is a hack. Shrikant has a patch out to fix this properly. In the interim, the only quick fixes are to reduce the number of fonts in %WINDOWS%\Fonts below 1750, or go to chrome://flags and disable DirectWrite."
scottmg@chromium.org说:“如果DirectWrite无法枚举系统字体集合(损坏的字体等),或者我们超过1750种字体,我们会中止并加载一个不包括Verdana或Georgia的非常小的集合。显然这是一个hack.Shrikant有一个补丁来正确解决这个问题。在此期间,唯一的快速修复方法是减少1750以下%WINDOWS%\ Fonts中的字体数量,或者转到chrome:// flags并禁用DirectWrite。“
The problem affects Chrome 38 and AFAIK last Opera with webkit core too... confirmed are issues with Georgia, Verdana, Tahoma, Calibri, Trebuchet and other locally hosted fonts.
这个问题影响了Chrome 38和AFAIK上一次使用webkit核心的Opera ...确认是Georgia,Verdana,Tahoma,Calibri,Trebuchet和其他本地托管字体的问题。
It should be fixed in Chrome 39+
它应该在Chrome 39+中修复