AZW3 Page-Break didn't work

[DropDeadAlex]

Hello guys!

I've researched a lot and tried so many ways, but I didn't find a way to use the CSS "page-break-before: always" property in a book in AZW3 format.

Does anyone knows if there is some limitation in AZW3 with that?

...my intention was to put a pageBreak() before each subchapter. The main chapters are already splitted in diferent .html files.

[GrannyGrump]

How are you creating the azw3 file?
Do you begin with an epub, and convert? If you do that, and convert with kindlegen, or "Kindle Previewer for PC" which uses kindlegen, or convert with Calibre, I think the page-break-before should work.

I have converted epubs that way, and in the Kindle Previewer the page break does work. But I do not have a Kindle device to test it on.

Is your chapter wrapped in a <div> that has page-break-inside: avoid?

[HarryT]

Originally Posted by GrannyGrump

How are you creating the azw3 file?
Do you begin with an epub, and convert? If you do that, and convert with kindlegen, or "Kindle Previewer for PC" which uses kindlegen, or convert with Calibre, I think the page-break-before should work.

I have converted epubs that way, and in the Kindle Previewer the page break does work. But I do not have a Kindle device to test it on.

It’s always worked absolutely fine for me on a Kindle. I just add the “page-break-before: always” to the CSS for whatever header level I’m using for chapter headings.

[Hitch]

Originally Posted by HarryT

It’s always worked absolutely fine for me on a Kindle. I just add the “page-break-before: always” to the CSS for whatever header level I’m using for chapter headings.

Me too. never had a problem.

Hitch

[theducks]

Me too

If it is not working, then there is a code (or conflicting code) problem.

<p class="Style1 Style2">

Style1 putith, Style2 taketh back

While it is valid to code that way, I prefer a single complete style.
Way easier to troubleshoot

[AlanHK]

Originally Posted by DropDeadAlex

Hello guys!

I've researched a lot and tried so many ways, but I didn't find a way to use the CSS "page-break-before: always" property in a book in AZW3 format.

It would help if you cited the CSS and the HTML that uses it.

e.g.

.mbp_pagebreak {page-break-after: always; margin: 0; display: block}
Note this is page-break -after.

I think that is more reliable and the way mobis are usually coded.

invoked in a stand-alone line like
<div class="mbp_pagebreak"></div>


The Calibre viewer (ebook-viewer.exe) is useful to inspect mobi and AZW.
It's not a perfect previewer, but lets you select and "Inspect" text to see the underlying code and its interactions and change it to see the results, so you can work out if some other code has negated what you wanted.

[GrannyGrump]

I just remembered when I had a problem with page-break-before: always--- it would not work in EPUB.
If the page-break was preceded by <hr/> (horizontal rule), it failed --- it needed to have TEXT preceding it.

see this thread:
https://www.mobileread.com/forums/sh...d.php?t=270007

Maybe the OP is having a similar glitch?

[BettoReader]

Originally Posted by DropDeadAlex

Hello guys!

I've researched a lot and tried so many ways, but I didn't find a way to use the CSS "page-break-before: always" property in a book in AZW3 format.

Does anyone knows if there is some limitation in AZW3 with that?

...my intention was to put a pageBreak() before each subchapter. The main chapters are already splitted in diferent .html files.

If this can help you, after inserting in my azw3 the css rule

page-break-after: always;

I had to carry out a reconversion on the same type (AZW3 -> AZW3).
Simply saving and copying the azw3 on the kindle I did not get the desired result (even if in the calibre viewer I got the page-break as expected).

So investigating I tried to reopen the reconverted AZW3 and I noticed that the html file was divided at the points where I wanted the page-break (perhaps in this way the kindle correctly detects the page-break).

In the book before the conversion I had ~ 80 html files and in the converted one ~ 140 html files.

[Arjayem]

Originally Posted by BettoReader

If this can help you, after inserting in my azw3 the css rule

page-break-after: always;

I had to carry out a reconversion on the same type (AZW3 -> AZW3).
Simply saving and copying the azw3 on the kindle I did not get the desired result (even if in the calibre viewer I got the page-break as expected).

So investigating I tried to reopen the reconverted AZW3 and I noticed that the html file was divided at the points where I wanted the page-break (perhaps in this way the kindle correctly detects the page-break).

