Thanks for the quick reply.
I almost gave up, but I just found something that seems to work for
me.
So I've tried:
---
filename = codecs.BOM_UTF8.decode(postfile['filename'])
---
...which gave a LookupError.
Then I tried casting to Unicode:
---
filename = unicode(postfile['filename'])
---
...which still raised a UnicodeDecodeError.
Then I found a solution on an issuetracker for a project on Google
Appengine.
---
filename = postfile['filename'].decode('utf-8')
---
...and this works... With even the weirdest characters.
I'm not sure what's going on but I'm glad it works.
Regards,
Gijs
On Nov 27, 3:24 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Looking back at the commit logs, r7548 was May, 2008. Since then we've
> committed a large file system refactor, so this may well have just been
> a bug in the old system. I don't know for sure.
>
> In the new system, there still may be a non-ASCII filename handling bug,
> since ticket #9696 was opened recently. Somebody will need to look at
> the code carefully and trace through what is happening there.
>
> Somebody might have a suggestion about how to work around your
> particular problem with Django 0.96, but there isn't going to be any
> sort of fix to Django made for that, since it's code that doesn't exist
> any longer.
>
> Regards,
> Malcolm
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
