Ed Trager said on Mon, Nov 07, 2011 at 11:11:19AM -0500,: > Not just if you buy a phone in India. In this modern world, there are > plenty of > students and immigrants all over the world who might enjoy communicating with > their friends and families in their native languages. > > So I would say, if anyone buys *any* Android phone *anywhere* in the world, > it should just automatically support complex text rendering for all > Indic and Indic-derived > scripts ...
Arrey Bhai!!! Aap samjah karo; hum hindustani log pura Indic bhasha ASCII mein likha hai. Humko Unicode ya UTF-8 mumbu jumbo nahin chahiye. Sirf ek bhasha; sirf ek keyboard lay out - ASCII. (translation - ASCII is enough for us Indians to communicate in any Indic language - only one Keyboard, only one language) /just venting my frustration at all those device makers, and I am not very fluent in HI. And the second paragraph you quoted above - those are almost exact words I used in one of my comments on one issue over at Android's issue tracker site. > I wonder if perhaps India needs to legislate script support on > computing devices and cell phones? May help. OTOH, when I got my last nokia phone, the sales lady simply handed it over it to me, after fiddling with it for some time. After I got out of the shop, realised that the GUI was in some other language (either MR or GJ). It was an XpressMusic series phone. She apparently could not come out of the unfamiliar script. I finally looked up the user manual (one of those rare events in my life when I read a user manual before using a product), and followed the logos to come out. The X2 too has the same problem. Otherwise, both were very good phones. But ML renering was very poor. To be fair, when I flash one of the EU firmwares on my Android device, it boots up into Russian. I tried the Asian firmwares, only once - and it booted up into Chinese/ Korean / Japanese / one of those East Asian languages!!! ;-D -- Mahesh T. Pai || End Users are just friends who haven't submitted a patch yet.
