Skip to main content

The Indic Mashup

This weekend got contributed for the first Indic Mashup workshop. The idea initiated by Karunakar finally took shape inside Red Hat premises at Pune.

The participants were expected to come from various language communities. So most of the Red Hat's Localization team appeared on a Sunday morning. It would have been great if more linguists and i18n contributors around Pune and Mumbai would have participated. But except Karunakar and Localization team, the only linguist present was Ravi Pandey who is a font designer and Marathi, Sanskrit expert. Still the crowd of 13 and the issues were good enough to discuss and work upon for 10 to 5 schedule.

Various issues from keyboard layout to collation tables, a lot got discussed. I thought related bug reports could also have been filed at appropriate places, but that might need more focussed workshops in near future. Now we are clear what issues are there and what can be done for them. I think this is a very good achievement for now.

So far, most of the events I have seen were mostly like someone presenting and others listening. This was certainly different. People had actually got into source codes and bugzillas. Testing for most of the Indic related tools was done across distributions. Reports got generated for upcoming features like collation. The collation sequences for various languages with reference to unicode provided collation charts and proposed modification/additions to that are posted here. The only missing for now would be bengali, assamese, tamil and oriya. Now that Assamese, Tamil and Oriya collations are already implemented, a thorough testing could have been done, but the absence of Language experts limited this task.

Among other issues, the important ones that have given few todo's would be the ones related to the keyboard layouts. Few characters like Om, ZWJ, ZWNJ have been either absent or not placed uniformly among various languages. We tried to find out vacant places on current layouts to accommodate these new additions for one-to-one mapping(xkb). Other options like sequence of keys are kept for scim. There is lot more that got discussed which would be worth for filing bugs.

Among feedbacks, the most obvious one, it was different. It was a workshop in real and not just a speech and presentation. Being first of this kind, it was more generalized. Request are now coming up for more focussed ones in future. focusing particular field like input methods or fonts, focusing particular language and so on.

Among few negative feedbacks, one was the weekend work. Not many like the idea of spending a lovely Sunday for such a tensed work. It would be great if it can be managed during weekdays, not as big as this but preferably shorter sessions of couple of hours.

One more comment I received was that the Indic mashup sounded more like Marathi mashup. This was expected to some extent. I would rather say it concentrated more on Devanagari issues. But this was inevitable. Only linguist present was a Marathi and Sanskrit expert. There were two maharashtrian i18n engineers(including myself), one Marathi language maintainer and one Hindi expert and others who understood Devanagari better. For other languages only one developer was present per language. In my personal opinion there could have been more involvement from other language developers. More issues and requirements could have been raised. But nevertheless even though most of the references were done using Devanagari, most issues were common in general for rest of the scripts and languages.

About venue and facilities, WiFi worked very well. IRC was use mainly for sharing URLs and satisfying the curiosity of few remotees. Except for a delayed lunch, food and all worked out well too.

To sum up I can say this event proved to be productive and I would be looking forward for few more focussed and comparatively shorter sequels.

Popular posts from this blog

PVR is so wierd!

Yesterday we went second time to a mall bit far from office to complete the earlier failed mission of watching this 3D movie, Clash of the Titans. On ticket counter, we were first told that evening show was house full. Then we asked for a night show, and were told there isn't any show then and the gentleman handed us the pamphlet of all movie schedules. We checked on the nearby digital kiosk and also on the printed schedule to be sure of the show timings. Then went to second counter, and asked the lady for the night show tickets, and without any problem got the tickets for back seats. In fact this show was hardly 20% full, wonder how the evening show became houseful.

But the biggest wonder/blunder is yet to come. On the entrance we were stopped for having a laptop bag along with (we had went straight after the office). In spite of having checked the bag, we were not allowed, because laptops were not allowed inside! Then we asked for keeping it at the baggage counter. But then, the…

अग्निपथ से धूलपथ तक!

अक्सर दिल्ली की धूप में 'दोपहर' के १० बजे घरसे निकलो, तो अपनी ही दशा को देखकर सबसे बड़े बच्चनजी की पंक्तियाँ याद आती हैं।

यह महान दृश्य है, चल रहा मनुष्य है,
अश्रु-स्वेद-रक्त से लथपथ लथपथ लथपथ।
अग्निपथ अग्निपथ अग्निपथ...

किंतु आज तापमान में गिरावट और धूल-वायू की लहरों के चलते, दिल्ली की सड़कों को अग्निपथ से 'धूलपथ' में परिवर्तित होते पाया गया है। फिरभी देखा जाए, तो इसे उष्मा से मुक्ती का एक तात्कालिक ही सही लेकिन सुखद अनुभव कहा जा सकता है।

Designing for scalability – a startup perspective

What is scale? Is it the number of customers a company has? Is it the number of products that are sold? Is it the amount of revenue the company makes? Is it the amount of infrastructure one has? Or is it the number of features the product has? Well, it can be all of this or none of this. When an organization talks about scale it is not just a number. When an economist talks about it, again it’s not just a number. For an economist, the scale is about doing more with less. Scale is about perspective, about relationship between two or more variables that ultimately help you generate optimum value for your efforts.
Consider this, let’s say you are into making a lollipop. Selling 10 lollipops you earn $100 revenue of which $10 is you profit and $90 is the cost. When you increase you production you start selling 100 lollypops and earn $1000 revenue with $100 as your profit and $900 as cost. Did you really benefit from the scale here? In absolute terms, of course. In terms of ratios though,…