MobileRead Forums - View Single Post

pete6055 · 04-12-2015, 05:41 PM

Hi Kevin,

This afternoon I did extensive testing on Vista-64 of release 8.6, creating &/or editing a dozen epubs without any problem at all -- No crashes, TOC creation problem, "file jumping", lost files on close or anything else. In some of my tests I intentionally created html errors and Sigil handled them as I expected.

For those using Comodo Firewall, I noticed that the new exe did not automatically inherit the old HIPS settings. I had to manually reset Sigil as a trusted application before it would open. Anyone needing help doing this can contact me here and I'll post instructions at that time.

Nice release; it has my highest seal of approval.

Thanks,

Pete

P.S. In 8.7 can you give us an option to set the W3C validator to CSS 3.0? Right now it's hard-coded to 2.1, which doesn't support font-family, font-style or font-weight. I'd probaby make the standard to be used configurable in preferences, or remove W3C validation altogether, since this can be done by plugin (though some users will not want to install Python and update it as needed). Prior to version 7.0 CSS 3.0 was the default. Thanks again for all your hard work.

04-12-2015, 05:41 PM	#1
pete6055 Connoisseur Posts: 74 Karma: 10 Join Date: Nov 2012 Device: none	8.6 is Rock Solid Hi Kevin, This afternoon I did extensive testing on Vista-64 of release 8.6, creating &/or editing a dozen epubs without any problem at all -- No crashes, TOC creation problem, "file jumping", lost files on close or anything else. In some of my tests I intentionally created html errors and Sigil handled them as I expected. For those using Comodo Firewall, I noticed that the new exe did not automatically inherit the old HIPS settings. I had to manually reset Sigil as a trusted application before it would open. Anyone needing help doing this can contact me here and I'll post instructions at that time. Nice release; it has my highest seal of approval. Thanks, Pete P.S. In 8.7 can you give us an option to set the W3C validator to CSS 3.0? Right now it's hard-coded to 2.1, which doesn't support font-family, font-style or font-weight. I'd probaby make the standard to be used configurable in preferences, or remove W3C validation altogether, since this can be done by plugin (though some users will not want to install Python and update it as needed). Prior to version 7.0 CSS 3.0 was the default. Thanks again for all your hard work. Last edited by pete6055; 04-12-2015 at 06:15 PM.