Problems with Network Server, Kindle Paperwhite and Filename

[youvedone]

Hi there,

It looks like I'm having a little bit a specific problem here with calibre and the paperwhite device.
-Calibre 7.19 (before 7.16) installed on Windows
-Run it mostly as service but for a test i also startet the content server via ui
-All fine with the books and sharing epub and mobi format
-Except I have the problem with some book I'm not able to download on the amazon Kindle Paperwhite.

- altough these files download file in every other browser

Filenames not working:
- Blutzahl -1- - Horst, Jørn Lier & Enger, Thom_295.mobi
- Mörderfinder -1- Die Spur der - Strobel, Arno_286.mobi
- Düstergrab - Fölck, Romy_297.mobi


Are there limitations on amazon kindle? I'm pretty sure. Kindle is telling me something like:
The Browser can't download the file. It can only download files with .AZW, .PRC, .MOBI, .TXT

For me it looks like the filename with special chars is not allowed by the kindle browser.. First hints to the "ø".. Same at "Mörderfinder" it had trouble, too. Then Düstergrab.

To verify I attached on a working download an "ü" at the title and restarted the content server.
For example
- Das Herz der Zwerge 2_ Roman - Markus Heitz_285.mobi --> could be downloaded
- Das Herz der Zwerge 2_ Roman ü - Markus Heitz_285.mobi --> not working in kindle but every other browser.

Is there somehere possible to "simplify" the filenames for the contentserver so the paperwhite is able to download?


Kind regards
Chris

[kovidgoyal]

Use the mobile view of the server, add /mobile to the end of the server URL in the kindle browser. That will automatically simplify the names.

[youvedone]

I everytime use the mbile variant...

[kovidgoyal]

The mobile variant makes all download filenames plain ascii.

[youvedone]

Originally Posted by kovidgoyal

The mobile variant makes all download filenames plain ascii.

The downloadname of thehlne is same:
Blutzahl -1- - Horst, Jørn Lier & Enger, Thom_295.mobi

[kovidgoyal]

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.

[kovidgoyal]

Actually since I am pretty certain waiting for amazon is pointless, here you go: https://github.com/kovidgoyal/calibr...38c5a13477cab1

[youvedone]

Thanks in advance.
That is/was my feeling, to. Let me check. I think, I need to build a calibre version based on that commit to verify.

[kovidgoyal]

You dont need to build just use this fridays preview release

[youvedone]

I've tested it right now, and can confirm that the release calibre-64bit-7.19.101 is working. Thanks.
Filed a support case with amazon nevertheless.