Sigil V0.7.3 released - Page 2

user_none · 08-07-2013, 07:37 PM

Quote:

Originally Posted by Moonraker

nbsp; errors and image errors (I think the image path was wrong apparently).

The nbsp error is because your file is invalid. That prevents the file from being automatically cleaned (and many issues corrected) which is why you're seeing the other errors.

theducks · 08-07-2013, 08:59 PM

UN
I am seeing a lot of 'This file is malformed...' on SOME older calibre conversions (not all).
Unfortunately, the error message is kind of terse, not saying what-were the issue is.
I did not see this frequency of this error with prior versions. Is it possible to have a log (view log button)?

Moonraker · 08-07-2013, 09:31 PM

I assumed it was Sigil because it happened on three different files one after the other. All three opened with errors according to Sigil. I could not correct two of the errors because I could not find them. I spent considerable time looking but had to give up. I have never known it before. When I went back to the previous 7.2 version all was well.

meme · 08-08-2013, 11:34 AM

Quote:

Originally Posted by theducks

UN
I am seeing a lot of 'This file is malformed...' on SOME older calibre conversions (not all).
Unfortunately, the error message is kind of terse, not saying what-were the issue is.
I did not see this frequency of this error with prior versions. Is it possible to have a log (view log button)?

Quote:

Originally Posted by Moonraker

I assumed it was Sigil because it happened on three different files one after the other. All three opened with errors according to Sigil. I could not correct two of the errors because I could not find them. I spent considerable time looking but had to give up. I have never known it before. When I went back to the previous 7.2 version all was well.

Can you PM a link to the epub that is causing you issues?

gbm · 08-08-2013, 12:06 PM

Quote:

Originally Posted by meme

Can you PM a link to the epub that is causing you issues?

Bedlam Boyz by Ellen Guon in the Baen Free Library.

screenshots of the errors

bernie

System
Ubuntu 12.04 32 bit on a Intel® Core™2 CPU 6600 @ 2.40GHz × 2 with Intel® 965G x86/MMX/SSE2 graphics

meme · 08-08-2013, 03:33 PM

Quote:

Originally Posted by gbm

Bedlam Boyz by Ellen Guon in the Baen Free Library.

That book is missing the DOCTYPE in every chapter:

Code:

<?xml version='1.0' encoding='utf-8'?>

should be

Code:

<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

EDIT:
And to expand on that - if you set your preferences to NOT clean on open, then you will get the error messages. The book will still open in Sigil, allowing you to see your files are missing the DOCTYPE. And if you have Preview on, then you will see it is identifying a line with an nbsp entity as causing the error.

If you set your preferences to clean on open, then the DOCTYPE will be added for you and the files will display ok.

The issue is, as I think was mentioned previously, that your file contains some nbsp characters (353 of them I believe) which in 0.7.2 were probably converted to normal spaces, but in 0.7.3 those nbsp characters are now correctly being converted to the nbsp entity   But since the files are missing the DOCTYPE header, Sigil does not know how to display that entity.

You can let Sigil clean the file for you. Or if you want to make sure nothing else is touched, you can open it without cleaning and then use Find&Replace to add the DOCTYPE line to every file.

PeterT · 08-08-2013, 06:02 PM

Wouldn't it make some sense to have the error message that is displayed give some guidance as to what the issue is....

gbm · 08-08-2013, 07:11 PM

Quote:

Originally Posted by meme

That book is missing the DOCTYPE in every chapter:

Code:

<?xml version='1.0' encoding='utf-8'?>

should be

Code:

<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

EDIT:
And to expand on that - if you set your preferences to NOT clean on open, then you will get the error messages. The book will still open in Sigil, allowing you to see your files are missing the DOCTYPE. And if you have Preview on, then you will see it is identifying a line with an nbsp entity as causing the error.

If you set your preferences to clean on open, then the DOCTYPE will be added for you and the files will display ok.

The issue is, as I think was mentioned previously, that your file contains some nbsp characters (353 of them I believe) which in 0.7.2 were probably converted to normal spaces, but in 0.7.3 those nbsp characters are now correctly being converted to the nbsp entity   But since the files are missing the DOCTYPE header, Sigil does not know how to display that entity.

