Quote:
Originally Posted by enuddleyarbl
I'm assuming that the publisher just ran some automated "stick a page id in here somewhere" program that looked at a print book and at the start of each dead-tree page, stuck a tag into the ebook.
|
They most likely placed the page break smack dab in the middle where it occurred in the print book.
Code:
There was an ele-
-------PAGE 2-------
phant in the zoo.
would then be converted to:
Code:
There was an ele<a page="page_2"></a>phant in the zoo.
This is a case where the page number code should've been adjusted afterwards.
Quote:
Originally Posted by enuddleyarbl
EDIT: From that "Page Navigation" link you provided, inline page markers are supposed to look something like:
|
Listen to it for
some advice, not all.
For all the latest "Real Page Numbers" (RPNs) stuff, see my post here:
where I link to many of the previous topics.
You'll also want to type this into your favorite search engine:
Code:
RPNs Tex2002ans site:mobileread.com
page numbers Tex2002ans site:mobileread.com
where me + Hitch + Doitsu have discussed this topic to death.
- - -
For a working sample of EPUB3 page numbers, see
Doitu's sample book.
And his fantastic Sigil plugin:
- - -
Quote:
Originally Posted by enuddleyarbl
Ninety-nine percent of the time, it'll be the old <a id="pag_330"></a> method, which that document specifically says bad things about. Occasionally, I'll see something like what's done in the current book I'm editing ("<span epub:type="pagebreak" id="page_330" title="330"></span>")
|
Yes.
The simple <a> was the EPUB2 method.
The <span> + epub:type="pagebreak" is the EPUB3 method.