Re: Request for resolving situation(kn_IN)

[Claude Paroz <claude 2xlibre net>]

Le jeudi 13 mars 2008 à 17:52 +0530, Vikram Vincent a écrit :
> Hello,
> 
> On 13/03/2008, Behdad Esfahbod <behdad behdad org> wrote:
>         On Thu, 2008-03-13 at 17:33 +0530, Vikram Vincent wrote:
>         >
>         > Just a few weeks ago the stats for Kannada showed 16%
>         > translated(anybody can verify this) and suddenly it jumped
>         to 50%. Do
>         > you know how much work you forced us to duplicate?
>         
>         
>         Then there's a communication problem.  Is there a mailing list
>         for your
>         translation team?  If not, ask for one.  It wouldn't have
>         prevented
>         duplicate work if you were the coordinator either.
> 
> Pramod and Shankar are working on localisation as individuals. The
> swatantra.org team is working as a *team*. We use Entrans at
> http://translate.swatantra.org as our translation application.
> There was also some work done by others in the past and most of them
> are not active. And we have 2 mailing lists.
> Personally, I am not ready to throw away this method of involving
> people in the localisation process.

(As I am about to send my mail, I see that Gudmund has sent a similar
mail, sending anyway :-)

If I understand correctly, you would like to enforce the use of your Web
translation tool for all kn translations. I can imagine the sort of
problems you may face where on one side some are committing translations
directly in SVN and on the other side other people are working on the
same translations through the Web tool.
The problematic is somewhat similar to the Ubuntu Launchpad vs upstream
GNOME.

I cannot see any optimal solution to this problem.
One solution could be to divide the remaining work, and announce to the
current coordinator the particular packages on which you want to work.
You should then only open these packages for translation in your Web
tool. When you're done, you send the po files to the coordinator (or
commit if you get the permissions), and then announce another set of
packages on which you'd like to work on in your team.

Regards,

Claude