Tag Archives: Transifex

Transifex is out

Effective immediately we have stopped using Transifex.net for translating LXDE components. All translators and prospective translators inside the LXDE project have been informed about this move via the platform itself. We have removed the possibility to submit strings in the tool but unfortunately for people who have submitted stirngs there in spite of the earlier warnings we can not recover the strings. If you have done work and the file appears more complete in Tx than in git/pootle please contact the lxde-i18n mailinglist to get advice on how to proceed.

It’s sad to be forced down this path but as with every decision there is a rollback option. If the time changes we might consider to use Transifex.net again in the future. This is however way out of schedule by now.

Thanks everyone using Tx to do translations for LXDE – it’s been valuable and we hope you will switch to use Pootle instead (as upload service or as a online tool).

Thank you Transifex developers, we do know you a great guys doing a great deal of work but the connection between the projects just weren’t there for the time being. If you make changes that we might benefit from we love to here from you again!

Improving the translations workflow with Transifex

Roughly about a month ago Martin Bagge mentioned that we were researching the possibility of using Transifex as a translation platform for all of the LXDE components. That is not to say that our Pootle server won’t be around, but we felt that our translators could benefit from a few handy features that Transifex has to offer.

So what exactly is Transifex you may ask? I guess the best way to describe it is as a bridge between source code that needs to be localized and people who know how to translate it. But that was a rather simple description of what this amazing tools does! I could go on and on about the cool features, but for this post I’ll try to keep it simple and go directly to the point.

For the administrators: Nothing needs to be done! That’s right, nothing! No more local user accounts, ssh keys and all of that nonsense! Put your feet up and relax!

For the translators: At first glance it may seem like there is yet another entry point for you to do your work, but bear with me for a bit. If you love how Pootle works and that does the trick for you, then nothing has changed. The same goes for those who like me have direct commit access and like to use the command line! Keep up the good work! However, if you crave for some some type of management and up to the second information about your translations, then you’re going to enjoy what Transifex has to offer!

As I mentioned before, Transifex acts like a bridge between your source code and translators. It doesn’t really matter what type of versioning control system is used to store the source code (by the way, we use subversion). All this tool needs to know is: where does the code live, who is entitled to work on translations, and if translations that are uploaded can be automatically committed upstream.

Transifex workflow
Transifex workflow

So your job as a translator will be:

  1. to create a (free) account in the Transifex server;
  2. associate yourself with the LXDE project and the specific language you want to work on;
  3. and use the web interface to reserve a file for translation. This file can then be downloaded and translated offline and then submitted back via the same interface. The translation is then validated and committed upstream into the official repository.

If you are responsible for managing one of the language teams or just want to make sure you know what is happening with the project as a whole, you can choose to be notified every time someone reserves a file for translation, writes down a comment, reviews someone’s work, or a commit takes place. Since people will have to reserve a file for translation, you can make sure that no two people work on the same file at the same time, in the end saving time, headaches and redundancy. Best of all, since your work can be committed automatically when you upload your translation, you can see in real time your progress and that of your teammates.

Reserving and submitting translations
Reserving and submitting translations

In the next few weeks we will have a LXDE project officially set up and hosted by our friends from the Transifex project and we will then make a call to arms so that those who want to use this new platform can get the proper permissions configured, but I kindly ask everyone to wait until we make another announcement here.

In the meantime, keep up the excelente work you’veĀ  been doing and let us know how we can make your lives easier! Comments, concerns and suggestions are more than welcome!

Launchpad or Transifex? What is the best system for LXDE?

With the increase of LXDE components and the ongoing development of LXDE the need for a better translation system has increased. We discussed different option in this forum here: viewtopic.php?f=12&t=35

We have set up a vote for you to cast which system and solution you prefer. Please vote in this forum: http://forum.lxde.org/viewtopic.php?f=12&t=163

There are three options:

1. Launchpad

2. Transifex at fedorahosted.org

3. Transifex hosted at lxde.org

Some quotes from the forum:

cwickert:
Launchpad
Pros:
* large user base, this means a lot of potential translators
* beginner-friendly
Cons:
* bad workflow for getting translations upstream
* getting translations into a a new release requires manual intervention: It has to be downloaded from launchpad and added to LXDE’s SVN.
* known to produce bad translations. This is the downside of being beginner-friendly

Transifex
Pros:
* More professional
* works with nearly every VCS: CVS, SVN, git, …
* Translations are automagically pushed back to upstream’s VCS
Cons:
* Requires ether to be set up on a server (which also mean maintainance) or to use fedorahosted.org
* Smaller userbase

Elias: I think Transifex is better for this project, because the development of LXDE is not made in Launchpad. Launchpad is not (afaik) so flexible than Transifex.

cwickert: If we use fedorahosted we are bound to the Fedora accounts system (just like we are bound to Launchpad user management), if we setup our own transifex we can manage users ourselves more easily.

ogmaciel: I’d like to support the idea of using Transifex and host it with Fedora projects (unless someone has the time and hardware/bandwith). All pros/cons already cited are a pretty good list but the one that imho is the most important is the fact that translations should always be done upstream, and then trickle down to distros. Transifex plus a good quality control process before committing files (more about that later) will allow for a quick, efficient, and top quality translation process.

For a better coordination of translations of LXDE we have started the LXDE Translation Project. Please also join the Translations Mailing list.

Transifex: http://transifex.org
Launchpad: https://launchpad.net
Forum for voting: http://forum.lxde.org/viewtopic.php?f=12&t=163
LXDE Translation Project: http://wiki.lxde.org/en/Category:Translations
LXDE Translations Mailing list: http://mailinglist.lxde.org/cgi-bin/mailman/listinfo/translation