Thread: Logical TOC problem in Kindle on iOS
View Single Post
Old 10-14-2019, 03:09 PM   #20
jhowell
Grand Sorcerer
jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.
 
jhowell's Avatar
 
Posts: 7,094
Karma: 92190113
Join Date: Nov 2011
Location: Charlottesville, VA
Device: Kindles
Quote:
Originally Posted by ash-f View Post
Wow, transferring mobi worked! now iOS shows toc correctly.
So I should never use azk?
I've heard that file format for iOS should be azk before.
When a Master MOBI is transferred to the iOS app the older MOBI-7 part of the file is used and the KF8 portion is ignored. To see KF8 formatting you need to sideload an AZK file.

I played around with AZK a while ago and I found the azkcreator included in the Kindle Previewer to be quite buggy. I did testing on the files it produces and found some serious problems:
  • AZK creation loses styles declared in the HTML head element. They are replaced with a link to a missing stylesheet.
  • AZK does not contain page numbers.
  • AZK has a link to the content TOC in the guide instead of including the original NCX TOC.
jhowell is offline   Reply With Quote