-
Busy and fun weekend with L10n stuff? You bet.
-
I just got into my new apartment. Important services were installed first: power, internet, heating. Important stuff were moved then: Desk, espresso machine and grinder. Now I can work from the new place and sleep or cook a pizza at my friend’s house for a few more days, until the new furniture and appliances arrive.
The weekend was a very productive one, got the chance to fix a bunch of Fedora Localization TODOs, and ~15 bugs, some of them pretty important for people’s work. Let’s see:
-
Kannada, Indonesian, and Italian teams were created, people have stepped up as maintainers for them. We’ve put their details on translate.fpo, so that people can easily see how to submit corrections and bug reports, and how to join the teams.
With these, we have more than 34 active teams and a total of ~75 languages.
-
We now have all the shipped Fedora Docs, system-config-network and yumex accepting translations from Transifex. Especially with the case of the last two, translation submissions no longer need to be sent with emails/bug reports, nor the developer needs to have account associations for every translator wanting to send something. Get these babies to 100%!
-
translate.fedoraproject.org is now also available in Italian and Greek. Thanks to Francesco Tombolini for the Italian version.
-
Having questions pop up on fedora-trans-list all the time, I went on and created a single FAQ page. While I prefer a proper documentation than FAQs, this stuff work great as a reference point. Next step: move finalized text from there over to the Fedora Translation Quick Start guide, since it’s in DocBook and already translated in many languages.
-
Together with Bart, we moved all content from wiki/L10N/Teams over to the XML files producing translate.fpo/teams/. From now on, we’ll add each new team’s information on the dynamic website instead of the wiki: it’s more easy to maintain, and localizable.
-
Finally, and probably most exciting, a remote command line interface to Transifex has made its first connection over HTTP.
$ ./tx --list-modules -v Creating request http://transifex.shuttle:8084/module/?tg_format=json Module name Description testmodule-cvs A CVS testing module testmodule-git-revisor A Git testing module testmodule-hg-smolt A Mercurial testing module testmodule-svn A Subversion testing module
More to come!
Home-made pizzaUpdate, 2 hours later: Oh, and another fix I was just reminded (thanks ricky): We found the bug that caused Subversion modules behaving strangely and now they are working again.
-