Tag Archives: translation

LXDE speaks 13 languages!

Three weeks have passed (was supposed to deliver some statistics last week but not that much had happened so I took the weekend to rest =)) since last report and we have had another huge progress in the code, most of it has happened the last week though.

As we approach the imminent release of GPicView the translators have been busy to complete the new strings and most of them have also completed and updated other parts of the project. It’s nice to see how interested the community are in completing the translation effort for their language. In early May we had four languages (and English) completed – Arabic, Spanish, Japanese and Swedish. I am pleased to be able to report that we have twelve (not including English!) individual language codes fully translated. We even got some new languages added these weeks that are completed. That’s a really fulfilling experience. Big up to Urudu (a sole maintainer does both Urdu and Urdu as spoken in Pakistan).
Another great achievement this last week was the progress from Dutch and Indonesian, Dutch was placed in the need work category (less than 50% completed) and are now completed. Indonesian wasn’t that far off but not in the runners up category (90% or more done).

Let’s get down to the figures for real then, the completed translations enable 1200 000 000 people to use LXDE in their native tounge. We have doubled the numbers in just about a month work! By completing the runners up category we will add another 411 200 000 native speakers. And by all you who get around by using a secondary language (English, Spanish, French?) the number of enabled users are truly amazing! The translators really deserv a big hand for their great work in connecting people.

I always try to get some languages to deliver, we have a sad category I call “Needs work“. These are not by any means minor languages but their progress is stalled and their completion rate is under 50%. We call members of the community who speak Afrikaans, Bulgarian (new language added just yesterday!), Galician, Korean, Norweigan BokmÃ¥l, Norgweigan Nynorsk, Farsi/Persian, Turkish or Vietnamese to the stands. If you show up and can complete the translation effort we could add another 275 000 000 people to the stash. Please note here that the Chinese translations (as spoken in China and as spoken in Taiwan) are not completed and would bring another 1 000 000 000+ people to the totals. We are a large community, but why stop at large when great is near?

If you know any of the not completed languages or want to translate LXDE in to a new language that we at this stage not try to support please contact us (via the mailinglist, the forums, me directly or by IRC, any means would probably do – e-mail is the best because of time zones=)).
If your language is already in LXDE in some state it is enabled in the Pootle server and it’s easy as reading the guide to get started. Or if you rather would like to get the files and use a PO-file editor there are guides for that approach. Help us become a well translated and enabled Desktop Environment.

Translate *.po files with Poedit

Many of you wanted to help translating LXDE but only a few know how to do this, until now. Here is a description on how to help translating the components of LXDE. You can also view this article in the Wiki:

Translate *.po files with Poedit

This is a description how to translate LXDE components with Poedit. It is not complete and may be wrong at some places edit when I missed something important or even said something wrong (hope not ;)).

Get the code

First of all you should get the latest code from svn. To do so type in the following

 svn co https://lxde.svn.sourceforge.net/svnroot/lxde/trunk/ ./lxde

into a Terminal. You also can use a script for this.

 #!/bin/bash
# svn_co_lxde.sh
# autor maces

if [ -z $1 ]
then
	xterm -e $0 copy
else
        echo "starting"
        echo "------------------"
        svn co https://lxde.svn.sourceforge.net/svnroot/lxde/trunk/ ./lxde

        echo "------------------"
        echo "(program exited with code: $?)"
        echo "Press return to continue"
        #to be more compatible with shells like dash
        dummy_var=""
        read dummy_var
fi
exit

The script opens xterm and execute the same command as above. Make sure to make it executable (chmod 755 ./svn_co_lxde.sh). You now should have the latest code in ./lxde.

Install Poedit

Of course we need Poedit, so just install it (as root).

Archlinux:

 pacman -Sy poedit

Debian/Ubuntu:

 aptitude install poedit

Please add the command for your Distro

Translating

In this example we are going to translate LXMusic (Just change the path for another Program).

Open a *.pot file

This way when there is no yourlanguage.po file. Click on File->New catalog from POT file, navigate to ./lxde/lxmusic/po and open lxmusic.pot with Poedit and open the file. Now insert the wanted informations (if you want) and click OK. Now you have to choose the *.po file which will be generated. Please name it like de_DE.po/es_ES.po/zh_TW.po/… .

Open a *.po file

This way when you want to edit an existing yourlanguage.po file. Click on File->Open navigate to ./lxde/lxmusic/po and open lxmusic.po with Poedit and open the file.

Start translating

You should see something like this (If it doesn’t check Menu->View).

Here is a explanation of what you see.

Now we start translating. Simply select the strings you want to translate by click on them and insert the translation in the empty box under the original text (look at the Image). Go on like this until you are ready.

(hint: ctrl+up/down arrow moves between the strings)

Fuzzy translations

A translation can be marked as fuzzy, a fuzzy translation can originate from more or less to sources. The first one being yourself – or one of your peers. If a string is roughly translated and needs more attention it’s wise to mark it fuzzy to make it easy to find and review. The second source for fuzzy strings are msgmerge or something similar, when mergin an old translation with an updated template (.pot) msgmerge will note updated english strings with fuzzy to notify the translator to review the translations.

Do not leave fuzzy strings in translations considered done!

Image:Fuzzy-button.png

Edit Comment

For editing/making a comment simply click on the edit button (next to fuzzy button) and insert a comment in the Window which will appear.

Image:Edit-comment.png

You easily can see if a translation contains a comment by the comment icon in front of the original text in the mainview.

Image:Comment-symbol.png

What have I changed

To check what you have changed look for lines with a star in front of the original text.

Image:Changed-symbol.png

Save the translation

To save the .*po file just Click on File->Save.

Upload translation

There are (at the moment)two ways to upload the translations.

Way1 – The tracker

For this way you need an SF.net account. Go to https://sourceforge.net/tracker2/?group_id=180858&atid=894871 and click on add new artifact. As subject use something like “German translation for lxmusic” and choose “Translations” as Category. Type in a nice text and don’t forget to attach your *.po file. After this click on Add Artifact and you are ready.

Way2 – The Mailinglist

For this way you need to subscribe to translation@mailinglist.lxde.org. If you are subscribed write a email to translation@mailinglist.lxde.org with Something like “German translation for lxmusi” as subject. Type in a nice text and don’t forget to attach your *.po file. After this send the email and you are ready.

Links

Wiki:

Translation project:

Mailinglist:

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