View Single Post
Old 03-22-2019, 04:59 AM   #16
AlanHK
Guru
AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.
 
AlanHK's Avatar
 
Posts: 681
Karma: 929286
Join Date: Apr 2014
Device: PW-3, iPad, Android phone
Quote:
Originally Posted by DiapDealer View Post
The question is: why would you do something like that?
To make a test file.

Quote:
Originally Posted by DiapDealer View Post
Sorry, but protecting a user from every single way they could possibly manage to break their own epub
No one is asking you to stop people shooting themselves in the foot.

The issue is about how Sigil deals with epub files that have such problems already.

If the manifest does not match what is actually in the archive, then I think most people would like to know that, rather than having files silently deleted.
It could just give a warning that the named files will be deleted on saving. Or even give an option to add them to the manifest as if they had been imported normally.
AlanHK is offline   Reply With Quote