here´s a snippet which shows an implementation: http://djangosnippets.org/snippets/1710/
however, the only cross-browser solution I´ve come across is the one I ´ve posted above. regards, patrick On 22 Nov., 16:40, David De La Harpe Golden <david.delaharpe.gol...@ichec.ie> wrote: > Looked into this a bit (will undoubtedly bite us soon): > > On 22/11/10 13:54, Torsten Bronger wrote: > > > Is there a standard at all for how non-ASCII in the header field > > "Content-Disposition" is supposed to be encoded? > > The rfc5987 [1] based filename*=UTF-8''bl%c3%a4h mechanism very recently > exists, otherwise iso-8859-1/ascii, pretty much... See the rfc author's > test page [2] > > Talking chromium implementing it days ago sort of very recent, mind [3] > > While some present-day clients apparently do try to interpret the > filename=... into utf-8 in one manner or another (I suppose you could > get into UA detection if you have the patience/need), I think servers > (including django apps) can maybe start to send both a fallback standard > filename= in no more than iso-8859-1 and the now-standard filename*= in > utf-8 as seen in [4], though there are some compat issues with that too [5] > > [1]http://tools.ietf.org/html/rfc5987 > > [2]http://greenbytes.de/tech/tc2231/#encoding-2231-char > > [3]http://code.google.com/p/chromium/issues/detail?id=57830 > > [4]http://greenbytes.de/tech/tc2231/#encoding-2231-fb > > [5]https://bugzilla.mozilla.org/show_bug.cgi?id=588781 -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
