लेखन

"Show me the code" is really showing its outputs. With help from Gora Mohanty and Ravishankar Shrivastava, we now have a new Chhattisgarhi (hne_IN) locale defined in glibc with changelog: "" 2008-12-05 Ulrich Drepper * SUPPORTED (SUPPORTED-LOCALES): Add hne_IN. * locales/hne_IN: New file. Contributed by Pravin Satpute . "" Thanks Pravin and Urlich for making it upstream, http://sourceware.org/cgi-bin/cvsweb.cgi/libc/localedata/locales/hne_IN?cvsroot=glibc I am sure there is a lot more to come in near future. - Cheers!

We didn't have a great camera and skills with us but clicked every moment that looked interesting and worth saving. Here I have uploaded few pics taken from either Pravin's digicam or my cellphone cam. Lookout for ones that are tagged with ' fossin2008 '. Apart from foss.in, there are few taken while wandering around in the city of Bangaluru. There are few more, but they would better fit in my orkut profile. cheers :)

With the start of 5th day, starts the end of a journey. A journey of talks, presentations, discussions, BoFs and of course the workouts at foss.in accompanied by a nice not-too-hot-not-too-cold rainy climate in Bangalore, negated by the depressed concerns about the terrible happenings back in Mumbai. About the event, my personal highlights have been the talks, workouts and BoFs around Indic computing. It is interesting how the language computing forms a significant part of almost any foss event in India. The collation workout, Indic BoF, talks on text-to-speech, speech recognition, machine translations all went fine along with my own talk about language i18n support accompanied by Pravin on very first day. On other notes, the Nokia stall very well showcased maemo and N810, with the talks inline with the applications it runs. The workout on collation helped update the status of all the Indic sorting and proceed with the remaining ones like Malayalam. Bengali still remains uncertain. ...

They say, "i18n is not a feature, its an architecture". Its not about downloading and configuring stuff around thats available somewhere in pieces, its about creating something that was not there at all. Me and Pravin have been recently working on getting few of the yet-to-be (digitally) visible languages to meet a minimum technical support/usability criteria. On this background both of us came up with an idea of having a talk or demo on this at foss.in 2008. But looking at the amount of information and practical work involved with the entire thing, a workout looked like a more sound option. So we proposed the workout with title, " Creating Language Support Architecture (i18n) For A New Language On Desktop " which is right now in the first shortlist . The plan is to start with essential theory and some demo about the work, followed by some real work with the help of participants. The proposed abstract is as follows.. Aim is to guide developers from languages that s...

I think the term 'Language Support' has been used in more vague sense so far (please correct me if I am wrong). Also there has been a difference between a language being supported technically and a language that is supported with all the localization. Thus there has been a need to define the terms with more clarity. I think it would be good if we have two different sections for a language support namely, i18n and l10n. Recently I have tried to formulate a minimum criteria for a language to have "I18N Support". The same is documented here: https://fedoraproject.org/ wiki/I18N/ LanguageSupportCriteria On the same lines we may even have similar criteria for l10n support. Although the above has been defined from fedora perspective, I hope it would be common for most other distributions. Feedbacks are welcome :-)

The pango bug #441654 about mprefixups for Malayalam, better known as "Kaarkkodakan" issue has now undergone a history of one year and has caused a lot of pain among Malayalam users. It has also seen a lot of patches like this so far. But none of them neither solve the problem completely nor were they fit for Pango's coding style. Now, finally I have come up with a patch that looks pretty much generic and does not affect the coding style much. Also the testing done so far proves to be fine. All the test cases reported so far have been fixed up without anything else getting affected. Manilal has also did his bit by doing the testing himself and posting the screen shots . Now if everything goes fine and Behdad's critical eye doesn't spot any problem :-), hope to see this one getting committed for next pango release soon.

It seems like there is some problem with comment posting on Anivar's blog . So I decide to put my reply as a separate blog post. Here it goes: Few factual corrections and comments: 1. About the pango bug 357790 and the patch on it: The patch on this bug is a mere clean up version of the patch on bug 121672 which was originally created by LingNing. This was also based on the inputs given by Ani about the grammar of 0d30 and 0d31 which was later resolved (to 0d30 only) through discussions with smc. Point is not to transfer the responsibility, but to acknowledge that pango genuinely has a problem that it does not behave the way Uniscribe does. Another problem in this case is that, Uniscribe bahavior has changed from its version in XP to Vista and we are yet to fix this bug completely. Anyway, my patch was reverted one year back (see Comment #32 on bug 357790 ). Ever since then I have urged on concentrating on the original issue which I still continue to. And Lohit was agreed to b...