Merge lp:~milo/gwibber/gwibber-milo into lp:~segphault/gwibber/webkitui

Proposed by Milo Casagrande
Status: Merged
Merge reported by: Ryan Paul
Merged at revision: not available
Proposed branch: lp:~milo/gwibber/gwibber-milo
Merge into: lp:~segphault/gwibber/webkitui
To merge this branch: bzr merge lp:~milo/gwibber/gwibber-milo
Reviewer Review Type Date Requested Status
Ryan Paul Approve
Review via email: mp+2543@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Milo Casagrande (milo) wrote :

I've set up Gwibber for internationalization and localization (i18n - l10n) support; modified the setup.cfg and setup.py to use DistUtilsExtra for handling the i18n building; set as translatable the string in the gwibber.desktop file so now they are inside the PO file for translators; renamed gwibber.desktop into gwibber.desktop.in for making it possible to translate; created the po/ directory with POT files and POTFILES.in; started to mark as translatable the strings from the UI (need more work to discovery which strings are really going to be visible to end users); modified the license in the About dialog to a more concise version of the GPL (need more work to discovery why the translators-credit strings doesn't appear).

Revision history for this message
Dominic Evans (oldmanuk) wrote :

Excellent work Milo.

Is there any other infrastructure work needed to start using rosetta (https://translations.launchpad.net/gwibber) for accepting translations?

Revision history for this message
Milo Casagrande (milo) wrote :

Il giorno ven, 26/12/2008 alle 21.47 +0000, Dominic Evans ha scritto:
> Excellent work Milo.

Thank you!

> Is there any other infrastructure work needed to start using rosetta
> (https://translations.launchpad.net/gwibber) for accepting
> translations?

There are a couple of thins that I need to look into the code: a couple
of strings that need to be rewritten for making them clearer to
translators and a couple more of strings that I have to check if need to
be translated (any advice is welcome!).

Apart from that, it's now possible to host the translations inside
Launchpad. If somebody is going to load them in Launchpad, I suggest to
assign the translations to a team: actually there are "Ubuntu
Translators" and "Launchpad Translators". The first one is (obviously)
dedicated at translating the Ubuntu distribution, but not only, they
have some external packages as swell; the second one is a more generic
translation group and is kind of new: it's *not* a group of people
translating Launchpad interface, it's a container of translation groups
that have an active team in Launchpad and that are following certain
"rules". If you want to discuss more this aspect we can have a private
email or meet on IRC, it's a little bit complex right now... :)

Cheers.

--
Milo Casagrande <email address hidden>

Revision history for this message
Ryan Paul (segphault) :
review: Approve

Subscribers

People subscribed via source and target branches