Hi,
The other use case is distributing free of charge kindlegen generated mobis without the source zip archive. Kindlegen can in fact generate these now with a simple command line option and their terms of use allow you to give them away for free to others without going through Amazon.
If someone had such a kindlegen generated mobi and they could decide they would like to convert it to epub for reading on another device. If they use calibre to do this now, they would lose the real page information.
Similarly, with KindleUnpack you can split out the source and create azw3s with page info in PAGE sections, and post them for others to convert.
The nice thing about the PAGE section is that it keeps the real page info right inside the mobi where it belongs, and not in some external APNX file.
Either way, I plan to make KindleUnpack keep the PAGE section when splitting while adding the capability to create an APNX file from it too. Perhaps a standalone APNX file generator if that turns out to be useful.
Take care,
KevinH
Quote:
Originally Posted by kovidgoyal
I'm somewhat unconvinced for the need for PAGE sections so far. It seems to me:
1) The only thing that uses it is Amazon's servers. And since you cannot send AZW3 by email anyway, generating AZW3s with PAGE sections appears to be useless, unless you intend to send you book to KDP, and KDP does not accept calibre generated AZW3 files anyway.
2) The other possible use case is converting kindlegen produced AZW3s to EPUB. However, since the only way to (typically) get hold of kindlegen produced AZW3s is generating them yourself, you should already have an epub with a page map, so I dont see why you would not want to use the source epub directly.
That said, the code is pretty trivial, so I might just add it anyway. But it is not a priority.
|