Problem putting a book from calibre into Kindle

[Quoth]

Originally Posted by j.p.s

But wasn't established a while ago that it is better to use percent rather than negative margins, especially when a book might be viewed on a variety of screen sizes?

Yes, though either works, a percent suits a variety of kindles, as you write.

[Flaviocc]

Originally Posted by Quoth

Only edit azw3 specific settings AFTER converting epub to azw3.
That was in the instructions.

You can edit AZW3 in Calibre. Such as negative margins. A -1.5% may be be more general purpose than -30px

That was I did.

EDIT AZW3 AFTER the conversion.

I did another test on old kindle from my daughter (PPW 6th generation ---- sooo slow). And the SAME thing - firmware 5.12.2.2

My Kindle PPW5 - latest firmware.

And the Kindle PPW5 - firmware 5.14.2 (that kindle have a problem on rubber coating and Amazon send me other and blacklisted that - here I don't have to return the device, so I can use offline - like I do always).

[Flaviocc]

Originally Posted by j.p.s

But wasn't established a while ago that it is better to use percent rather than negative margins, especially when a book might be viewed on a variety of screen sizes?

Yesterday I tried with % and nothing....I will try the edit option with -1.5% now....

EDIT.:

RESULTS with 1.5% - the problem is the same BUT now it's intermittently. How? sometimes the message pops up, sometimes the font is changes automatically (like for some default settings) and sometimes works ok. It's a bug (kindle or book).

I will scramble that other book and upload here.

[dedeca]

I have the same issue when sending epub via email or using Send To Kindle. The error message appears when trying to move forward or backward a page. The "solution" I found was: when the error message appears, enter the book again and change some font or layout settings of the book, when you do this the error message will appear, close the book and open it again. It's not a permanent solution because occasionally the problem comes back and I have to repeat the process.

[JSWolf]

Originally Posted by j.p.s

But wasn't established a while ago that it is better to use percent rather than negative margins, especially when a book might be viewed on a variety of screen sizes?

-45px is what I use for a PW5.

[Flaviocc]

Originally Posted by dedeca

I have the same issue when sending epub via email or using Send To Kindle. The error message appears when trying to move forward or backward a page. The "solution" I found was: when the error message appears, enter the book again and change some font or layout settings of the book, when you do this the error message will appear, close the book and open it again. It's not a permanent solution because occasionally the problem comes back and I have to repeat the process.

OOhh tks ! I'm not crazy

It's the same bug, but started by other way. And sometimes your workaround works here and sometimes no.

[JSWolf]

Originally Posted by Flaviocc

OOhh tks ! I'm not crazy

It's the same bug, but started by other way. And sometimes your workaround works here and sometimes no.

The code has to be added to the KF8 eBook AFTER conversion and you cannot use your -30px code at the same time.

Get rid of your extra CSS. Then after conversion, put in

html {
  margin-right: -45px;
  margin-left: -45px;
  break-inside: avoid !important;
}

at the top of the CSS. Also, make sure there is no @page of any kind in the CSS. You do not want two sets of global margins competing.

If you do not follow my directions, it's not going to work.

[Flaviocc]

Originally Posted by JSWolf

The code has to be added to the KF8 eBook AFTER conversion and you cannot use your -30px code at the same time.

Get rid of your extra CSS. Then after conversion, put in

html {
  margin-right: -45px;
  margin-left: -45px;
  break-inside: avoid !important;
}

at the top of the CSS. Also, make sure there is no @page of any kind in the CSS. You do not want two sets of global margins competing.

If you do not follow my directions, it's not going to work.

Jon, I DID that.

ok...I will look now for @page on css. and back here.....

I followed exactly what you told me. But the @page is new info....I'll do now.

[JSWolf]

Originally Posted by Flaviocc

Jon, I DID that.

ok...I will look now for @page on css. and back here.....

I followed exactly what you told me. But the @page is new info....I'll do now.

No you didn't. You have multiple @page and the CSS is not correct.

html, .calibre {
  margin-right: -1.5%;
  margin-left: -1.5%;
  break-inside: avoid !important;
}

Use -45px until it works.

The problem may be in your settings.
Go to preferences > Common options > Page setup and set all of the margins on the left side to -0.1pt.

This is the CSS to use.

html {
  margin-right: -45px;
  margin-left: -45px;
  break-inside: avoid !important;
}

[Flaviocc]

Originally Posted by JSWolf

No you didn't. You have multiple @page and the CSS is not correct.

html, .calibre {
  margin-right: -1.5%;
  margin-left: -1.5%;
  break-inside: avoid !important;
}

Use -45px until it works.

The problem may be in your settings.
Go to preferences > Common options > Page setup and set all of the margins on the left side to -0.1pt.

This is the CSS to use.

html {
  margin-right: -45px;
  margin-left: -45px;
  break-inside: avoid !important;
}

Jon, this is another test with %

I'm told you, I did.

I did right now:

1 - EPUB to AZW3 in CALIBRE WITHOUT ANY OTHER SETTINGS OR EXTRA CSS.

2 - Calibre give me the AZW3.

3 - Opened the AZW3 with CALIBRE editor

4 - PASTED your code on the top of the main CSS

5 - Looked for any @page CSS\

And the same BUG.

You tried to replicate what I wrote here?


I will look here as you said: The problem may be in your settings.
Go to preferences > Common options > Page setup and set all of the margins on the left side to -0.1pt.


I never changed this settings but I will take a look.

One note - ALL MY SETTINGS WORKS AT PAST.

[Quoth]

Originally Posted by dedeca

I have the same issue when sending epub via email or using Send To Kindle.

All bets are off if you use Amazon, because they convert. Only do your own conversions and use USB transfer.

[Flaviocc]

OK, I will give up.

I DID step by step and did another test:

EPUB to AZW3 - WITHOUT ANY SETTINGS / EXTRA CSS ETC.

Page setup in Calibre - as Jon said: -0.1pt

Calibre give me the AZW3 - and I load this PURE AZW3 without any changes on Kindle. Kindle display to me the book with the default kindle firmware margins. No error. Fwd and bcw pages - NO ERROR.

I deleted this file from Kindle.

Opened the same AZW3 file on Calibre editor - look for any @page setup css (none) - Pasted the JON code ON THE TOP of the CSS, saved and load on Kindle.

The book now has the margins as I set. Fwd a few pages. Leave the book. Open again, fwd a page and ERROR. Closed the book, opened another randomly book, close, open the book 1 again and ERROR.

So, the error appears AFTER the code.

And in the past I used to use the SAME code without any problems.

EDIT.: just to be clear - I have a lot of books that I did the margin settings before, that I had no problem when I read them, I opened a few of these books and I have the error - so it's not a config problem.

[dedeca]

Hey, try changing your Kindle device's language to English. I did here and it worked! haha I don't know what's causing it.

[Flaviocc]

Originally Posted by dedeca

Hey, try changing your Kindle device's language to English. I did here and it worked! haha I don't know what's causing it.

WTF!!!!!!!!!!!!!

Works!!!

I'll test again and again.

Tks !!!

You are from BR or another non English language?

That was the reason why other users that use Kindle in English don't be able to replicate the bug. WTF!!!

Thank you so much.

Tested here with a lot of ebooks - open, close, change ebook to another, change fonts - and OK !!! The problem is when the kindle is set to PT-BR Language. Don't know if happen on other language.

[dedeca]

Originally Posted by Flaviocc

You are from BR or another non English language?

Sim haha brasileiro aqui

I tried adding pt-BR to <dc:language> in the content.opf file. The error message still persists. I really don't know what is causing this.