Hi again, I solved the original problem. The django book had me confused and I placed the .po file in APP/conf/locale instead of APP/locale. It works now.
I now have another question however: I am storing various strings in the database and I would like these to be translated too. What would be the best way to manage this? I was looking at transdb (http://code.google.com/p/transdb/) and django-multilingual (http://code.google.com/p/django-multilingual/), as well as simply storing the strings multiple times manually and then checking the language in my code. None of these seem ideal, however. What do the experts suggest? 2008/6/13 Daniel Kersten <[EMAIL PROTECTED]>: > Hi, > > I am trying to get internationalization working in django, but seem to > have run into some problems. > I have added 'django.middleware.locale.LocaleMiddleware' to my list of > middleware classes, generated the i18n files and compiled them and > then changed my browsers prefered language. > Outputting request.LANGUAGE_CODE shows that django does, indeed, > detect and the language I want it to use, however, it is not using the > translated strings, but is still displaying the text specified in the > template (marked with {% trans "whatever" %}, I have also have {% load > i18n %} at the top of my template file). > > Am I missing something? Any ideas or tips as to how I can get i18n working? > > Thanks!! > Dan. > > -- > Daniel Kersten. > Leveraging dynamic paradigms since the synergies of 1985. > -- Daniel Kersten. Leveraging dynamic paradigms since the synergies of 1985. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Python Ireland" 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.ie/group/pythonireland?hl=en -~----------~----~----~----~------~----~------~--~---
