On Tue, May 3, 2011 at 11:59 AM, Uri Goldstein <uri.goldst...@gmail.com> wrote: > Thank you for your quick response. > > I now realize that my friend was referring to "the strings commonly > displayed by Django". Naturally these are yet to have been translated to all > available languages but I'm sure we'll get there sme day :). > > I'm fine in knowing that the i18n infrastructure in Django can handle any > available language - that was the crux of my question. >
If you wish to have a language available that is not in Django's set of base translations, so that you can add your own translations for that language for your parts of the site, then you have to go through some additional hoops to allow this. This is probably what your friend was referring to. http://docs.djangoproject.com/en/1.3/topics/i18n/localization/#how-to-create-language-files Cheers Tom -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
