View Single Post
Old 07-19-2014, 02:56 PM   #37
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,690
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by KevinH View Post
Along, those same lines, I would like to prevent replacement of html entities into unicode in code view if they were originally present as entities, in an attempt to keep things as the designer intended or as close as.

Thanks,

KevinH
Hey Kevin,

If you do look into preventing entity replacement, take a peek at this thread that documents the steps to reproduce 0.7.4 eating markup (regarding the   entity). Post #13 has the steps to duplicate.

I've just not been able to get my head around the codebase (C++ and Qt double-whammy). The problem originated in the changes from 0.7.3 to 0.7.4--where it was decided that   would be replaced with   to fix the problem of 0.7.3 barking about missing DOCTYPES (because Sigil would replace the unicode non-breaking space character with   in documents it was opening/importing when Tidy was turned off).

That bug is one of the main reasons I've held off on using 0.7.4. It's easy to make sure my epubs have a doctype before editing ... not so easy figuring out whether markup got silently eaten.

Maybe your work will make it go away.
DiapDealer is offline   Reply With Quote