Converting to Kepub with Calibre doubles the page count.

[JSWolf]

Originally Posted by ViktorEvil

I have checked both toc files and they are identical and have the correct number of files listed.

The book displays the pages correct and in the right order etc, it is just the page numbers that are off

Forget the HTML ToC exists. It's worthless. Just ignore it or delete it.

What you need to do is edit the NCX ToC to add ALL of the HTML files to the ToC. If you are missing any HTML files in the NCX ToC, the page numbers can be off.

In the calibre editor, go to Tools > Table of Contents > Edit Table of Contents and edit the ToC to add in the missing HTML in the same order they are in in the Text list in the left of the editor.

[DNSB]

Originally Posted by xhaydenx

I've got a Kobo Clara HD and I use a Calibre to manage all my Epubs. I convert them in Calibre to Kepub and then transfer them over.

Originally Posted by JSWolf

Forget the HTML ToC exists. It's worthless. Just ignore it or delete it.

What you need to do is edit the NCX ToC to add ALL of the HTML files to the ToC. If you are missing any HTML files in the NCX ToC, the page numbers can be off.

In the calibre editor, go to Tools > Table of Contents > Edit Table of Contents and edit the ToC to add in the missing HTML in the same order they are in in the Text list in the left of the editor.

Jon, Jon, Jon... I hate to burst your bubble but in an ePub3, the html navigation document is not worthless. It is the navigation document for that ePub. You can have an optional NCX ToC which is not used by an ePub3 renderer rendering an ePub3 document. The only reason for the NCX document in an ePub3 is for backwards compatibility with ePub2 renderers.

Since it is clearly stated that the OP is using kepub—you did read the original message in this thread which I quoted above?—they are using the ePub3 renderer and any ePub3 documents will be using the HTML navigation document.

[ViktorEvil]

When I said I checked the toc files I mean in both an epub and converted kepub and both NCX toc files were correct listing all html files in the correct order. The book loads an reads correctly but the page numbers are off by 100% of the total pages after the cover

In a book of 300 pages:
The cover is page 1
page 2 is displayed as 300
pages then count up correctly until
page 300 is displayed as 600

I can read the book fine but the slider at the bottom of the menu jumps to halfway after I click past the cover

[JSWolf]

Originally Posted by DNSB

Jon, Jon, Jon... I hate to burst your bubble but in an ePub3, the html navigation document is not worthless. It is the navigation document for that ePub. You can have an optional NCX ToC which is not used by an ePub3 renderer rendering an ePub3 document. The only reason for the NCX document in an ePub3 is for backwards compatibility with ePub2 renderers.

Since it is clearly stated that the OP is using kepub—you did read the original message in this thread which I quoted above?—they are using the ePub3 renderer and any ePub3 documents will be using the HTML navigation document.

I'm talking about the HTML ToC that most eBooks come with that you don't need be it ePub3 or ePub2 because it's not really used.

[DNSB]

If the ebooks are public domain, you could attach one of them to a message in this thread so others can see the exact structure. If they are not public domain, you can use the ScrambleEbook: Getting help with copyrighted books plugin to scramble the kepub and then attach it to a message here. You will likely have to change the extension to end in .epub since I don't think MobileRead allows attaching .kepub files.

[DNSB]

Originally Posted by JSWolf

I'm talking about the HTML ToC that most eBooks come with that you don't need be it ePub3 or ePub2 because it's not really used.

In many ePub3 ebooks, the navigation document also serves as the HTML ToC document. In an ePub3, the NCX navigation document is not used. It's a vestigial appendix.

[JSWolf]

Originally Posted by DNSB

In many ePub3 ebooks, the navigation document also serves as the HTML ToC document. In an ePub3, the NCX navigation document is not used. It's a vestigial appendix.

In most eBooks, there is an HTML ToC that's not the NAV or the NCX. That's the one that's not needed.

[Quoth]

Originally Posted by JSWolf

In most eBooks, there is an HTML ToC that's not the NAV or the NCX. That's the one that's not needed.

It's copying the paper book. It's not needed on any decent ereader or app.

[JSWolf]

Originally Posted by Quoth

It's copying the paper book. It's not needed on any decent ereader or app.

