View Single Post
Old 12-04-2014, 04:53 AM   #3
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,827
Karma: 8700631
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by Doitsu View Post
You could theoretically use page number anchors in the book and a pagelist in the .ncx file or a pagemap file to define page numbers. (There are example files in this post.)
However, AFAIK, only large publishing houses can publish books with "real page numbers." I.e., if you plan to publish your book with KDP, you can save yourself the hassle.

BTW, KindleGen won't generate an .apnx file for you, but you can generate an .apnx file for testing purposes with the latest KindleUnpack version. However, IIRC, you'll also need to add ASINs with dualmetafix_mmap.py, before you generate the .apnx file with KindleUnpack.
Please, could you explain a bit more the procedure?
That is, if I have an epub with a pagemap file, and with that epub I build a .mobi with Kindlegen and after that I use the last version of KindleUnpack to unpack the generated .mobi, will I have an .apnx file?
And regarding ASIN, can it be any number? (I ask you this because the generated .mobi could be a public domain book whose ASIN doesn't exist).

Many thanks in advance.
Rubén
RbnJrg is offline   Reply With Quote