Updates:
Summary: Support sites using EOT fonts and font encoding with the
on-the-fly transformation to Unicode
Comment #21 on issue 14948 by [email protected]: Support sites using EOT
fonts and font encoding with the on-the-fly transformation to Unicode
http://code.google.com/p/chromium/issues/detail?id=14948
Glenn, I'll mark them with 'eot' label.
BTW, I have to tell you that these sites are not "easy targets" for two
reasons.
1. According to my limited and *indirect* experiences, it's rather tough to
convince
them of the need.
2. Even if they're convinced, it may not be easy for them to switch
quickly. It appears
that they need to go through an overhaul of their CMS. Apparently, most of
these
sites (Indian newspaper sites) use rather old versions of DTP tools and
have in-house
tools convert the output to HTML
In short, it'll take quite a while for them to switch.
That's why we have https://bugs.webkit.org/show_bug.cgi?id=22339 and this
bug to
support those pages with 'font encoding hack' in the meantime.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
