Quote:
Originally Posted by pssquirrel
When you use KindleUnpack to explode an azw3, are the resulting files lossless? Have they been modified or converted in some way, or were they simply decompressed or unwrapped?
|
It's
not a lossless process; style names in stylesheets survive, but file names don't. Also some system files are re-created.
Quote:
Originally Posted by pssquirrel
what does "Fix ASIN for Kindle Fire" do?
|
AFAIK, it manipulates the metadata of a mobi/azw3 file; it adds ASIN numbers and changes the ebook type to EBOK.
Quote:
Originally Posted by pssquirrel
Am I guessing correctly that "Fix ASIN for Kindle Fire" edits hidden files or hidden data not accessible in an exploded azw3?
|
AFAIK, that's correct. This plugin modifies the binary
EXTH metadata of a mobi/azw3 file.
Quote:
Originally Posted by pssquirrel
Is there a way to "Fix ASIN" manually?
|
You could theoretically use a
Python script to manually change/add the ASIN number.
Quote:
Originally Posted by pssquirrel
As far as I can tell, KindleGen/KindlePreviewer is a one-way process where you feed data in and an azw3 comes out, yes? You can't use it to open up an azw3 for editing?
|
That's correct.
Quote:
Originally Posted by pssquirrel
If you want to edit, you have to go back to the source data, edit that, and then run it through KindleGen/KindlePreviewer to make a new azw3?
|
That's correct. BTW, KindleGen will generate a hybrid mobi file that contains the old and new formats and the source files by default. (You can generate an AZW3 file directly with Calibre.)