user_none
I installed v 0.8.3 yesterday and started using it to correct an 800 page epub. It appeared to work perfectly and then . . . I was working for about a day in proofreading and saving when suddenly I couldn't save. Sigil notified me that it was set to save only when there were no errors so an error must have crept in even though I could change from code view to book view without problems. I accepted the automatic clean changes and saved it. Then I started thinking about earlier versions that used to provide pages and pages of < and > unicode additions where they were not needed, in addition to numerous unwanted coding errors of various types. When Sigil announced that it was automatic, I mean there was no way to stop the correcting until finished. No way to see what Sigil was doing until finished and then I check in detail the 800 p epub.
I checked the epub for < > unicode and found only one unwanted error, and I don't know when it was produced. But perhaps I should start over on the proofing using a clean copy on my reader that hasn't been corrected by Sigil 0.8.3.? The same problem, though, could arise with further checking because eventually I need to save a copy that passes validation. Or should I try to turn off the automatic checking forever and see if the fully proofed copy will validate? Do you have any recommendations about this?
It would be ideal to be able to see what Sigil is doing before producing more 'corrections' automatically, that is, an option for a auto/manual corrections in place of the complete auto correct before saving.
Last edited by bobcdy; 02-02-2015 at 01:49 PM.
|