Handling non-ASCII file names in the content-disposition header is always annoying. Different browsers handle them differently. For example, Firefox seemed to handle that name fine as is.
Regardless, I have changed it to deaccent/romanize, so it should generally work better.