On Thu, 2007-03-22 at 11:56 -0700, sandro.dentella wrote: > Hi, > I'm starting with internationalization. All is good with django.po > & mo. but tere are words that are not > found by make-messages.py as are in variables so I add the by hand. > I'd prefere to keep them in a separate > file my_file.po. > > Compile-messages finds it and creates my_file.mo but django doesn't > seem to use it. > > Any hint?
Did you follow the setup described in http://www.djangoproject.com/documentation/i18n/#using-translations-in-your-own-projects ? You don't mention how you are trying to use this new file, so can you please confirm you have put it somewhere in your project that Django is going to expect to find it. Also did you add the LocaleMiddleware to your list of middleware packages in settings.py? That's something that is easy to overlook: Django's core translations don't need it, but you do need this for application-level translations. If you've done both of those things and it still doesn't work, please come back and ask for more help. We'll see what we can think of. A short example of how you're trying to use these strings in your code would be useful, too, I guess. Is it only the strings in your special file that are not being picked up? Or are all strings in your application not being translated? Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
