W3C home > Mailing lists > Public > public-mw4d@w3.org > August 2010

Re: I18N, fonts and mobile (was Re: After Access Challenges Facing Mobile-OnlyInternet Users in the Developing World)

From: Stephane Boyera <boyera@w3.org>
Date: Thu, 05 Aug 2010 16:42:04 +0200
Message-ID: <4C5ACDBC.7020408@w3.org>
To: David Storey <dstorey@opera.com>
CC: public-mw4d@w3.org
Hi David,

thanks for the information.
Could-you let me know what font transcoding is ?
i mean the opera proxy for mini detect that a page requires specific 
fonts, let's say hindi. What is it doing ?
Are you saying that opera mini does not use the system fonts?

Stephane
> I bumped into one of our Indian sales guys in the corridor and he
> mentioned that phones in India are usually sold with Hindi fonts, so
> Opera Mini works fine with Hindi web sites. He also mentioned that it
> doesn't matter too much for Opera Mini as we do font transcoding (this
> needed for for example TATA, one of the biggest Indian telecoms
> companies) such as we do content transcoding, so it should work with
> those languages even when there are font issues.
>
> David Storey
>
> Chief Web Opener / Product Manager, Opera Dragonfly
> W3C WG: Mobile Web Best Practices / SVG Interest Group
>
> Opera Software ASA, Oslo, Norway
> Mobile: +47 94 22 02 32 / E-Mail/XMPP: dstorey@opera.com / Twitter: dstorey
>

-- 
Stephane Boyera		stephane@w3.org
W3C				+33 (0) 5 61 86 13 08
BP 93				fax: +33 (0) 4 92 38 78 22
F-06902 Sophia Antipolis Cedex,		
France
Received on Thursday, 5 August 2010 14:42:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 5 August 2010 14:42:09 GMT