Quote:
Originally Posted by DiapDealer
The question is: why would you do something like that? Anyone knowledgeable enough to risk manually editing the opf should already know that they also need to delete the image-file itself for the removal to be complete. Those NOT knowledgeable enough (or those who are just plain lazy like me), would use Sigil's integral delete function which would take care of both details properly.
Sorry, but protecting a user from every single way they could possibly manage to break their own epub if they try hard enough is not a rabbit-hole I plan to start down. Neither is protecting a user from all the ways an externally created epub could already BE broken before Sigil ever touches it.
Perhaps that will all change if we ever get to the point where sigil doesn't need to enforce its own internal structure on all epubs. but until that time ... it is what it is.
|
Y'know, we get crap ePUBs like this, (web archives or the like) or I should say, inquiries about them, all the time, and IMHO, the probable
best way to handle that is to follow Thasaidon's suggestion.
Run it through Calibre, manifest the unmanifested items, and then you can edit in Sigil, if you wish. Gets you everything you need, and it's a
de minimis additional effort.
Given Sigil's
intent, and what's trying to be done here, I don't see Kevin and Diap changing this anytime soon. Diap is right--protecting every single user from every single possible way that they can screw s**t up is the road to hell
and bloat.
Hitch