[Webkit-unassigned] [Bug 22339] Support Indian web sites with EOT by on-the-fly transcoding to Unicode

[bugzilla-daemon at webkit.org]

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





--- Comment #24 from Jungshik Shin <jshin at chromium.org>  2013-02-11 14:12:24 PST ---
(In reply to comment #22)
> I'm curious if there is any updated context for this bug? or if it's just as important as it sounded in '09, just 3 years later? :)

The Unicode is much more widely used than before, but still there are quite a lot of pages in one of Indian languages using this 'font hack encoding'. We still have a continuous stream of 'cryptic bug reports' from India saying that 'Tamil (put any Indic languages)' web page is rendered with gibberish. Most of them, if not all, refers to font-encoded web pages. 


In case of Chrome (as with Firefox), we implemented a transcoding extension, Padma ( https://chrome.google.com/webstore/detail/padma/ngifghlmhidnielinpjdkkiadocdffbi?hl=en ) to work around this problem. 

Unfortunately, this does not help Chrome on Android because Chrome on Android does not support an extension, yet. 

Recently, we realized that there are two 'pseudo-Unicode/font-based encodings' widely used for Burmese/Myanmar. [1]  In a sense, it's even worse because the pages are apparently in UTF-8 but Unicode code points are interpreted differently than what's specified by Unicode. Nonetheless, they can be handled in a similar way as font-encoded Indic pages. 


[1] They're Zawgyi and San Myanmar. Even though Unicode-based Burmese fonts have been freely available (e.g. Padauk and Mynamar 3), Zawgyi and 'San Myanmar' were used apparently for the easier input.  BTW, Windows 8 is the first version of Windows with a Burmese/Myanmar font included.

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