Indic localisation is a buzz item now. Everyone talks about it and there are projects that attempt to use (and sometimes re-use) various aspects of this hot ticket. The one thing that is missing amidst all this is the need to talk about deployment of the localisation projects and more importantly – discuss about how best these efforts can be leveraged. All the projects, all the efforts to meet translation (and string) freeze deadlines will come to be nullified if we do not manage to deploy them. Sadly, that is what is happening with the L10n effort.
Sometime back (and more often these days) I talked about application driven L10n. This is nothing more than identifying a core stack of applications that are used in eGovernance and other Government transactions and then going ahead to put in place a roadmap for making them available in maximum number of Indian languages (if the application permits). On the face of it, not supporting an Indic desktop, but going after applications might seem to be counterproductive. I agree that it could backfire. But then look at the bright side – you get to introduce L10n in form of interface localisation as well you get to drive FLOSS into the game. The desktop environment will catch up in due course. Already there are DEs Projects in other Indic languages which are attaining a sort of stability wherein they can be put through UI tests. If someone has doubts as to whether such a stack can be identified, do take a look at Spikesource – their stack is wonderfully created to integrate just those elements which enable some developer to go hard on a LAMP course. Additionally, the time is perhaps just right for the L10n groups to consolidate themselves and leverage Intel’s resources in terms of reach as well as its deep involvement in ethnographic studies.
Additionally, what we should be looking towards is involving the user in the development process. I will try and write more about this in the next post.
Here is a nice blog.
