View Single Post
Old 10-30-2013, 02:49 PM   #3
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,648
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
The short answer is upgrade to v0.7.4.

The long answer is (and feel free to bypass it):

If your code uses & nbsp ; (or any named entities other than the 5 xml-approved entities), then it needs a Document Type Definition declaring it as XHTML or it's technically invalid.

v0.7.3 will also automatically convert any unicode non-breaking space characters to & nbsp ; (because of an unavoidable Qt issue) which can also make the document invalid if there's no existing DTD (newer versions of calibre are creating epubs that--while valid--are just going to give Sigil v0.7.3 fits in this regard).

v0.7.4 converts those unicode non-breaking characters to the numeric entity & #160 ; so it won't break any otherwise well-formed documents.

So it's upgrade to 0.7.4 or stay with 0.7.3 and allow it to add the correct DOCTYPE by enabling the Clean Source setting upon "Opening." You can turn it off off again once you've opened and saved that ePub.

Last edited by DiapDealer; 10-30-2013 at 02:53 PM.
DiapDealer is offline   Reply With Quote