On Tue, May 3, 2011 at 12:39 PM, Uri Goldstein <uri.goldst...@gmail.com> wrote: > Thank you Tom and KG. > > I now see that my friend was right(!). > http://docs.djangoproject.com/en/1.3/topics/i18n/localization/#how-to-create-language-files > says: "Django does not support localizing your application into a locale for > which Django itself has not been translated." > > The motivation for this is explained there but I personally find this > disappointing. In my case I only care about my strings and I don't mind > mixing the translated language with English. >
The 'motivation' is a technical limitation, and you omitted to quote the part explaining how you can add translations for languages that Django itself does not have a translation for, a process which takes but a few seconds. Having docs is good, reading and comprehending the docs is better. You are looking for issues where there are none. If you require your site to be in Mongolian, it can be in Mongolian, even though Django does not itself have a Mongolian translation, it just requires a minuscule amount of effort on your part - as it would in any gettext based translation system. 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.
