Hi there, I have faced this kind of error a couple of times when the local wasn't correctly set on the system. Within the python interpreter it was C (ie ascii) where it should have been UTF8. Up to now, all have been resolved by correctly setting the locals system wide and within the web server (see apache setenv as mentioned in earlier post).
Regards, Xavier Ordoquy, Linovia. Le 15 juin 2012 à 07:36, kenneth gonsalves a écrit : > On Thu, 2012-06-14 at 23:46 +0200, Hendrik Speidel wrote: >> as an alternative you can provide your own Storage implementation like >> outlined here: >> >> http://source.mihelac.org/2011/02/6/rename-uploaded-files-ascii-character-set-django/ >> >> > > I have told the client to use only ascii for the time being - but that > is not a solution - for example assume that the same files are > accessed/uploaded by other applications. > -- > regards > Kenneth Gonsalves > > -- > 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. > -- 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.
