On Tue, 2011-05-03 at 03:59 -0700, Uri Goldstein wrote: > I'm fine in knowing that the i18n infrastructure in Django can handle > any > available language - that was the crux of my question.
to be precise, there are two parts in localisation - one is the strings in django itself and the other is the strings that you create as part of your app which you have to translate yourself. But if django itself does not have the language, your local strings will also not be translated. There are two ways of getting around this: 1. actually do the translation and get the language into django or 2. Create the directory structure for the new language in the django source code in your local version and add untranslated .po and .mo files. The second approach is a hack in that your strings will get translated but django strings will not. -- regards KG http://lawgon.livejournal.com Coimbatore LUG rox http://ilugcbe.techstud.org/ -- 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.
