View Single Post
Old 03-19-2019, 09:01 AM   #12
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,341
Karma: 203719142
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by mrprobert View Post
I understand the issue with named character entities, but I don't see this behavior with 0.9.10 set to preserve   and with my particular toolbar string.
You should be seeing see it. If you have   in your Preserve entities list and you start a brand new EPUB3 (or open an existing EPUB3) and enter   somewhere in Code View, you should immediately see the pink error window in preview. That should be the same with just about any version of sigil that supports creating both EPUB2 and EPUB3.

EDIT: Nevermind I think I see what you're saying now. As far as your ini file goes ... there's no Preserve Entities settings saved to it yet, anyway. Just stop using Sigil 0.9.11/12. It's not healthy. Generate completely new ini files with Sigil 0.9.10 and wait for the next release. Continuing to use the problem versions of Sigil just isn't worth the trouble.

Last edited by DiapDealer; 03-19-2019 at 09:13 AM.
DiapDealer is offline   Reply With Quote