On Sun, 2007-08-19 at 08:19 +0000, cesco wrote: > Thanks a lot Malcolm, I think we are getting there:-) > > > So, have a look at the debug screen and click on the "local variables" > > link just below this last line in the extended traceback. What is "s" > > here (in particular, it would be good know what type(s) is)? Also, what > > is the value of 'encoding'? > > Here are the values. > encoding: u'utf-8' > errors: u'strict' > s: <django.contrib.thumbnails.base.Thumbnail object at 0x019D4510> > strings_only: False [...] > > Hope I was able to report all the information. If the problem is, like > you suspect, the patch I applied, do you have any suggestion on how to > solve the problem? Maybe modify the patch itself following the > guidelines for transition to Unicode?
As suspected, it's the Thumbnail field that isn't handling non-ASCII filenames well. Use the instructions in [1] to port the URL display stuff (this is unicode.txt in the source tree, as well). The simple 5-step plan for porting to Unicode won't be quite enough in this case. Just giving the model a unicode method probably isn't enough, because you are still responsible for encoding the URL correctly. [1] http://www.djangoproject.com/documentation/unicode/#uri-and-iri-handling Regards, Malcolm -- Monday is an awful way to spend 1/7th of your life. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
