View Single Post
Old 06-26-2017, 12:24 PM   #15
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,478
Karma: 204127028
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by SigilBear View Post
Just create a new ePub, open it and the original damaged ePub with eCan Crusher, then copy the META-INF folder from the new ePub over the the META-INF in the damaged ePub. Then make sure your images are still there.
The problem I have with this is that it's completely unnecessary if you're using and saving with Sigil. It's also completely unrelated to using Sigil. If your container.xml file is disappearing, it's something other than Sigil that's causing the problem. You're free to take up your "how to manually fix some mysteriously broken epubs" in the epub format forum if you like, but Sigil doesn't need any more threads about missing container.xml files.

Last edited by DiapDealer; 06-26-2017 at 12:26 PM.
DiapDealer is online now   Reply With Quote