![]() |
#1 |
Fanatic
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 541
Karma: 1152752
Join Date: Aug 2010
Location: Evansville, IN, USA
Device: Samsung Galaxy Tab 4 Nook & Samsung Galaxy Tab S 10.5
|
Strange new error with 0.7.3?
Since upgrading to Sigil 0.7.3, I've begun occasionally receiving a strange error that I've never seen before. Sigil won't allow me to view several of my html files in book view. The error says:
"The operation you requested cannot be performed because *.html is not a well-formed XML document." "An error was found at or above line X: entity 'nbsp' not found." I've looked at the line of code and can't see anything whatsoever wrong. Has anyone else run into this? - Byron |
![]() |
![]() |
![]() |
#2 | |
Well trained by Cats
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 30,908
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
Quote:
![]() Sometimes the error STARTED way before the line mentioned (That being the first place it could determine that things went SOUTH) |
|
![]() |
![]() |
Advert | |
|
![]() |
#3 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 28,358
Karma: 203720150
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. |
![]() |
![]() |
![]() |
#4 |
Fanatic
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 541
Karma: 1152752
Join Date: Aug 2010
Location: Evansville, IN, USA
Device: Samsung Galaxy Tab 4 Nook & Samsung Galaxy Tab S 10.5
|
That's exactly what it was alright. I hadn't even noticed that those particular files hadn't been properly defined. The two files that we giving the error had no doctype definition whatsoever. I just hadn't noticed it. Once I copy & pasted the lines in, everything cleared right up. Usually Baen is better about putting their epubs together but occasionally mistakes slip through.
Thanks for the help. - Byron |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Strange error | onlystarlight | Devices | 7 | 07-07-2011 12:35 AM |
Strange error managing tags | paulfiera | Calibre | 2 | 02-16-2011 04:42 AM |
Strange Error Message - Anybody Else | Hughdal | Sony Reader | 4 | 05-27-2009 06:04 PM |
Strange Conversion error. | thepete | Calibre | 3 | 03-23-2009 11:39 AM |