Easing software localization with Transifex

Posted Mar 26, 2009 16:01 UTC (Thu) by mezcalero (subscriber, #45103)
Parent article: Easing software localization with Transifex

Tx is the best thing since sliced bread. For an upstream maintainer i18n is otherwise just pain: you have to hand merge a huge amount of patches that you don't understand (I don't speak Swahili, sorry!) band patches that usually have a pretty low quality since the authors are no die-hard hackers.

With Tx all this is gone. For supporting i18n all I need to do is run "git merge" from time to time to merge in new translations. And that's just awesome. I am pretty sure that Tx is exceptionally useful from a translators perspective as well, but for me only the upstream maintainer perspective matters directly. And it cannot get any better then just having to type in a single git command.

Transifex is plain awesome.

Easing software localization with Transifex

Posted Mar 26, 2009 16:37 UTC (Thu) by danilo (guest, #57549) [Link] (1 responses)

I agree, this is the biggest advantage of Transifex. Though, I disagree it can't be made simpler: it can happen without you typing a single command. ;)

Easing software localization with Transifex

Posted Mar 26, 2009 17:19 UTC (Thu) by mezcalero (subscriber, #45103) [Link]

Actually it can. You can configure Tx to commit directly to your master branch instead of a seperate i18n branch. That way you don't even have to merge things yourself anymore. But quite frankly I am always a bit uneasy if things commit directly to master, since only one guy should ever commit to master of my project. And that's me.