A minor nit that gets moderately annoying at times.
When I open an epub that has a close to flat file structure which both Flightcrew and epubcheck are happy with reporting no errors, Sigil happily moves the stylesheets to a Styles directory, images to an Images directory, etc. Rather nice, standards compliant, warm fuzzy inducing(?) behaviour. However, Sigil then popups a warning the epub has HTML files that are not well formed, etc... Do you want Sigil to automatically fix the files with possible data loss warning, Yes/No.
I tend to say no since I have had Sigil do some rather nasty items in past when automatically fixing a file—leaving half the HTML files in an ebook empty comes to mind though it was quite a few versions back when I last tried automatic fixing.
Looking at the source of the errors, it appears that Sigil—unfortunately—does not modify the paths in the HTML files to match the file location changes unless you say yes to automatic modification.
In a sample epub file with an OPS directory and an OPS/images subdirectory:
Code:
Orignal link to stylesheet:
<link rel="stylesheet" type="text/css" href="style01.css"/>
Orginal link to image:
<p class="pc2"><img src="images/cover.jpg" style="height:100%;max-width:100%" alt="cover.jpg"/></p>
After opening with Sigil, the links remains unchanged and need to be manually edited to:
<link rel="stylesheet" type="text/css" href="../Styles/style.css"/>
<p class="pc2"><img src="../Images/cover.jpg" style="height:100%;max-width:100%" alt="cover.jpg"/></p>
Is there an option that I have missed to have this done automatically without the popup when file locations are the only changes being made—Sigil is already munging the file structure so why not automagically change the paths when doing so? Preferably with a notification about what's happening.