I am Slovak GNOME Translation Coordinator and I decided to update Slovak translation of Django. Why?
GNOME is using Damned Lies[1] for GNOME translation status reporting and for the translation work organization. The Damned Lies is built on top of Django. I realized not ideal quality of Django translation to Slovak and because I am using Damned Lies often (and some mistakes are annoying) I considered to improve the translation of Django to Slovak.
There is already open ticket #9634 [2] where I uploaded new Slovak translation of both djangojs.po and django.po files.
I would like to see both files checked into the Django source repository. So, please, commit my translation work.
On Mon, 2009-02-09 at 20:51 +0100, Marcel Telka wrote: > Hi all,
> I am Slovak GNOME Translation Coordinator and I decided to update Slovak > translation of Django. Why?
> GNOME is using Damned Lies[1] for GNOME translation status reporting and > for the translation work organization. The Damned Lies is built on top > of Django. I realized not ideal quality of Django translation to > Slovak and because I am using Damned Lies often (and some > mistakes are annoying) I considered to improve the translation > of Django to Slovak.
> There is already open ticket #9634 [2] where I uploaded new Slovak > translation of both djangojs.po and django.po files.
> I would like to see both files checked into the Django source > repository. So, please, commit my translation work.
Thanks for doing this. A couple of things for the future:
(1) No need to announce when you upload a translation patch. There's a mailing list that shows all the ticket updates. Every now and again I go through all the tickets in the translation component and commit those that are ready.
(2) Please create a patch file containing the changes, not two separate PO files. That allows us to check that a recent version has been translated and makes reviewing the scope of the changes easier for those who speak Slovakian. It also saves brain power trying to work out what needs to be committed, since only the last upload patch file will ever be particularly relevant.
(3) Does your translation update include the changes mentioned in comment #3 on that ticket? If not, it would be good to include those.
On Tue, Feb 10, 2009 at 05:09:50PM +1100, Malcolm Tredinnick wrote:
> On Mon, 2009-02-09 at 20:51 +0100, Marcel Telka wrote: > > Hi all,
> > I am Slovak GNOME Translation Coordinator and I decided to update Slovak > > translation of Django. Why?
> > GNOME is using Damned Lies[1] for GNOME translation status reporting and > > for the translation work organization. The Damned Lies is built on top > > of Django. I realized not ideal quality of Django translation to > > Slovak and because I am using Damned Lies often (and some > > mistakes are annoying) I considered to improve the translation > > of Django to Slovak.
> > There is already open ticket #9634 [2] where I uploaded new Slovak > > translation of both djangojs.po and django.po files.
> > I would like to see both files checked into the Django source > > repository. So, please, commit my translation work.
> Thanks for doing this. A couple of things for the future:
> (1) No need to announce when you upload a translation patch. There's a > mailing list that shows all the ticket updates. Every now and again I go > through all the tickets in the translation component and commit those > that are ready.
> (2) Please create a patch file containing the changes, not two separate
You said above "for the future", but I am not sure here. Should I create patches now for my 2 weeks old translations or not? If so, I'll do it. No problem.
> PO files. That allows us to check that a recent version has been > translated and makes reviewing the scope of the changes easier for those
Ok. For future I'll do that.
> who speak Slovakian. It also saves brain power trying to work out what
Please use "Slovak" instead of "Slovakian". According to ISO "Slovak" is the correct English name for our language. Thanks. :-)
> needs to be committed, since only the last upload patch file will ever > be particularly relevant.
> (3) Does your translation update include the changes mentioned in > comment #3 on that ticket? If not, it would be good to include those.
Yes. Of course. Sorry for not mentioning it in the ticket. Quick look into PO files could prove that I fixed it. :-)
On Tue, 2009-02-10 at 11:01 +0100, Marcel Telka wrote: > Hi Malcolm,
> On Tue, Feb 10, 2009 at 05:09:50PM +1100, Malcolm Tredinnick wrote:
[...]
> > (1) No need to announce when you upload a translation patch. There's a > > mailing list that shows all the ticket updates. Every now and again I go > > through all the tickets in the translation component and commit those > > that are ready.
Hey, don't worry about it too much. That really was "for the future". It happens all the time. :-)
I'm on the list that receives updates, so I often see "ticket updated" email followed by announcement to the list in short succession, which highlights the issue to me.
> > (2) Please create a patch file containing the changes, not two separate
> You said above "for the future", but I am not sure here. Should I create > patches now for my 2 weeks old translations or not? If so, I'll do it. > No problem.
If you could create a patch for this one, that would be appreciated.
Also, I forgot to ask: did you translate trunk or the django-1.0.X branch? Just add a note to the ticket so that I start from the right place.
I've mentioned in the past on this list that, once the branches start diverging, I'll ask people to make two patches. However, at the moment, it's not been too difficult in practice to apply the patch to the original branch, run makemessages against the other branch and reapply the patch. When that stops working, I'll start asking for two patches a bit more.
> > PO files. That allows us to check that a recent version has been > > translated and makes reviewing the scope of the changes easier for those
> Ok. For future I'll do that.
> > who speak Slovakian. It also saves brain power trying to work out what
> Please use "Slovak" instead of "Slovakian". According to ISO "Slovak" is > the correct English name for our language. Thanks. :-)
Good point. Noted. :-)
> > needs to be committed, since only the last upload patch file will ever > > be particularly relevant.
> > (3) Does your translation update include the changes mentioned in > > comment #3 on that ticket? If not, it would be good to include those.
> Yes. Of course. Sorry for not mentioning it in the ticket. Quick look > into PO files could prove that I fixed it. :-)
My internet connection was playing up yesterday, I was getting very old waiting for the PO file to load (I was trying to look for that). I'm not complete useless, just practical at times. :-)
