On Sun, 2007-04-08 at 09:31 +0200, Radek Svarz wrote:
> Hi Malcolm,
>
> I am the maintainer of Czech translation and did not know about the
> responsibility of running ./bin/make-messages.py myself.
>
> When I was the maintainer of TortoiseSVN translation I was used to
> watch the status of translations on the status page:
> http://tortoisesvn.net/translation_devel_gui
>
> When I realized that Czech is too far bellow (like today) I took the
> current czech .po file and updated it.
Periodically I think about putting together one of those pages. They are
very easy to generate, so it's just a matter of finding some spare time
to do it. If nobody else does it first, I'll get to it one day.
By the way, you can always look at the statistics for any individual PO
file by running "msgfmt --statistics ..." on the file. For example:
`--> msgfmt --statistics django.po
444 translated messages.
Everything is translated.
`--> msgfmt --statistics djangojs.po
19 translated messages, 2 fuzzy translations.
Almost everything is translated. Make sure the PO file is up to date
(make-messages.py) before running this, since the statistics check only
looks at the existing file.
That's all the web page scripts do, too: generate an up to date copy of
the PO file (they throw it away afterwards) and run msgfmt --statistics
on each one and collect the numbers.
[...]
> In any case, Malcolm, could you please post the suggested approach
> with detailed steps for maintaining translation on the Django wiki?
There aren't really any detailed steps. As far as I know, the procedure
is:
-Run make-messages.py -l <locale>,
- update any untranslated messages with your favourite
translation too,
- run compile-messages.py -l <locale> and ensure there are no
errors.
- Upload either the complete new file or a patch (svn diff
<filename>) to Trac.
If somebody wants to turn that into content on a Wiki page somewhere,
please feel free. I'm the worst person to really describe the process
because I do exactly zero translations.
> So far, there is mentioned only posting the new translation and no
> details how often it is best to check .po file and what to do, just
> for update.
There's no really good schedule I can suggest because it's not very
predictable when we are going to commit lots of string changes.
When I find time, I'll get a web page up that shows the current status
for an "at a glance" look. In the meantime, just check every few weeks
(once a month or so if you're really enthusiastic; less often if you're
not) to see if there's been any big changes (using msgfmt --statistics).
Prior to any release, we'll make an announcement. Prior to 1.0, I hope
we'll have a couple of weeks of string freeze in order to give people
time to be 100% translated. But that's a while off yet. Not something to
worry about yet.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django I18N" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Django-I18N?hl=en
-~----------~----~----~----~------~----~------~--~---
