Pages are wrong

[chris080]

I testes Sigil and somehow it worked, but the page numbers are very strange. I've got 2 times every page number, which means I get these page numbers: 1,1,2,2,3,3 and not 1,2,3,4,5,6

And where [1,1] begins on this page is somewhere in the text a '1' and layering the book text. Same for [2,2] and [3,3]. This isn't normal ...

I have a Kobo N514

[DiapDealer]

Sigil doesn't have anything to do with page numbers.

[Binchen]

Thats an eReader issue. Readers with RMDSK are just dividing the compressed filesize by 1024 and considering that as a page. Depending on the amount of text a page can span multiple screens. As a result the end of a page and the start of a new page can be on the screen displayed as 5-6

The advantage is showing the same pagenumber independent from font and font sizes and devices. Provided it is exactly the same file.

[JSWolf]

Originally Posted by Binchen

Thats an eReader issue. Readers with RMDSK are just dividing the compressed filesize by 1024 and considering that as a page. Depending on the amount of text a page can span multiple screens. As a result the end of a page and the start of a new page can be on the screen displayed as 5-6

The advantage is showing the same pagenumber independent from font and font sizes and devices. Provided it is exactly the same file.

With Kobo, RMSDK does not display page numbers as 5-6 in the footer. If the page is 5-6, it will display 5 and the next page will display 6 or 7 depending where 6 ends.

The other thing that causes the appearance of skipping/stuck page numbers on a Kobo is reading KePub. I don't if anyone here knows how Access (which is used to display KePub) handles page numbers.

[davidfor]

Originally Posted by chris080

I testes Sigil and somehow it worked, but the page numbers are very strange. I've got 2 times every page number, which means I get these page numbers: 1,1,2,2,3,3 and not 1,2,3,4,5,6

And where [1,1] begins on this page is somewhere in the text a '1' and layering the book text. Same for [2,2] and [3,3]. This isn't normal ...

I have a Kobo N514

As the others have said, this is how the RMSDK does page counting. It is used by Kobo and other ereaders and apps. The advantage of this system is the page numbers do not change as you change the font size and other settings. The number in the margin shows where the page starts. On Kobo devices, there in option in the settings to turn it of.

On a Kobo device, if you want page numbers to match the screen, you can use kepubs. There are several way to get kepubs onto the device, including calibre and a standalone utility called kepubify. There is plenty of discussion of the pros and cons of kepubs in the Kobo forum.

[JSWolf]

Originally Posted by davidfor

On a Kobo device, if you want page numbers to match the screen, you can use kepubs. There are several way to get kepubs onto the device, including calibre and a standalone utility called kepubify. There is plenty of discussion of the pros and cons of kepubs in the Kobo forum.

Did 4.26.16704 fix KePub page numbers or are they still broken? We did have a conversation someplace on MR about the broken KePub page numbers. If he page numbers are still broken, then they will not be a 1-1 (1 screen = 1 page) match.

[davidfor]

Originally Posted by JSWolf

Did 4.26.16704 fix KePub page numbers or are they still broken? We did have a conversation someplace on MR about the broken KePub page numbers. If he page numbers are still broken, then they will not be a 1-1 (1 screen = 1 page) match.

Honestly, I don't pay enough attention. Checking the book I am reading, the page count was correct except for the last page of the chapter. That gets repeated.

[MicroDrie]

Originally Posted by JSWolf

If he page numbers are still broken, then they will not be a 1-1 (1 screen = 1 page) match.

With a lot of challenges and without flexibility you can go a long way. That's because when I have a printed book, each page is a fixed size. I can display a certain amount of text (and images) on it. When all available space is used up, the remaining text continues to the next page. More unused white space and/or larger text and/or font determines whether more text is scrolled to the next page. We call this a fixed page content. Simply put, the text fits exactly on a screen.

If we're going to display the same amount of text on a web page, increasing the font size and/or white space means we'll have to scroll more on this web page to see the full text. That's what we call flowable page content. Simply put, the text appears a little longer on a physical screen

By nature, EPUB is a flowable format, which we can convert with formatting codes into a fixed page content representation, but that comes at a price. Because if something doesn't fit on a physical screen, what do you do? Discarding is not an option, so it moves to the next screen with the same page number.

The charm of an EPUB is that it can be fully displayed on any screen, font and resolution size. You can give the reader the freedom to adjust all kinds of things. If you want a fixed page layout with horizontal scrolling per line, it is better to opt for a fixed-layout PDF solution.

And yes, the page numbering in a book is functional to find something quickly. In an EPUB, you can find something even faster with the search function and with or without anchors without page numbers. EPUB works more with chapters than pages. It takes some getting used to: no more 50 pages, but 2 more chapters without a page number in the layout that I want, to be read if you omit the page numbers.

If you insist on using page numbers, you'd better split the text manually and add page numbers in the HTML view. With the combination Ctrl-Enter, the text after the cursor position is broken and the rest moves to a new page. So a lot of work and challenges.

[davidfor]

Originally Posted by MicroDrie

With a lot of challenges and without flexibility you can go a long way. That's because when I have a printed book, each page is a fixed size. I can display a certain amount of text (and images) on it. When all available space is used up, the remaining text continues to the next page. More unused white space and/or larger text and/or font determines whether more text is scrolled to the next page. We call this a fixed page content. Simply put, the text fits exactly on a screen.

If we're going to display the same amount of text on a web page, increasing the font size and/or white space means we'll have to scroll more on this web page to see the full text. That's what we call flowable page content. Simply put, the text appears a little longer on a physical screen

By nature, EPUB is a flowable format, which we can convert with formatting codes into a fixed page content representation, but that comes at a price. Because if something doesn't fit on a physical screen, what do you do? Discarding is not an option, so it moves to the next screen with the same page number.

The charm of an EPUB is that it can be fully displayed on any screen, font and resolution size. You can give the reader the freedom to adjust all kinds of things. If you want a fixed page layout with horizontal scrolling per line, it is better to opt for a fixed-layout PDF solution.

And yes, the page numbering in a book is functional to find something quickly. In an EPUB, you can find something even faster with the search function and with or without anchors without page numbers. EPUB works more with chapters than pages. It takes some getting used to: no more 50 pages, but 2 more chapters without a page number in the layout that I want, to be read if you omit the page numbers.

If you insist on using page numbers, you'd better split the text manually and add page numbers in the HTML view. With the combination Ctrl-Enter, the text after the cursor position is broken and the rest moves to a new page. So a lot of work and challenges.

Sorry, I'm not sure what the point of that is. It is not anything that we don't know. If you do some searching, you will find that page numbering has been discussed frequently and, shall we say, vigorously here. And @JSWolf has been very involved in those discussion. But, basically, people like to see page numbers as they are used to them in paper books. They just have to understand what they mean.

What @JSWolf was asking about a is known problem on Kobo ereaders using their kepub format. This is supposed to use one page per screen. But, there is a bug where the number is not incremented properly as you turn the page. It sometimes happens in the middle of chapters and sometime for the last page in the chapter. All it really means is that if you counted how many times you need to tap to go through a book, it would be about 10% more than what the page count shows.