Book downloaded via OPDS only visible in KOReader?

[avggeek]

Hi,

I've got KOReader installed on a PW2 (running FW 5.11), and connected to my local Calibre Content Server.

When I download a book from this server, I'm saving it to /mnt/us/documents which seems to be where any books downloaded from the Kindle store go to.

However, only KOReader seems to be able to see the book I've downloaded. When I switch to the standard Kindle homescreen, the book is not visible at all. I've tried switching to the "Downloaded" tab, changing the sort to "Recent", turning "Filters" on & off and even restarting the Kindle, but nothing seems to work.

When I connect the Kindle via USB, I can see that the epub is there in [Drive]:/documents.

Any suggestions on what I can do to investigate this further?

[pazos]

Kindles don't support epub and won't support them ever. At least not in FW 5.11

[avggeek]

Originally Posted by pazos

Kindles don't support epub and won't support them ever. At least not in FW 5.11

. It's been so long since I've directly loaded books onto the Kindle that I completely forgot the dialog box prompting me to convert that pops up whenever I use Calibre to directly load books onto the Kindle. Tried a different book that had an AZW3 version and that worked with the stock reader (well except for the bug below)

I found an interesting bug with non DRM AZW3 books and KOReader. When I tap on a book that an AZW3 format via the OPDS Catalog, KOReader offers to save it as a ".AZW" file and not ".AZW3". If you accept the default, the file will not open in the stock Kindle reader.

Now I know that KOReader does not support AZW3, but I'm guessing it's prompting to save as AZW based on the MIME type. This results in a dead-end where you can't rename the file in KOReader (as it ignores formats it does not support, while still allowing you to download them!) and the stock Kindle reader cannot open the file (as it's expecting AZW based on the extension but the file is actually AZW3 internally).

There's also another interesting bug here - if you hit read now immediately after downloading the file, KOReader will open it (although the rendering is messed up) but if you choose read later then you can no longer open the file in KOReader (as it will filter out AZW3 files).

[NiLuJe]

That's because we don't actually support AZW3 (i.e., KF8), only AZW (i.e., M7, a.k.a., legacy Mobi), yet they apparently share a mimetype or two ("application/vnd.amazon.mobi8-ebook" & "application/x-mobi8-ebook").

And "support" is kind of a strong word here (i.e., don't do this, just read ePubs).

If there are more precise mimetypes available (and they're actually used properly by OPDS servers), I'm all ears .

[avggeek]

Originally Posted by NiLuJe

And "support" is kind of a strong word here (i.e., don't do this, just read ePubs).

Totally fair especially since there's a lot of discussion on why AZW/AZW3 is not supported on the KOReader GH tracker.

I'm using MOBI instead of EPUB for now, as my wife uses the Kindle as well and she's definitely not going to be interested in going the KUAL>KOReader route. MOBI formats work across the stock reader (atleast on 5.11.2) and KUAL so that's a good enough compromise for me.

[pazos]

Originally Posted by avggeek

Now I know that KOReader does not support AZW3, but I'm guessing it's prompting to save as AZW based on the MIME type. This results in a dead-end where you can't rename the file in KOReader (as it ignores formats it does not support, while still allowing you to download them!)

You can enable unsupported files on the file manager (top left menu) and that will allow you to work with them.

[avggeek]

Originally Posted by pazos

You can enable unsupported files on the file manager (top left menu) and that will allow you to work with them.

That worked! Thank you!