Set up the internationalization infrastructure

[GoogleCodeExporter]

This issue will be used to track the progress of the internationalization
(i18n). The following tasks need to be performed :
  * Mark all the strings with this templatetag in all the templates {%
trans "Translate this string" %}
  * Mark all the strings with _() in the python files
  * Create the message files as place holder for the a couple of language :
spannish, german, french

I plan to use django-rosetta as part of the infrastructure, this will lower
the barrier  in collecting the translation string from hypothetic contributor.

Original issue reported on code.google.com by yann.ma...@gmail.com on 27 May 2008 at 7:06

[GoogleCodeExporter]

the changeset r37 add all the machinery to get the i18n. I have also added a 
first
draft for the french translation.

Original comment by yann.ma...@gmail.com on 28 May 2008 at 9:08

• Changed state: Started

[GoogleCodeExporter]

The internationalisation infrastructure is now in place. In order to add a new
language you should run : 
# make-messages.py -l <LANGUAGE_CODE>
to update the messages :
# make-messages.py -a
to compile the messages :
# compile-messages.py --settings="examples.settings"

Note that compile-messages.py and make-messages.py should be in your %PATH%.

Original comment by yann.ma...@gmail.com on 29 May 2008 at 10:49

• Changed title: Set up the internationalization infrastructure
• Changed state: Fixed