Google Web字体vs实际字体文件 - 适用于所有设备。 [英] Google Web-fonts vs Actual font files - For all devices.

问题描述

我正在使用Joesfin Sans，它在Google网页字体上列出，我也有.eot，.svg，.ttf和.woff。
这意味着完全兼容的文件（据我所知）。

我的主要问题是，哪个更好？ Google字体加载速度更快吗？ - 它更兼容？
或者我应该坚持使用这些文件？

解决方案

如果你想快速简单的解决方案，代码并继续前进。 Google经常为他们的服务添加更多的选项/功能。

个人而言，我更喜欢从Google下载文件并手动处理。由于有一个专门用于下载的选择字体的谷歌用户界面（以及阅读许可协议），我相信这是合法使用，但我不是律师。

为什么要这样做？

• 访问Google字体时遇到延迟（200-300ms ）。虽然这并不可怕，但我的大多数服务器环境响应速度更快，字体是页面重要的先决条件。任何打击单独域的好处（即通过浏览器并行到不同的主机）都会丢失。

我已经手动修剪了字体文件以删除所有不需要的字形。 IE8的支持 - 它出现了 .eot doesn'这个结果是一个较小的文件大小。 t总是得到下载。




这些原因大多是轶事，但是我自己管理字体文件已经非常快乐了。 / p>


I'm looking to use Joesfin Sans, It's listed on Google web fonts, I also have the .eot, .svg, .ttf and the .woff. This means full compatibility with the files (as far as I know).

My main question is, which is better? Does Google fonts load faster? - Is it more compatible? Or should I stick with the files?

解决方案

If you want the quick and easy solution, embed the font loader code and move on. Google is frequently adding more options/features to their service.

Personally, I prefer to download the files from Google and work with them manually. Since there is a Google UI specifically for downloading your selected fonts (and from reading the license agreement) I believe this is legitimate use, but I'm not a lawyer.

Why do I do this?

• I have experienced latency when accessing Google fonts (200-300ms). While this isn't terrible, most of my server environments respond faster and a font is an important prerequisite for a page. Any benefit from hitting a separate domain (i.e. parallelization to different hosts by the browser) is lost.

• I've manually trimmed the font files to remove all unwanted glyphs. This results in a smaller file size.

• IE8 support--it appears the .eot doesn't always get downloaded.

These reasons are mostly anecdotal but I have been much happier managing the font files myself.

这篇关于Google Web字体vs实际字体文件 - 适用于所有设备。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！