You can let Sigil clean the file for you. Or if you want to make sure nothing else is touched, you can open it without cleaning and then use Find&Replace to add the DOCTYPE line to every file.

Thanks that is what I thought it was, good to have a second and expert opinion.
It does also this when converting the html or lit to epub with calibre.

bernie

forster01 · 08-09-2013, 05:38 PM

Dear friends, im not sure if this is the thread where i should post this question:
I liked a example of the Sigil site, of Alice's in the wonderland. can anz one share a stylesheet (css) of that exact epub please? Or entire book, as i understand it is already at project gutenberg.

PeterT · 08-09-2013, 05:55 PM

I think the version open there is the free one from http://www.feedbooks.com/book/22/ali...-in-wonderland

Bob Houston · 08-09-2013, 08:03 PM

Windows 8 - 64 bit.
I've been following this thread with great interest because I was hoping that the Nbsp problem was solved. I'm not sure that it is.

I followed the advise to "Clean on open", with both print tidy and then also with HTML tidy. No success.

I built a short epub that consisted of:
titlepage.xhtml
NbspTestFrontPage_split_000.html
NbspTestFrontPage_split_001.html - This split contained all of the blank spaces to be fixed.

The epub opens fine in v0.7.2.

What I noticed when the epub was opened in v0.7.3, was that the Doctype entry was inserted into titlepage.xhtml and also into NbspTestFrontPage_split_000.html.

But, in NbspTestFrontPage_split_001.html, the spaces were replaced with &nbsp and then it looks like the process had an error and didn't insert the Doctype entry and then issued the error messages as noted previously in this thread.

If the process was reversed and the Doctype entry was inserted first and then the spaces changed to &nbsp, would it make a difference?

Bob

meme · 08-10-2013, 04:29 AM

Quote:

Originally Posted by Bob Houston

But, in NbspTestFrontPage_split_001.html, the spaces were replaced with &nbsp and then it looks like the process had an error and didn't insert the Doctype entry and then issued the error messages as noted previously in this thread.

If the process was reversed and the Doctype entry was inserted first and then the spaces changed to &nbsp, would it make a difference?

Post your short epub. Do you see an error every time?

If I recall correctly, the nbsp character is replaced with ann entity as soon as the file is opened, otherwise it would be lost by later routines.

Bob Houston · 08-11-2013, 06:16 PM

I have attached the short epub for review. The epub validated with v0.7.2.

I tested it multiple times with v0.7.3 to make sure that I wasn't wasting anyone's time on this. It received the not well formed error on each opening, whether from the file - open in a running version of Sigil or from an "open with" and picking Sigil. I also used clean on open with both pretty print tidy and HTML tidy without success.

DiapDealer · 08-11-2013, 07:34 PM

So far as I understand, the DOCTYPE is not a requirement of the ePub spec (but it certainly needs to be correct if it IS present). So since Bob's attached, sample ePub is entirely compliant before 0.7.3 touches it, shouldn't the question be; "Why is Sigil inserting entities (by converting nbsp characters) into a document when doing so will make said document become 'not well formed?'"

I understand the reasoning behind wanting to preserve the intent of the non-breaking space character (which 0.7.2 did not do at all), but the fix shouldn't really come at the cost of making otherwise valid epubs, invalid. Should it?

I don't know. This is a bit of weird one. I always have the DOCTYPE in my files, myself, so this issue doesn't really affect me, but still... it seems like it's a bit of a catch-22.

phossler · 08-12-2013, 08:41 AM

Quote:

Originally Posted by user_none

... somewhat pleased ...

That's OK .. I'm very pleased. So far it's worked very well for me

Paul

