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

[bugzilla-daemon at webkit.org]

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





------- Comment #26 from jshin at chromium.org  2008-10-20 14:24 PDT -------
(In reply to comment #24)
> (In reply to comment #21)
> 
> > Ick. No ISCII, please.
> 
> There is nothing wrong in storing and serving the files in the various ISCII
> representations, 

You may not, but many people want to see *all* the web pages encoded in UTF-8
or UTF-16.  I know legacy-encoded pages will keep being put up for a long time
to come.  However, do we really want to introduce any 'new legacy encoding'
('new' in the sense that they've not been used in any meaningful number of
sites) into 'the web sphere' ?

> especially low memory mobile devices in places like China and Japan).
> 
> > copy'n'paste, find-in-a-page, and history would not work
> 
> These features do not require Unicode, 

Did I say that it requres Unicode?  Of course not ! Otherwise, all those
non-Unicode encoded pages would be in big trouble. 

> If it is easier to talk sites into using ISCII than it is to get them to use
> Unicode, then that's great, lets do that.

I don't think it's any easier to persuade them to switch to ISCII than Unicode. 
Besides, note that Firefox does not support ISCII at all although it's
relatively easy to add support for them.  Chrome does not either (it's even
easier to support ISCII in Chrome than in Firefox), but again I'd not do that
unless it's really necessary. 


-- 
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.