View Single Post
Old 06-29-2014, 11:09 AM   #843
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,887
Karma: 6120478
Join Date: Nov 2009
Device: many
Hi,
As I said, it is not going to happen. The extra metadata will not hurt anything and shows what was in the original azw3 which helps when diagnosing new Kindlegen features.

This tool is not really an azw3 to epub converter because it is not guaranteed to even generate an epub that meets spec. It is meant to unpack the AZW3/Mobi file so that modifications can be made, html/css code differences can be detected, etc, and then passed back thru kindlegen to create a new azw3/mobi. Any epub-like structure generated by KindleUnpack should be tested, and edited in Sigil (or any text editor) and fixed. During that process feel free to hack any unwanted metadata out.

KevinH


Quote:
Originally Posted by JSWolf View Post
I don't care about that metadata in the AZW3 itself. I'm just looking for things to be automated so when the code shift to ePub is done, that data is dumped as ePub has no need of it at all. All it is for the ePub is code bloat.
KevinH is offline   Reply With Quote