Page Mapping Using toc.ncx

[KevinH]

FWIW, Kindleunpack has had experimental code to do that and even generate an epub pagetable from it.

[Hitch]

Originally Posted by jhowell

EPUBs with real page numbers are rare so few tools exist that work with them.

APNX files produced directly by calibre or by using the APNX plugin do not include pages defined in the NCX pageList, they only create approximately positioned pages based on a specified (or estimated) page count for the book.

That's what I thought. Good to know I haven't completely missed the bus.

Kindlegen will process a pageList and save it in the MOBI file produced, but I do not know of any software that can split out this information to produce a separate APNX file as needed for Kindle devices.

The KFX Output plugin for calibre will make use of an NCX pageList to produce KFX files containing real page numbers that can be sideloaded to Kindle devices. (KFX format does not rely on APNX files.)

Good to know, although I don't think it solves the OP's issue, if he's attempting to do this for commercial reasons.

Hitch

[JSWolf]

Originally Posted by jhowell

EPUBs with real page numbers are rare so few tools exist that work with them.

This is wrong, oh so very wrong. Any ePub read with any software that uses ADE style page numbers has real page numbers.

[Hitch]

Originally Posted by JSWolf

This is wrong, oh so very wrong. Any ePub read with any software that uses ADE style page numbers has real page numbers.

Wofie:

No, they don't. Not to match the original print edition. RPNs are typically used in books in which the publisher wants study groups to be able to both find the same content on the same "page" with ease and facility. Using ADE page numbers--given that not all eReaders use ADE as their engine--doesn't achieve that.

Hitch

[JSWolf]

Originally Posted by Hitch

Wofie:

No, they don't. Not to match the original print edition. RPNs are typically used in books in which the publisher wants study groups to be able to both find the same content on the same "page" with ease and facility. Using ADE page numbers--given that not all eReaders use ADE as their engine--doesn't achieve that.

Hitch

if everyone is using ADE page numbers and the teacher says to go to page 15, everyone will be at page 15 no matter the font, font size, margins, or line height settings. ADE page numbers are real. It's the fault of the person reading the ePub that a program that uses ADE page numbers is not being used.

It would be like reading as kepub when you should be reading as ePub.

[jhowell]

Originally Posted by JSWolf

if everyone is using ADE page numbers and the teacher says to go to page 15, everyone will be at page 15 no matter the font, font size, margins, or line height settings. ADE page numbers are real. It's the fault of the person reading the ePub that a program that uses ADE page numbers is not being used.

I guess the best solution is to require all printed books to use ADE page numbers from now on!

[JSWolf]

Originally Posted by jhowell

I guess the best solution is to require all printed books to use ADE page numbers from now on!

It's silly to require eBooks need printed page numbers. They aren't relevant because different pBooks with different formats have different page numbers. ADE page numbers work because they are like pBooks, a different container with different page numbers.

[Hitch]

Originally Posted by JSWolf

It's silly to require eBooks need printed page numbers. They aren't relevant because different pBooks with different formats have different page numbers. ADE page numbers work because they are like pBooks, a different container with different page numbers.

Wolfie, my sweet, come ON.

Now, you know darned well that that will never happen--"everybody" won't have ADE. They'd be more likely to all have iOS on a phone, than having ADE. Your argument doesn't hold water, simply because the world fo devices is too diverse. And not everyone has a tablet or laptop that can run ADE. Then what?

Nope, dear, I'm sorry to say this, but we cannot use ADE as some world-wide page-numbering standard. We simply cannot.

Hitch

[JSWolf]

iOS & Android can run Bluefire Reader wich is based on some version RMSDK. Any Reader that supports Adobe DRM has RMSDK. That means nook, Kobo, Sony, and others.

What platform that people might use to read eBooks won't have some app/program that supports ADE page numbers?

[Turtle91]

Jon....not everyone WANTS to use an ADE based reader even if they could.... I'm sure there are many reasons for this...thus the selection of different platforms.

Regardless, you aren't going to get everyone to follow your preferences...even if you COULD make the perfect argument for their use...and everyone here agreed with your preferences not everyone reads MR so your message won't reach everyone.

Please accept the fact that ADE is not the end-all, be-all, of ereaders and move along. We really don't need to read another thread where you insist that ADN based RPN is the only valid solution. It is A solution that has some merit, but there are others with equal merit...including the solution that ebook page numbers are irrelevant... with links and ToC and search functions it's redundant, at best, to have a "page number".

Thanks!

[Hitch]

Originally Posted by JSWolf

iOS & Android can run Bluefire Reader wich is based on some version RMSDK. Any Reader that supports Adobe DRM has RMSDK. That means nook, Kobo, Sony, and others.

What platform that people might use to read eBooks won't have some app/program that supports ADE page numbers?

Jon:

Does it matter? What if they're using Readium? What if they're using some other software reader? You can't FORCE people to all go out and use reader X, especially if they already have their own.

Moreover, I find that the page numbers between iOS and ADE are NEVER close, much less the same.

I just think you're trying to square-peg/round-hole here. We'll all agree that IF the class is all using the SAME eReader, then page numbers don't matter, but in what world will that ever happen? Not here, that's for damned sure. C'mon, dude, you know you're just arguing to argue.

Hitch

[JSWolf]

If you are the teacher and you say that the students are to be using Bluefire, then Bluefire it is. That way when the teacher says to go to page 34, page 34 it is. Also, when citing, the teacher will know if the page number is correct. So yes, the teacher can dictate what reading software is used.

[Hitch]

Originally Posted by JSWolf

If you are the teacher and you say that the students are to be using Bluefire, then Bluefire it is. That way when the teacher says to go to page 34, page 34 it is. Also, when citing, the teacher will know if the page number is correct. So yes, the teacher can dictate what reading software is used.

Jon:

You obviously haven't been in a classroom in a long time. ;-)

Hitch

[Turtle91]

No he mustn't have been. They might be able to dictate what devices/apps get used in grade school or high school, but that is because they are supplied by the school. But, in those schools, no one cares about page numbers...it's hard enough to get them care about the class, or the assignment!

In college, the instructor doesn't have that authority...nor would the instructor care what the students use...or even IF they use an app...

So much for grasping at straws... lolz

[JSWolf]

Originally Posted by Turtle91

No he mustn't have been. They might be able to dictate what devices/apps get used in grade school or high school, but that is because they are supplied by the school. But, in those schools, no one cares about page numbers...it's hard enough to get them care about the class, or the assignment!

In college, the instructor doesn't have that authority...nor would the instructor care what the students use...or even IF they use an app...

So much for grasping at straws... lolz

Wrong, the teacher can dictate what's used in class. That includes college.