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. So, the .po files are automatically generated daily, updating the status page. I even contacted Luebe from TortoiseSVN project for his status update mechanism if we were interested in something similar for Django. What anyone from the translation group thinks about it? Would you like to have such translation status page? In any case, Malcolm, could you please post the suggested approach with detailed steps for maintaining translation on the Django wiki? 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. Thanks, Radek On 4/8/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > Hi Georgi, > > On Sat, 2007-04-07 at 20:55 +0200, Georgi Stanojevski wrote: > > > > One little question about updating translations which I'm not 100% sure > > about, and don't want to break something. :) > > > > Am I expected to run ./bin/make-messages.py on my svn version when I > > want to update the django translation and file a ticket with that version. > > > > Or should I wait until LC_MESSAGES/django.po in the official svn tree > > gets new messages, basically when the core developers run > > ./bin/make-messages.py? > > > > I wanted to update some bad translations in my language but when I run > > ./bin/make-messages.py I got some new and fuzzy translations and don't > > know which .po file to attach with the ticket. The one after > > ./bin/make-messages.py or the original from svn with only the fixed > > translations? > > You should run bin/make-messages.py and then update the newly generated > PO file and upload that (or even just the patch generated by "svn > diff"). > > The Django maintainers are hardly ever going to run make-messages.py on > files that translators are maintaining. it's generally a bad idea for > non-translators to touch those files. The only possible exception to > this might be just before a major release (like 1.0), when we might > consider updating all the PO files to include precisely the messages in > the Django release, rather than whatever was there last time the > translator touched the file (which could be months old, sometimes). > However, that's not clear yet and it's a long way off in any case. > > Do you understand why fuzzy messages appear and what to do with them? > Was that part of your question, too? > > 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 -~----------~----~----~----~------~----~------~--~---
