Error in azw3 books with reduced margins after conversion with Calibre

[Quoth]

Probably a new Kindle-MTP driver would be best. I suspect any future Amazon Kindle eink models with more than 32G storage will also use MTP.

[JSWolf]

Originally Posted by pdurrant

Moved.

This actually belongs in Kindle Formats as this has to do with KF8.

[kovidgoyal]

Originally Posted by jhowell

No, that folder is still accessible using MTP.

The issue is that calibre uses separate drivers for Kindle devices and MTP devices. Only the Kindle device driver has the code to handle Kindle thumbnails. Fixing this requires significant changes to the calibre MTP driver or the creation of a new Kindle-MTP driver..

It doesnt need changes to the MTP driver as such, just somebody with a scribe needs to write additional code in that driver to do the thumbnail dance, when the device being managed is a scribe. The scribe isnt even available in my country so...

[mg10]

Originally Posted by mg10

I've been testing and found a procedure to solve the issue with thumbnails, at least temporarily:

Firstly, I use Sigil to generate de thumbnail while converting proccess, or you can create the file with correct dimensions.
In Calibre:
Convert the ebook (in my case from epub to azw3)
Transfer it to the Kindle
After disconnect the kindle from pc, the generic thumbnail appears
Connect again the kindle to pc
With file explorer:
Go to Kindle Scribe\Internal Storage\thumbnails\
Sort the content by date. You will see the last file generated after transfering the book and disconnecting the device from pc. The format should be:

thumbnail_....._EBOK_portrait.jpg.tmp.partial

Line ends with ".tmp.partial"
This line corresponds to the last uploaded ebook. It's 0 KB of size.
Select and copy the entire name including the first extension "thumbnail_0b....._portrait.jpg". With the same format that the rest of files.
Rename the thumbnail file created with Sigil or your own method, with the copied text.
Copy the renamed file to this folder and delete the "partial" file.
After disconnecting from pc you will see the correct thumbnail.

I hope this helps whoever wants to see the thumbnails ok

Hi moderators
I don't know if you estimate that this can be uploaded in a dedicated post as a temporary solution to the thumbnail problem in Scribe for the most recent firmwares... although, maybe it's already well known

[JSWolf]

Originally Posted by DNSB

Using a Kindle Paperwhite 10th Gen with firmware 5.16.6. I added the following CSS to the ePub file's stylesheet using Sigil before converting them to azw3 in calibre 7.5.1 (note that I wrapped the extra CSS in a media query).

@media amzn-kf8 {
  html {
    margin-left: -50px;
    margin-right: -50px;
    break-inside: avoid !important;
  }
}

I did this with 3 books (Sigil User's Guide, calibre User's Guide and Fated Blades by Ilona Andrews). I opened all of them on the Paperwhite, paged around, switched to some other ebooks and back. So far nothing other than the narrower margins on those 3 were seen.

This CSS code fails on a PW5. If you remove the @media part, it works no problem. I do use -45px instead of -50px.

[Sirtel]

Originally Posted by JSWolf

This CSS code fails on a PW5. If you remove the @media part, it works no problem. I do use -45px instead of -50px.

Are you using KFX instead of AZW3, perhaps?

[JSWolf]

Originally Posted by Sirtel

Are you using KFX instead of AZW3, perhaps?

I use KF8. I cannot stand KFX.

[j.p.s]

Originally Posted by JSWolf

This CSS code fails on a PW5. If you remove the @media part, it works no problem. I do use -45px instead of -50px.

Why haven't you switched to % yet since it works for more screen sizes?

[JSWolf]

Originally Posted by j.p.s

Why haven't you switched to % yet since it works for more screen sizes?

I never thought of % and it works as is. I'll never be doing this for a Kindle larger then a PW5.

[j.p.s]

Originally Posted by JSWolf

I never thought of % and it works as is. I'll never be doing this for a Kindle larger then a PW5.

It is not a new idea to you. It was discussed extensively in the thread
https://www.mobileread.com/forums/sh...d.php?t=351310
that you participated in.

In addition, you have been quite aggressive at trying to bully people into doing things your way to support long out of date hardware and software even when it is of no interest to them. And yet here you are discouraging use of techniques that work well with all screen sizes in a time when screen sizes and pixel densities have been increasing for a while and many sizes and several pixel densities are still in wide use..

[JSWolf]

Originally Posted by j.p.s

It is not a new idea to you. It was discussed extensively in the thread
https://www.mobileread.com/forums/sh...d.php?t=351310
that you participated in.

In addition, you have been quite aggressive at trying to bully people into doing things your way to support long out of date hardware and software even when it is of no interest to them. And yet here you are discouraging use of techniques that work well with all screen sizes in a time when screen sizes and pixel densities have been increasing for a while and many sizes and several pixel densities are still in wide use..

But before then I was using px and since it's working, I'm still using it.

[j.p.s]

Originally Posted by JSWolf

But before then I was using px and since it's working, I'm still using it.

Then stop harassing others that use px instead of em in other contexts, especially when it works for them.