Sigil-1.4.0 Released

[KevinH]

The errors on opening is most likely because of a missing doctype. The doctype is important and should not be omitted when serving the epub pages as xml/xhtml.

BTW, I could not find any earlier bug report from you other than this one, which you said was because your ncx was not updated.

https://www.mobileread.com/forums/sh...0&postcount=21

Which earlier report are you referring to?

[DiapDealer]

Originally Posted by Moonraker

I always say no and open the file with Sigil and check myself and always there are no errors according to both Flight Crew's validation and Sigil's own validation.

Please try to remember that Sigil doesn't have its own validation. The Well Formedness check basically only checks to see if the markup is machine parseable (all opening tags have matching closing tags and there aren't any nesting mismatches). It should not be used to check if the file(s) in question conform to any kind of epub or xhtml specifications.

[KevinH]

Originally Posted by Moonraker

Also I noticed in this newer version I get a load of extraneous amp; in the <dc:description></dc> description field and when I convert it in Calibre these show up — see attached pic — it just plain looks wrong. This does not happen in Version 1.2.

https://imgur.com/a/fBS9gh6

I was able to duplicate this bug and track it down and fix it. We were double xmlencoding some opf metadata fields.

I have just pushed a fix to this to master. If we can recreate and track down the other issue you were having quickly, we may be able to release a Sigil 1.4.1 with these fixes before the holidays.

Thank you for your bug report.

KevinH

[HaPeSchu]

Hi,

thanks for the new version. But i have an issue with search & replace on macOS Mojave.

When i select a text and press cmd-F the text was copied and masked for regex into the find field in former versions.

In 1.4 the s&r dialog is closed in addition. cmd-f brings it back with the masked text in the find field.

HaPeSchu

[Moonraker]

Please reinstall Sigil 1.4.0 just temporarily, and then provide us with an exact sequence of steps to recreate the issue. The more detail the better. Without this nothing will ever be fixed.

Thank you. I have installed Sigil 1.4 again for testing.

Your mention of the DOCTYPE made me realise how silly I have been. I assumed that Sigil would create the same doctype details for the new page as the rest of the book... Duh. Now I have this info instilled into my brain it works perfectly. (I now copy and paste the doctype from one of the original pages to the new page) and problem solved.

Regarding the extraneous amp;(s) This is still occurring. I have checked with Calibre's opf file and there are no amp;(s) on it. They only seem to appear once the file is opened and saved in Sigil. I cannot send a copy of this opf file for copyright reasons. In the meantime, because these amp;(s) only appear after saving with Sigil, I can remove them in Calibre when converting.

I have changed my preferences in Sigil 1.4 so that "mend not well formed" is not selected for "open and save" and "Validation" is set at CSS 2.1. So that stopped the pop-up window appearing and I will correct any errors myself using Flight Crew and/or Sigil's Well-Formed ePub check.

[KevinH]

If you add a blank html using the menus (right click on Text in BookBrowser", then a proper Doctype should be automatically added.

If you run Mend, a proper Doctype should be added.

If you enable Mend on Open then if Doctype is missing in some files, it will fail the well-formed check and allow you to auto fix them.

Only if you use AddExisting a file without a Doctype, or copy and paste in source that is missing a Doctype would you then need to add it manually or simply just run Mend.

[KevinH]

Yes, this has already been reported will be fixed in the next release.

Originally Posted by HaPeSchu

Hi,

thanks for the new version. But i have an issue with search & replace on macOS Mojave.

When i select a text and press cmd-F the text was copied and masked for regex into the find field in former versions.

In 1.4 the s&r dialog is closed in addition. cmd-f brings it back with the masked text in the find field.

HaPeSchu

[KevinH]

Originally Posted by Moonraker

Regarding the extraneous amp;(s) This is still occurring. I have checked with Calibre's opf file and there are no amp;(s) on it.

Yes, I just found and fixed that bug last night. The fix will be in the next release. Thank you for reporting the bug.

[Tex2002ans]

Originally Posted by KevinH

Yes, I just found and fixed that bug last night. The fix will be in the next release. Thank you for reporting the bug.

Originally Posted by Moonraker

I cannot send a copy of this opf file for copyright reasons.

What?

There is absolutely no copyright in such a file. Just as there is no copyright in a Table of Contents.

[exaltedwombat]

Originally Posted by DiapDealer

Since I don't think it's explicitly mentioned anywhere, I'd like to draw attention to the fact that there's a custom icon theme available at https://github.com/Sigil-Ebook/IconT...eleases/latest called legacy.rcc that allow users to indulge their fantasy of having Sigil's pre-0.9.7 icons back.

Check out the README at https://github.com/Sigil-Ebook/IconThemes for instructions on how to install/use custom icon themes.

Thank you.

How about charitably taking one further step away from your principles and including the legacy theme in the shipping instalation? Then the dinosaurs who appreciate them have a much higher chance of discovering them!

Any chance of getting back one-click access to header styles?
(OK, scrub that one. I can have that, and more, with a customised Clip Bar. Nice.)

But, of course, mostly thank-you for the continuing improvements.

[DiapDealer]

Nope, and nope.

[Thasaidon]

Originally Posted by DiapDealer

Nope, and nope.

Say what you mean, do not beat around the bush, be more direct and less circumlocutory.

[exaltedwombat]

Originally Posted by DiapDealer

Nope, and nope.

It's more fun to say 'nope' than to explain how to do it, isn't it!

[DiapDealer]

I don't want or need a legacy theme. It's not up to me to exp!ain it. The instructions in the README file at the link provided will suffice. Those who are are unable to follow those instructions are unlikely to be able to find, download, or use Sigil in the first place.

I very much subscribe to the Rolling Stones' philosophy when it comes to Open Source distribution. Thought that was pretty clear by now. You don't try, you don't get.

[StephV]

Hi,

I updated to 1.4.0 but it appears that this update is not working at all for me. Every book I open (that validated fine previously and contains no epubcheck errors) suddenly aren't "well-formed" (but really, there is no error at all and the headers are the same on every xhtml file within a single file).



Here is a "well-formed" header:



And here is a "faulty" header (according to 1.4.0):



Unfortunately, as I need a few tools that are blocked by the "well-formed" validation, I'm forced to revert back to 1.3 for now...