On Mar 20, 10:06 pm, elm <ernesto.la...@gmail.com> wrote:
> 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???
Are you sharing the web server with web applications written using
something else, such as PHP? If PHP is playing with the language
settings, you might be hitting an ordering problem. That is, it works
if any PHP code gets executed first in a specific process and doesn't
otherwise, or vice versa.
You also need to be careful about stopping and starting Apache using
sudo command without the -H option. Leave out the -H option and
environment from your personal account leaks into that of Apache. So,
things may work if you use sudo without -H, but then if system reboots
and Apache started at boot time, then it lacks that same environment
that you as a user have and which was leaking into Apache environment.
Thus things can then break.
Graham
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
