Wiadomość napisana w dniu 2008-11-25, o godz. 11:17, przez Thomas Guettler:
> The last days I did my first i18n application and befor I read this: > http://docs.djangoproject.com/en/dev/topics/i18n/ > {{{ > Application message files are a bit complicated to discover -- they > need > the LocaleMiddleware. > If you don't use the middleware, only the Django message files and > project message files will be processed. > > }}} > > I don't know if it is really need. But the documentation says so. Or I > read it to quickly and overlooked I thing something is wrong with docs then, because I'm speaking from my practice. On my site I have few apps with per-app translations (django-registration, django-confirmation and so on) and I have some sitewide translations for my own code. The translation keys from 3rd party apps appear in my own catalog but I left them untranslated there (as they are already translated). If the things would work as described, the strings from registration app would appear untranslated because I do not have LocaleMiddleware installed. Of course, they appear in Polish, as I expected. -- We read Knuth so you don't have to. - Tim Peters Jarek Zgoda, R&D, Redefine [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
