-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yes, mostly yes.
We can put .po/.mo on it, or even sync the source to LP and use the auto-extract feature to extract all the strings (this is a new feature, I have to survey it). For Translation status, LP has a interface for showing status for all languages. [1] After click in any link, you can see contributors of that translation. [1] https://translations.launchpad.net/rt/+translations Best wishes, BlueT Gabor Szabo wrote: > > I have no idea how that would work out so I am trying to understand > what we need in order to switch. > > If we decide to use that service for translations then: > > 1) We won't keep neither the .mo nor the .po files in our repository > so people won't be confused what to update. > 2) We need a command line tool to upload the most recent .mo files > 3) We need a command line tool to export all the .po files > and put them in the right place in the padre source tree > just before packaging or when someone wants to try Padre > 4) We need a way to track the translators and add them to the list > of translators in Padre. > 5) The currently active translator need to agree to the whole thing. > > Am I misunderstanding something or missing something? > > regards > Gabor > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvtmVwACgkQfoJ/q1KWx6it2QCdEuqKpQQV4a22vUGpJ0HaDrVs snwAnRISopciby3RmepZvZNTgLDY1KYG =hplt -----END PGP SIGNATURE----- _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
