Quote:
Originally Posted by Perkin
When fixing editing epubs, one of the most often uses of Sigil for me (apart from quick spelling mistake edits) is having the handy ability to split and merge, keeping track and updating all the file/link references without Sigil would be a nightmare.
When building my own epubs (personal use), I have the html source file and any images/css/fonts
Once I import a html file, and the resources linked in it, I usually run the 'Split at markers', then 'Generate ToC', Check the metadata, fix semantics, check the validity, then save the epub. Job done (usually).
If you do the same import in calibre, a lot of styling etc is flattened and you end up with loads of 'calibre###' styles - not as nice as the given style names if you then need to edit the epub at any point.
So even if in future Sigil is embedded in calibre I'd still want the existing Sigil (or it's abilities) so any simple html-epub conversions don't get calibre'd.
|
Very well said. I too don't want my styles converted. I want them with the names I've put in the CSS. I want Sigil in Calibre to work like stand-alone Sigil where when I put something in and it's correct, it stays how I've added it.