On Tue, 2007-02-27 at 13:35 +0100, Nicola Larosa wrote:
> [nothing like the smell of a fresh self-reply in the morning ;-) ]
> 
> Nicola Larosa wrote:
> > Hi, I'm updating the Italian translation. I'll create a ticket and attach
> > the diffs today or tomorrow at the latest.
> 
> I updated the Italian translations on the already existing ticket:
> 
> http://code.djangoproject.com/ticket/1984
> 
> I hereby formally ask to be included in the Django AUTHORS file. :-)

No problems. I'll do that in the morning (too tired right now; might
screw it up).

[...]
> On a related note, I had to dig in the source code of the
> bin/make-messages.py command to discover how to update the djangojs.po file
> (that is, with the "-d djangojs" undocumented option). I'll try and put
> together a code and doc patch for this issue.

It's documented here:
http://www.djangoproject.com/documentation/i18n/#creating-javascript-translation-catalogs

(and in docs/i18n.txt in the source). Just maybe not in the place you
were looking for it.

When Hugo wrote the original docs, he put all the Javascript pieces in
one section, so it talks about using the javascript translations and
then how to generate them, etc, just like for the Python stuff.

What might be useful is a short wiki page checklist or step-by-step just
for translators. Something along the lines of running the two
make-messages.py invocations to update both files, running
compile-message.py to check for errors, etc. Please feel quite free to
create that if you want to. Or if you can think of a better way to
explain what's in the current docs, that would be good to have, 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to