Forum: Author Hangout

Under the html settings section, you need to define the page-break for the h1

I do the formatting in Word so I use "Heading 1" to format the chapter headings. Calibre converts that to the appropriate HTML.

but there's no clear cut way of forcing < H1> headers to create a page break

Calibre must recognize Word's page break and does the magic in HTML.

Sorry, but I've checked several Calibre produced ePubs, and they don't carry over the manual page breaks from WORD (which is why I properly coded the CSS entry in my ePubs).

That's an issue with the way MS Word codes the format data, not with how Calibre handles it.

As to the page break within an epub within Calibre, the default is to have a page break before a H1 so the headings work in the html.

Mind you Libre Office now has a one-click process to create epubs, and it breaks up the html code based on the H1 Heading style.

As to the page break within an epub within Calibre, the default is to have a page break before a H1 so the headings work in the html.

Except every once in a while the epub generated from Calibre did not have a page break before a chapter heading which was defined as "heading 1" (H1). But when I put a Word page break before the chapter headings I never have the problem.

Except every once in a while the epub generated from Calibre did not have a page break before a chapter heading which was defined as "heading 1" (H1). But when I put a Word page break before the chapter headings I never have the problem.

I never had that problem happen to me.

I never had that problem happen to me.

It's happened to me several times when using the Calibre e-book Viewer to check out the results of the epub created. It's never happened since I put the page breaks before the chapter headings.

I was afraid I would end up with a blank page before each chapter (two page breaks) but that never happened.

Have you checked your ePub code?

To do that is way above my pay grade.

Sorry, but I code ALL of my ePubs by hand

CW, please make up your mind as to what you're doing and complaining about!

Before you said

Sorry, but I've checked several Calibre produced ePubs, and they don't carry over the manual page breaks from WORD

which I said would be a MS Word code issue, not a Calibre issue. Now you talk about using html. So why did you mention the MS Word page break to start with if you aren't using it?

Calibre must recognize Word's page break and does the magic in HTML.

Actually, I think you'll find it recognises the Heading 1 and applies that then breaks up the html as per the H1 code.

As always, the more you learn, the more you realize how little you know.

I'm not saying this to be taken at anything other than face value.

I was writing these stories because I've always wanted to be author, and finding SOL allows me to not only write material, but to post it so that other people can either enjoy it or not at their own discretion is almost like my childhood dream finally coming true.

The minor detail that I've had people on here that like my work so much that they're willing to pay for something I'm posting for free is like the ultimate compliment.

So it prefers DOCX over ODT. And surprisingly, DOCX is more preferred than HTML. I'm also surprised that MOBI is more preferred than EPUB.

My understanding from comments seen about Calibre in the past, is that is a 'user' preference list in that it shows the order of frequency of the users. I always took it to mean that the most frequently converted files were Lit being converted to something else or converted from Lit, then so on down the list.

I just happened to stumble upon this in Calibre documentation:

Switch, I forgot to mention in the earlier post, what you have to remember is that Calibre is not a tool for creating e-pubs from scratch, although we use it as such. Calibre is a tool for converting e-books to other formats so people can read them on different readers to the readers they first purchased the e-books for. Thus the creators of Calibre have always had, as their primary focus, conversion from one e-book format to another and their coding reflects that aim. The later input types have been added as people have requested them. When I first started using Calibre the list of input options was only half of what it is now.

MOBI is a very early e-book format. It predates e-pub

MOBI was created in 2000 by Mobipocket (Amazon purchased Mobipocket in 2005, Kindle 1 was released in 2007). EPUB was created ~2007 by the IDPF (International Digital Publishing Forum).

This is where Chapters and Page Breaks is discussed in Calibre's documentation: https://manual.calibre-ebook.com/conversion.html

calibre has two sets of options for chapter detection and inserting page breaks. This can sometimes be slightly confusing, as by default, calibre will insert page breaks before detected chapters as well as the locations detected by the page breaks option.

So if it detects a chapter heading it should do the page break. But I've had situations where it didn't (I don't have the specifics).

And then it says:

By default, calibre uses the following expression for chapter detection:

//*[((name()='h1' or name()='h2') and re:test(., 'chapter|book|section|parts+', 'i')) or @class = 'chapter']

This expression is rather complex, because it tries to handle a number of common cases simultaneously. What it means is that calibre will assume chapters start at either < h1> or < h2> tags that have any of the words (chapter, book, section or part) in them or that have the class="chapter" attribute.

My chapter names start with "Chapter" (e.g., Chapter 1) so it finds the word "chapter." I remember one situation where it didn't do the page break (and maybe it was the only situation) when my chapter name was "Preview - Chapter 1" (it was some preview chapters of a different novel at the end of the current novel). It appeared in the Table of Contents but did not have a page break before it. So maybe it was that it started with the word "Preview" rather than "Chapter."

http://validator.idpf.org/

Thanks for the link. Although it says it's in Beta.

All my epubs validated. They were created with Calibre using docx files as input.