On 18 Oct 2008, at 3:33 am, Maciej Stachowiak wrote:
Some of the proposals there sound really interesting.1) Detect when known unusually-encoded EOT fonts are used, and convert text in that font on-the-fly to Unicode. This has the advantage that features like "find in page" and copy/paste will work correctly; apparently they normally do not when the font is encoded in a way that doesn't match the server-stated text encoding.
No "apparently" necessary, you can see for yourself. Some Kannada sites I know of: http://prajavani.net/ http://udayavani.com/ http://kannadaprabha.com/(these sites usually have font download pages such as http://www.kannadaprabha.com/Fonts/Help.asp with the ASCII-encoded font they use, which you have to download and install to get the site to look right)
Many of these sites don't send an encoding in the Content-Type header, so will probably appear as high‐byte Latin-1 or invalid UTF−8 diamonds, depending on the user's default encoding. Needless to say neither will work with find‐in‐page or copy & paste.
— Nicholas Shanks.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
