Updating this after problem resolution, the issue was with the translation (.po and .mo) files, not Django itself. Old gettext with Windows may have been the culprit, found using Linux to create the message files much more reliable.
On Feb 12, 10:21 am, Scott <scott....@gmail.com> wrote: > Hi Karen, > > Thanks for the suggestion on upgrading, I followed the steps to bring > the Helper up to the latest revision hosted on Google code, but am > still seeing the UnicodeEncodeErrors (not to mention that the > languageroutingby cookie ceased to work). > > Does anyone have a working build that can verify that Unicode support > in .mo files is working? That will help me narrow the issue down to > either configuration of the gettext util that I'm using locally, or > the environment. > > Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
