Bug 18668
Summary: | support EOT dynamic fonts | ||
---|---|---|---|
Product: | WebKit | Reporter: | Jungshik Shin <jshin> |
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Enhancement | CC: | ap, eric, mitz |
Priority: | P2 | ||
Version: | 525.x (Safari 3.1) | ||
Hardware: | All | ||
OS: | All |
Jungshik Shin
Safari now supports dynamic fonts in TTF/OTF, but the vast majority of web pages that use dynamic fonts (as of today) use EOT format. Until recently, the EOT format is not known in the public so that it's not possible to support it. However, I've just found that Microsoft had submitted the following document to W3C.
http://www.w3.org/Submission/2008/SUBM-EOT-20080305/
This will help Safari (and other webkit-based browsers) penetrate South Asisan (Indian subcontinent and its vicinities) and Southeast Asian markets where EOT format dynamic fonts (and 'font-encoding') are still widely used in place of the proper Unicode encoded documents.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Eric Seidel (no email)
Awesome. I wonder where this belongs though. I guess we could write our own font parser. Would be nicer if there was already a libEOT out there.
Eric Seidel (no email)
*** Bug 18669 has been marked as a duplicate of this bug. ***
Jungshik Shin
http://www.w3.org/Submission/2008/SUBM-MTX-20080305
: MicroExpress font compression format spec used by EOT.
Dave Hyatt
I do not believe WebKit should support EOT (for reasons that have been hashed out on www-style).
Eric Seidel (no email)
No plans to fix this. If the CSS WG decides to recommend support , we'll reconsider.
Alexey Proskuryakov
I would imagine that another reason to reconsider would be having bug reports for multiple important sites that break because of this.
Jungshik Shin
sorry for bug spam. need to reopen before duping this to 20542.
Jungshik Shin
*** This bug has been marked as a duplicate of 20542 ***