|
No, open /mobile in a desktop browser and look at the link, the link contains no non-ascii characters, the filename you are seeing is coming from the content-disposition header which does contain the "proper" non-sanitized filename. If the Kindle browser is choking because of that its a bug there and should be reported to Amazon. Of course Amazon is completely hopeless at tech so I doubt you will get a fix from them. I might look into sanitizing the content disposition header of non-ascii chars in the /mobile interface when detecting a Kindle UA, but only if Amazon refuses to fix their bug.
|