- From: Chris Lilley <chris@w3.org>
- Date: Wed, 5 Aug 2009 10:38:30 +0200
- To: Jonathan Kew <jonathan@jfkew.plus.com>
- CC: "Tab Atkins Jr." <jackalmage@gmail.com>, Dave Crossland <dave@lab6.com>, <www-font@w3.org>
On Tuesday, August 4, 2009, 6:53:37 PM, Jonathan wrote: JK> Not really. Most of those sites (or so I gather from various past JK> comments) are using custom "hacked" 8-bit encodings where ASCII/ JK> Latin-1 character codes are rendered with entirely different glyphs, JK> typically in an Indic script. They then use EOT fonts in order to JK> provide glyphs that correspond to their particular encoding. JK> Providing any support at all for this, which will reduce pressure on JK> those sites to update and become conformant with standards (in JK> particular, Unicode) is doing a disservice to their users and to the JK> web as a whole. Agreed. Any developer resources for dealing with such sites would be better put into a tool that can figure out what pseudo-encoding is actually used and then outputs a UTF-8 encoded version of the site. -- Chris Lilley mailto:chris@w3.org Technical Director, Interaction Domain W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Wednesday, 5 August 2009 08:39:26 UTC