- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 28 Jan 2014 09:47:06 -0800
- To: Andrew Cunningham <lang.support@gmail.com>
- Cc: Henri Sivonen <hsivonen@hsivonen.fi>, WWW International <www-international@w3.org>, Asmus Freytag <asmusf@ix.netcom.com>
On Tue, Jan 28, 2014 at 1:52 AM, Andrew Cunningham <lang.support@gmail.com> wrote: > Your point is valid, but there is the flip side: the specs should also > require browser developers to implement correct rendering of those > codepoints. > > In those cases where there is full Unicode support for a laanguage. > > Passing off the problem as a need to provide guidance to web developers to > Unicode ignores the fact that browser developers also need to get it right. > > You need a complete ecosystem, browsers, web services and infrastructure > and content. > > And honestly its the web browsers that are the weak link in the utf-8 cycle. You can supply your own font. And if your current font has a mapping for the wrong code points, you could fix it. Browsers provide all the necessary infrastructure to do the right thing. It would be great if we had better fonts too, but you can do without it. -- http://annevankesteren.nl/
Received on Tuesday, 28 January 2014 17:47:34 UTC