Font Embedding on the Web

IE8 팀 블로그 — Wed, 25 Mar 2009 11:08:41 GMT

안녕하세요 Bill Hill 입니다. 웹에서의 폰트를 인쇄물과 같은 수준으로 높이기 위해 노력 중 입니다. 이번 주에 커다란 진전이 있었습니다. 미국의 유력 폰트 배급업체가 Embedded

Trustworthy Browsing with IE8: Summary

IEBlog — Tue, 02 Dec 2008 02:37:04 GMT

Back in June, Dean Hachamovitch kicked off a series of blog posts explaining how the IE team approached

re: Font Embedding on the Web

thacker — Mon, 04 Aug 2008 00:48:41 GMT

Hill--

Tried my hand at use of EOT via the font-face rules. http://boinkinchipmunks.com/web/articles/white.aspx

This page is a partial reproduction of a Texterity online magazine publication. Texterity is a service that uses a propriety technology to deliver exact reproductions of a client's print magazine to a Web browser. The problems with these specialized types of delivery are self evident.

EOT was well suited for this. Since EOT EULAs are up in the air so to speak, Calibri and Cambria were used rather than exact duplication of the publication typefaces. Font-face rules have been specified using an external style sheet within conditional comments. Partial subsets were used. XHTML 1.1 custom, CSS 2.1, Priority 3 WCAG 1.0, blah blah blah compliant. The CSS could have been done much better by someone who is much more proficient than I.

re: Font Embedding on the Web

EricLaw [MSFT] — Wed, 30 Jul 2008 22:28:51 GMT

No, IE6 will never be removed by "automatic update." It will eventually fall out of support, on the schedule outlined here: http://support.microsoft.com/gp/lifesupsps/#Internet_Explorer

re: Font Embedding on the Web

Karthik Ram — Wed, 30 Jul 2008 21:47:52 GMT

This is all great..but as GM do you / MS have any plans / dates as to when MS will retire IE 6? If so, can you share them?

Like an automatic update that would remove it? Something that will make it stop working? I am getting ready to start using IE 8 technologies for serious development, but it is increasingly difficult to ensure cross-browser compatibility for 3 different versions of A browser.

re: Font Embedding on the Web

Karthik Ram — Wed, 30 Jul 2008 21:47:20 GMT

This is all great..but as GM do you / MS have any plans / dates as to when MS will retire IE 6? If so, can you share them?

re: Font Embedding on the Web

anony.muos — Wed, 30 Jul 2008 07:29:14 GMT

Why is that utility web-based and not downloadable?

re: Font Embedding on the Web

Glen — Mon, 28 Jul 2008 20:38:50 GMT

"What possible reasons do Microsoft have for not implementing support for embedding TrueType (or even OpenType) fonts via the @font-face CSS declaration? Could you at least explain that?"

I think by not doing that they're trying to get the other browser makers to support EOT. Time is money, and they already have something that works.

re: Font Embedding on the Web

Ralph — Mon, 28 Jul 2008 18:15:39 GMT

I can't believe there is an entire thread dedicated to the argument over a non-standard font issue, when developers would much rather see features they care about added to IE.

How about some OPACITY people!? (the CSS property that is, we'd like TRANSPARENCY from the IE team)

How about some improved DOM support for Select and Table elements, why must these be soooo broken?

How about addEventListener? We realize this spec has only been around for like Two-Thousand-And-Five-Hundred days or so, but surely support must be almost ready now?

re: Font Embedding on the Web

Ben Darlow — Mon, 28 Jul 2008 16:29:53 GMT

Joe Clark more thoroughly deconstructed the article above than I think any of the rest of us could hope to, but I am still left with questions based on the comments above by Chris Wilson.

You state that Internet Explorer has supported @font-face embedding for ten years (and /get with the program/ etc. etc.), but isn't this only the self-same EOT embedding that nobody uses or cares about, rather than TrueType as now supported by Safari?

I agree that directly linking to system-installable font files is a messy solution, but contrasted with what is effectively an obfuscation wrapper around fonts, created using proprietary software, it's easily the better one.

What possible reasons do Microsoft have for not implementing support for embedding TrueType (or even OpenType) fonts via the @font-face CSS declaration? Could you at least explain that?