Author: mtredinnick Date: 2007-03-12 04:02:18 -0500 (Mon, 12 Mar 2007) New Revision: 4707
Modified: django/trunk/docs/i18n.txt Log: Fixed #3084 -- Documented that Django's core must be translated into a particular locale for application translations in that locale to work. Modified: django/trunk/docs/i18n.txt =================================================================== --- django/trunk/docs/i18n.txt 2007-03-12 08:43:07 UTC (rev 4706) +++ django/trunk/docs/i18n.txt 2007-03-12 09:02:18 UTC (rev 4707) @@ -282,6 +282,16 @@ Once you've tagged your strings for later translation, you need to write (or obtain) the language translations themselves. Here's how that works. +.. admonition:: Locale restrictions + + Django does support localising your application into a locale for which + Django itself has not been translated -- it will ignore your translation + files. If you were to try this and Django supported it, you would + inevitably see a mixture of translated strings (from your application) and + English strings (from Django itself). If you are wanting to support a + locale for your application that is not already part of Django, you will + need to make at least a minimal translation of the Django core. + Message files ------------- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
