Re: [indic] Lack of Complex script rendering support on Android

From: Philippe Verdy <>
Date: Fri, 4 Nov 2011 17:36:45 +0100

Yes, no problem to render this list (note that the site is viewed in
its mobile version, MediaWiki autodetects that I use a smartphone and
alters a bit the layout, but not the text). Only Tibetan is not
correctly displayed for now because I have not found a way to install
a font for it, and Lao has some issues.

This is not a complete test though, I still use a Windows PC (laptops
and notebook) mosts of the time. And I can't test tablets (I don't
think I'll want a tablet for now to replace my notebook, I still want
to use traditional keyboards and mice). On the go, I will prefer a
smarthpone that fits in my vest pocket. We may finally see the
development of tablets with a dock station that works like a notebook
with additional hardware, CPU, disk storage, DVD player/burner, large
5.1 audio, cumfortable keyboards and mice, an additional GPU with HDMI
output and everything you want on a traditional PC, but even then I'm
not sure I would unplug the screen to turn it into a mobile tablet: I
will still want to use a smartphone that should better integrate with
my non-mobile environment, as if it was a supplementary screen and
input device. It should also offer a native virtual desktop to connect
from remote to my home or work environment via the Internet and with
the possibility of syncing some contents even from remote (how many
times I went away and forgot my last photo collections or some
documents? And why do I need to store everything on the mobile device,
using extra storage plus too many apps that just pumps the battery?)

If the world is going to the "cloud" direction, we should be able to
use any device with any convenient form factor, to access to our
prefered clouds (not necessaily hosted on the Internet). OS
differences should disappear if there was a real developement for a
cloud OS where all access devices are just extending out own clouds
with some input and output capaiblities adapted to the form factor.
All applications should be able to run from everywhere and without
even requiring multiple installations. This includes the need for
equal treatments of text renderings and portable fonts that can be
synced automatically.

All OS distributors should work on creating a base set of fonts needed
to support all languages and scripts of the world (not necessarily in
many styles), with a repository of webfonts that an be synced and
cached automatically. It is no longer acceptable to see square boxes
for texts written in modern languages and soon people will want to be
able to read also technical documents with collections of symbols from
anywhere too, even if they can't easily input them on their device.
Input methods should also be ported to include also user preferences
on their layouts for the various device form factors they want to use
(physical keyboards or virtual on-screen touch keyboards) We should
also be able to extend any smartphone with additional input devices
with a Bluetooth or WiFi connection, or by the USB plug.

But the main problem of mobile devices is still their battery: you
can't fit everything in your device, but you also cannot use mobile
access networks due to the slow speed and cost of data transfers; if
those prices were lowered, we could host most CPU/GPU and
memory/storage capabilities remotely, and save lots of battery life on
the mobile device (no smartphone can work today at least for 24 hours,
and finding a place to recharge the device is still difficult)

2011/11/4 Shriramana Sharma <>:
> On Fri, Nov 4, 2011 at 8:05 PM, Philippe Verdy <> wrote:
>> he wants apparently, and suppress/disable some modules. I have no
>> problem on my Samsung S 2 that displays properly all languages shown
>> on the home page of Wikimedia Commons for example.
> Are you referring to the following list at the bottom of the page
> above "sister projects":?
Received on Fri Nov 04 2011 - 11:42:52 CDT

This archive was generated by hypermail 2.2.0 : Fri Nov 04 2011 - 11:43:20 CDT