[Webkit-unassigned] [Bug 20542] Adding EOT Font Rendering capability

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=20542





------- Comment #25 from mjs at apple.com  2008-10-17 18:28 PDT -------
(In reply to comment #21)

> There is a Firefox extension that makes all the above possible by translating
> each textnode in a font-sepcific encoding (depending on the font used) to
> Unicode on-the-fly. ( http://padma.mozdev.org/ ) There was  a proposal to add
> that feature to Chrome (actually,  Webkit) natively, but I haven't  mentioned
> it here because it'd require rather invasive (and potentially perf-impacting)
> Webkit changes (as well as a few dozens of font-specific conversion tables) and
> I was not sure whether it'd fly here.  That's a certainly alternative to EOT
> support with a better user-experience, but with a lot to think about as
> mentioned earlier. I wonder what others think of this alternative. 

I'd love to hear more details about this proposal. Is it always perf-impacting,
or only when a known oddly-encoded EOT font is used?

> Just thinking aloud further:
> How about enabling EOT supports for pre-configured list of (font, website)
> pairs? The vast majority of them will be Indian web sites with a small number
> of sites in Burmese,Khmer, etc (however, the speakers of the latter languages 
> have been rapidly embracing Unicode so it's perhaps 100% Indian web sites). 

That's also worth considering, though it sounds like translating on the fly to
unicode could lead to a better user experience, in all the ways you mention.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.