No it's not copying the pBook. Not many novels have a ToC. So the HTML ToC inside the book is not part of the pBook in most cases.

[DNSB]

Originally Posted by JSWolf

No it's not copying the pBook. Not pBooks don't have a ToC. So the HTML ToC inside the book is not part of the pBook in most cases.

Can we get a translation on exactly what "Not pBooks don't have a ToC" means? Followed by the almost equally weird "the HTML ToC inside the book is not part of the pBook in most cases."

Are you trying to say that the HTML ToC found in an ebook is not part of the pBook in most cases? If so, I just checked 11 fiction pBooks and all of them had a ToC. See attached sample image from Blindsight. The only difference between the ToC in the paper and electronic book versions is that the paper book version has page numbers.

[JSWolf]

Originally Posted by DNSB

Can we get a translation on exactly what "Not pBooks don't have a ToC" means? Followed by the almost equally weird "the HTML ToC inside the book is not part of the pBook in most cases."

Are you trying to say that the HTML ToC found in an ebook is not part of the pBook in most cases? If so, I just checked 11 fiction pBooks and all of them had a ToC. See attached sample image from Blindsight. The only difference between the ToC in the paper and electronic book versions is that the paper book version has page numbers.

I meant to say that not many novels have a ToC.

And in that case, the HTML ToC is not duplicating anything as it's not in the novel.

[DNSB]

Originally Posted by JSWolf

I thought it was the NCX Toc for ePub2 and ePub3 that KePub uses for page numbers. I've nevr edited the ePub3 Toc. I've always added to the NCX ToC for KePub.

In a ePub3, the navigation document is the one used for navigation. In an ePub3, the NCX document is only used when an ePub2 renderer is used.

[nana77]

Hi, can I ask if it's possible to solve this? I guess the problem on a book I'm reading it's similar: the book shows as having 438 pages and what makes me annoying is that the first page shows as 219.
All other stuff seems ok, thought I'd would like to try to solve it.
I'd read in internet that if there are epub and kepub of the same files in library it's possible that the converter mishaps something, or similar. Tried to use a new calibre library, within just that book file, tried removing epub and let only the kepub version, tried the opposite... nothing changed (didn't reboot the device, btw, so I'm not sure if metadata in there were really removed).
Tried to put "0" as value on "slpit files larger than" on "kepub output" into "preferences".
I have a Kobo Forma and use "Generic e-ink HD" in "Common Options" "Pages Setup" for "Output" and "Default Profile (which says' for 1600x1200)" for Input.

If I use the raw epub file, sideloading (copying and paste) to the device from the files application the book seems fine (but doesn't has the others enhancements from Calibre), and the page count start by page 1.

So it's something within the conversion I guess.
May someone give an advice about?
Thanks in advance.

Ps: the book is not recent, so I'll try some other settings, as maybe it doesn't fits fine within 1600x1200 input..

[nana77]

For the moment I had a nice result by converting it from the pdf file (to the Kobo epub/kepub).
The settings I'm using are these, btw: https://www.juliusunscripted.com/pos...-ebook-reader/

[jTolinoDouble]

Just for anyone having this same issue, i.e. when converting epub to kepub via calibre, the
page-count on a kobo/tolino is doubled and the first actual page is somewhere in the middle -
I just found a solution for the issue (at least, for the book I had it with):

When I edit the epub-version with calibre (right click -> edit book), the text-documents had a space in their name, e.g. "Book Title_split_001.html".

The content.opf (under Miscellaneous) had them as

<item ... href="Text/Book Title_split_001.html" ... />

while the toc.ncx had each navPoint as

<content src="Text/Book%20Title_split_001.html"/>

The entry in content.opf is the incorrect one - an href is a URI reference, so a space has to be
encoded as %20. Calibre passes both spellings through to the kepub unchanged, so the conversion
itself is fine; the reader seems to treat the two spellings as two separate files, which would
explain the doubled count and the content starting halfway through.

To fix this, I:

1. Renamed all the text files and replaced the whitespace with _
2. Adjusted the entries in content.opf to Book_Title_split_001.html
3. Did the same for the entries in toc.ncx

Then I re-converted, and from then on it worked just fine.