Seems to be a charset encoding mismatch.
Maybe try to get the "charset" http header from the response and pass it to the attachment in the same way you're doing with the content-disposition?
Seems to be a charset encoding mismatch.
Maybe try to get the "charset" http header from the response and pass it to the attachment in the same way you're doing with the content-disposition?