In the book before the conversion I had ~ 80 html files and in the converted one ~ 140 html files.

Very interesting, I can’t get page-break-before to work, but every forum I read insists it should. But if as you say it needs something to generate a file break using the page-break-before then this sheds some light on the problem.
New file results in a page break, no problem, I’ve been using new file to give a page break, but find the number of files messy, particularly if the section is short.

Does this mean everyone claiming page-break-before works are wrong and “something” is just using the page-break-before to generate a new file

[Quoth]

All my new pages seem to start new files. Seems to be the only thing that works on KF7.

Long ago KDP told me to switch from docx to epub2 when the page breaks in KF7 and AZW3 (KF8) downloads vanished. That solved the problem as long as each page break was a new file. It doesn't matter how many files it makes as they are all in an outer "wrapper" anyway, a simple Zip for epub actually, so there is no file system fragmentation. The entire collection of "files" for mobi, azw3 or epub is one physical file.

[Hitch]

Originally Posted by Arjayem

Very interesting, I can’t get page-break-before to work, but every forum I read insists it should. But if as you say it needs something to generate a file break using the page-break-before then this sheds some light on the problem.
New file results in a page break, no problem, I’ve been using new file to give a page break, but find the number of files messy, particularly if the section is short.

Does this mean everyone claiming page-break-before works are wrong and “something” is just using the page-break-before to generate a new file

Well, stoopid question (mine, I mean):

how are you deploying page-break-before:always?

Hitch

[jhowell]

page-break-before:always is supported by the Kindle platform. However there can be problems if you use calibre.

Enhanced Typesetting (KFX format) handles it by splitting the content into a new section (the KFX equivalent of a new HTML file) at that point.

Conversion using Amazon's kindlegen adds <mbp:pagebreak/> in MOBI7 and <div data-AmznPageBreak="always"/> in KF8 to make the page break actually function.

Conversion using calibre handles page breaks slightly differently. Calibre will change page-break-before:always into a split of the HTML file in KF8.

There is a bug in calibre's editor. It does not handle data-AmznPageBreak="always" properly resulting in broken page breaks if you attempt to edit a KF8 format book that was produced using kindlegen. Also you can't just add page-break-before:always into a KF8 book using calibre's editor since it does not convert it into data-AmznPageBreak="always" when you save the file.

[Arjayem]

Originally Posted by Hitch

Well, stoopid question (mine, I mean):

how are you deploying page-break-before:always?

Hitch

I have had a light bulb moment, and as with all light bulb moments you can't believe how stupid you've been.
What you see in calibre is not the azw3 as seen by calibre (doh!) Calibre converts the html you do see to azw3 format (obvious to me now) and calibre is not converting page-break- before (etc) into azw3 format page breaks. Calibre only converts new files to page breaks.
Not wishing to criticise such an excellent product as calibre, but as this is html supported by kindle it ought to be converted appropriately.
What I need is a different editor, but as this is my only gripe with calibre I won't bother, besides I can't find one at all let alone one that's better.

[Hitch]

Originally Posted by Arjayem

I have had a light bulb moment, and as with all light bulb moments you can't believe how stupid you've been.
What you see in calibre is not the azw3 as seen by calibre (doh!) Calibre converts the html you do see to azw3 format (obvious to me now) and calibre is not converting page-break- before (etc) into azw3 format page breaks. Calibre only converts new files to page breaks.
Not wishing to criticise such an excellent product as calibre, but as this is html supported by kindle it ought to be converted appropriately.
What I need is a different editor, but as this is my only gripe with calibre I won't bother, besides I can't find one at all let alone one that's better.

Uh, Sigil?

Why not just use Sigil to finish the book, if that's the only thing you're running into that bugs you? Use Sigil, get a final ePUB with your page-breaks in it and then drop that onto KP3. ???

Hitch

[odamizu]

Originally Posted by Hitch

... Use Sigil, get a final ePUB with your page-breaks in it and then drop that onto KP3. ???

Or use Sigil with Doitsu's KindleGen plugin installed. When you're done editing ePUB to your satisfaction, run the KindleGen plugin to output an azw3, dual-mobi, KFX ... without ever leaving Sigil.