On Sun, 2007-02-25 at 23:56 -0600, Jacob Kaplan-Moss wrote:
> On 2/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
[...]
> > Third, there are lots of translation tickets ready for checkin, which
> > would be nice to patch in. Django's got a good reputation for i18n/
> > l10n, so getting these into 0.96 would be good. This would also give
> > translators a chance to find and clean up any final glitches before
> > 1.0
>
> Can someone can give me a one- or two-sentance explanation on how I
> should check those in (just apply the diffs? Or do I need to rebuild
> the language files, and if so how?) If so, I'll check 'em in.
Apply the patch to the correct directory under
django/conf/locales/<lang_code>/LC_MESSAGES/ .
Regenerate the .mo files, since we are storing them in subversion, too.
This requires running bin/compile-messages.py from the django/ directory
in your source tree. This should only change the .mo files for any .po
files that you just patched. It also should not generate any warnings:
if it does, they are worth fixing (or emailing about so that others can
fix them).
Then check in the 2 - 4 changed files.
If you are adding a new locale, the procedure is a little longer, but
not much worse:
(1) Add the new language to django/conf/global_settings.py
(2) Run bin/make-messages.py -l <language_code> (note that for
some locales, the language code might be of the form ll_CC,
where CC is a country or region code. E.g. fr_CA and fr_FR are
different locales, whereas we would only have a single cy
(Welsh) locale. The person supplying the locale file will
mention if it's a specific region, although sometimes experience
helps, too.
(3) The make-messages script will create the django/conf/locale
directory. Now you can add in the new django.po and/or
djangojs.po files and run compile-messages again.
All of the above is documented in docs/i18n.txt if you forget.
Also,
http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&component=Translations&order=priority
shows the outstanding translation files (they should all be in the
internationalisation component).
Mario Gonzalez posted to the i18n list yesterday that he was going to
update the Spanish one, including merging the two existing patches
together (#3097 and #3555), so you may want to leave those two for a day
or two.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
