View Single Post
Old 12-18-2012, 02:08 PM   #9
Agama
Guru
Agama ought to be getting tired of karma fortunes by now.Agama ought to be getting tired of karma fortunes by now.Agama ought to be getting tired of karma fortunes by now.Agama ought to be getting tired of karma fortunes by now.Agama ought to be getting tired of karma fortunes by now.Agama ought to be getting tired of karma fortunes by now.Agama ought to be getting tired of karma fortunes by now.Agama ought to be getting tired of karma fortunes by now.Agama ought to be getting tired of karma fortunes by now.Agama ought to be getting tired of karma fortunes by now.Agama ought to be getting tired of karma fortunes by now.
 
Agama's Avatar
 
Posts: 776
Karma: 2751519
Join Date: Jul 2010
Location: UK
Device: PW2, Nexus7
I've started looking at how to do this via a plugin and noticed that something odd is going on. After deleting all the azw3 contents and copying in the ePub contents, the rebuild works fine. However, re-exploding shows that the rebuilder has done rather more than simply re-assemble the file:

1) The individual html files have been renamed and moved to a text folder.
2) The stylesheet.css has been split into 3 css files and moved to a styles folder.
3) The images have been renamed and moved to an images folder.
4) The metadata.opf has been re-written to reflect the above changes.

This must all be happening inside the Tweak Book rebuild and probably explains why this rebuild takes so much longer for azw3 than for ePub, (which only has to rezip the exploded contents.) Whilst this doesn't invalidate the idea of repacking an ePub into azw3, I need to have a look at the code in Tweek Book to see exactly what's going.
Agama is offline   Reply With Quote