Thanks for the hint, > > Indeed, that's the latin1 encoding of 'OTOÑO', notutf8. Maybe Oracle > is getting somehow getting the client encoding confused. Try setting > the environment variable NLS_LANG = '.UTF8' for the Apache process.
I will explore that path. It clearly has some relation with the latin1/utf8 encoding. But what puzzels me is the inconsistency (sometimes the data arrives in latin1 an sothers in utf8). Any idea waht could be causing this erractic behaviour??? Whoy would different apache processes get different encondings form the database??? THX Ernesto --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
