View Single Post
Old 05-12-2015, 01:51 PM   #52
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,620
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by darryl View Post
In this case, and it is really clutching at straws, could the "r" in the "kpr" input format in the second problem book signify "rich text format" Could these be some sort of intermediate file produced by KDP from Word or RTF before being input to Kindlegen? Perhaps even the mysterious Kindletool?
Makes as much sense as anything else to me.

Quote:
Originally Posted by darryl View Post
It may be that we will never know the answer. If the problem has now been fixed in KDP we will not be able to reproduce it.
In all fairness ... there's technically not anything to "fix" in KDP (WRT this particular issue, anyway). Whatever processing is going on, it's producing a valid Kindlebook with a working internal NCX ToC--functional on all Kindle devices/apps. Problems only arose because KindleUnpack and calibre didn't (then) have a way of unbinary-ing them while retaining the functional ncx.

Last edited by DiapDealer; 05-12-2015 at 01:54 PM.
DiapDealer is offline   Reply With Quote