08-09-2013, 08:03 PM	#26
Bob Houston Junior Member Posts: 8 Karma: 2062 Join Date: Aug 2011 Location: Queens, NYC Device: Kindle	Windows 8 - 64 bit. I've been following this thread with great interest because I was hoping that the Nbsp problem was solved. I'm not sure that it is. I followed the advise to "Clean on open", with both print tidy and then also with HTML tidy. No success. I built a short epub that consisted of: titlepage.xhtml NbspTestFrontPage_split_000.html NbspTestFrontPage_split_001.html - This split contained all of the blank spaces to be fixed. The epub opens fine in v0.7.2. What I noticed when the epub was opened in v0.7.3, was that the Doctype entry was inserted into titlepage.xhtml and also into NbspTestFrontPage_split_000.html. But, in NbspTestFrontPage_split_001.html, the spaces were replaced with &nbsp and then it looks like the process had an error and didn't insert the Doctype entry and then issued the error messages as noted previously in this thread. If the process was reversed and the Doctype entry was inserted first and then the spaces changed to &nbsp, would it make a difference? Bob Last edited by Bob Houston; 08-09-2013 at 09:28 PM. Reason: Edited for clarity.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Sigil 0.7.2 Released	user_none	Sigil	40	06-24-2013 11:35 PM
Sigil 0.7.1 Released	user_none	Sigil	64	03-26-2013 10:02 PM
Sigil 0.6.0 Released	user_none	Sigil	93	11-24-2012 06:50 PM
Sigil 0.5.3 Released	user_none	Sigil	85	05-13-2012 05:29 AM
Sigil 0.4.2 Released	user_none	Sigil	41	10-26-2011 06:03 AM

08-07-2013, 08:59 PM	#17
theducks Well trained by Cats Posts: 30,909 Karma: 60358908 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	UN I am seeing a lot of 'This file is malformed...' on SOME older calibre conversions (not all). Unfortunately, the error message is kind of terse, not saying what-were the issue is. I did not see this frequency of this error with prior versions. Is it possible to have a log (view log button)?

08-07-2013, 09:31 PM	#18
Moonraker Addict Posts: 314 Karma: 1002965 Join Date: Mar 2006 Location: UK Device: ILiad. Gen 3, PocketBook 360, Kobo Aura HD, Kindle Oasis 2	I assumed it was Sigil because it happened on three different files one after the other. All three opened with errors according to Sigil. I could not correct two of the errors because I could not find them. I spent considerable time looking but had to give up. I have never known it before. When I went back to the previous 7.2 version all was well.

08-08-2013, 06:02 PM	#22
PeterT Grand Sorcerer Posts: 13,306 Karma: 78876004 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	Wouldn't it make some sense to have the error message that is displayed give some guidance as to what the issue is....

08-09-2013, 05:38 PM	#24
forster01 Groupie Posts: 197 Karma: 82624 Join Date: May 2013 Device: Kobo Forma, Kobo Aura One, Kobo Aura HD, Kindle, Amazon Fire HD	Dear friends, im not sure if this is the thread where i should post this question: I liked a example of the Sigil site, of Alice's in the wonderland. can anz one share a stylesheet (css) of that exact epub please? Or entire book, as i understand it is already at project gutenberg.

08-09-2013, 05:55 PM	#25
PeterT Grand Sorcerer Posts: 13,306 Karma: 78876004 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	I think the version open there is the free one from http://www.feedbooks.com/book/22/ali...-in-wonderland

08-11-2013, 07:34 PM	#29
DiapDealer Grand Sorcerer Posts: 28,358 Karma: 203720150 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	So far as I understand, the DOCTYPE is not a requirement of the ePub spec (but it certainly needs to be correct if it IS present). So since Bob's attached, sample ePub is entirely compliant before 0.7.3 touches it, shouldn't the question be; "Why is Sigil inserting entities (by converting nbsp characters) into a document when doing so will make said document become 'not well formed?'" I understand the reasoning behind wanting to preserve the intent of the non-breaking space character (which 0.7.2 did not do at all), but the fix shouldn't really come at the cost of making otherwise valid epubs, invalid. Should it? I don't know. This is a bit of weird one. I always have the DOCTYPE in my files, myself, so this issue doesn't really affect me, but still... it seems like it's a bit of a catch-22.

Advert

Advert