Translation Teams Off

You are a developer and you want to keep your project moving forward. You set up various communication channels and organize an open community around. Your vivid project starts to attract new people, amongst them are people who intend to contribute code to the project. Great, because that’s what you were waiting for when you started building your FLOSS community.

Naturally, you do not allow anyone on the net to directly contribute code without any, more or less formal,  review process. That’s good, since you care about happy community of contributing members, but you also want quality that you can be proud of.

Translation Teams Off

And then there’s the world of community localization. You are most likely not a polyglot, and you can hardly do a review process with tons of languages from around the world, apart from making sure that the localization work you’ve been provided is not missing some obvious bits of technicalities. So you simply open the submit process for l10n to anyone, or reach to some nice outsourcing tool, hoping that translators will eventually cope with it and the project’s l10n will be worthy, as is the code. But really?

But Really, It’s For Your Own Good

That is, not to stick to the openness at any cost. The fact is that, quite similarly to the code contribution, the quality work in l10n will not miraculously show up. It needs reviews, proper management, suitable workflow. It needs community.

One of the first things you need to do if you want to facilitate building a real l10n community is to set up, more or less formal, rules. So you turn the translation teams option on. You encourage work in translation teams & projects, so your translators can interact with each other and share knowledge. You keep an eye on l10n. You are responsive to the needs of your translation team members. Then you are a great developer with FLOSS project that deserves quality & efficiency in l10n very much comparable to that of the professional (as in commercial) translators with plenty of ISO & DIN certificates. And your project has it. For free. (Almost.)

Translation Teams

4 comments ↓

#1 Translation Teams OffPetr Kovar’s Trivia | 9nd.pl on 10.06.10 at 3:05 AM

[...] Petr Kovar [...]

#2 Tweets that mention Translation Teams Off — Petr Kovar's Trivia -- Topsy.com on 10.06.10 at 3:23 AM

[...] This post was mentioned on Twitter by Planet Fedora and Zuissi, Zuissi. Zuissi said: Planet Gnome: Petr Kovar: Translation Teams Off: You are a developer and you want to keep your project moving forw… http://bit.ly/d2dV5S [...]

#3 Khaled on 10.06.10 at 6:43 AM

Lets also not forget that broken translations can crash your application (I’m myself guilty of doing this countless times, one learns the hard way), so the quality is l10n is not some luxury thing.

#4 Petr Kovar: Translation Teams Off | Gnu Architecture on 10.06.10 at 11:46 AM

[...] Planet GNOME You might also like: Andre Klapper: GNOME 2.32 is out. (Design by Vinicius Depizzol) It was a hectic day. GNOME 2.32, the last 2.x version, is out now! Big thanks to all the hackers, translators, bugsquadders, documentation writers, artists, marketing folks, …. Personally I’m proud that our small translation team again managed to have 100% coverage. The release notes might be a bit … Petr Kovar: Hi Planet GNOME! Being syndicated on Planet GNOME from yesterday, I’d like to thank Lucas Rocha for adding me to the list! If interested, you can read more about me as a GNOME contributor e.g. on live.gnome.org, and about intentions behind this blog in my first post. Okay, enough of self-promotion for now, back to … Thomas Wood: Universal Access Settings Jon McCann was recently working with the accessibility folks to come up with a new design for accessibility settings in GNOME 3.0. The results of the discussions are linked to on the Settings/Universal Access wiki page. To help clean up some of the current settings panels, I have been implementing the … [...]