On Tue, May 11, 2010 at 3:16 PM, BlueT <bl...@bluet.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Translation for ubuntu packages are not automatically sync to upstream
> becouse those "upstream"s don't have a way to let LP to push-back.
> LP dev team has trying to solve this for a long time.
> And BTW, there are more and more OSS project developers syncs their .po
> manually between thier project and LP. This is the only way for projects
> which don't have a way to automatically push-back.
>
> Please note, the problem only exist when you translate "ubuntu packages"
> under /+ubuntu/ dir.
>
> If Padre uses LP as it's "Official Translating Platform", we can
> maintain our .po ourself, without syncing problem, becouse this can
> become the "only officially support" method for translation gethering,
> .po files from any place should be updated on the platform.
>
> To have a "Official Translating Platform" can reduce the re-sync,
> re-sync, and re-sync cost on syncing all the .po files, maintain an
> official copy which every translators should follow.
> And when we wanna release a new version, just export those .po files,
> put it in the locale dir, make the tarball. All done. :-)
>
> I agree that installing our own system can have the adventage on the svn
> intergration.
> But the reason why I suggest to use LP service instead of installing the
> system on our own server is, we have limited resources, which should not
> be waste on places we don't really have to.
> And second, if we host our tranlations on LP's translation service, we
> can share all the resources which other projects on LP have. :-)
>
> It's just my suggestion, up to you guys. :-D
>
>
> Best wishes,
> BlueT
>
>
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
