Quote:
Originally Posted by JimLL
As for trivial coding, I've coded saves and it IS trivial unless you want to tie it in with all sorts of other stuff. I suggested auto saves. That would be trivial. You put the HTML filename in a variable (that's probably already done). You put on a timer. You save file by name. Trivial.
|
"The" HTML filename? When I make epubs with Sigil, every chapter and each of the front sections is its own HTML file. There's also the toc.ncx and contents.opf files, which I sometimes wind up tweaking, and of course any .css files I've included. Does the autosave make a backup of each separate file?
As already mentioned, it can't autosave the whole .epub unless it turns off the error-check feature. I'd rather have something that warned me "this can't save because it's not functional" than something that auto-saves. I can remember to hit ctrl-S every minute or two (and if I get an error message, be forced to go fix it); I don't want to think I've got a readable ebook when I don't.