Sigil-2.4.2 Released

[DiapDealer]

Sigil-2.4.2

Sigil version 2.4.2 is primarily a bugfix release with one new feature. It fixes a number of issues related to Python 3.13+ use. Also note that the Microsoft VC++ runtime redistributable is no longer being bundled in the Sigil Windows installer starting with version 2.3.1. This should already be installed on any Windows PC that Sigil is supported on.


New Features

• Added new tool: 'Update OPF Manifest Media Types' to set unrecognized media types based on actual file contents

Bug Fixes

• ensure CodeView code highlighting colors coincide with dark/light themes on certain Linux DEs
• fix sigil-gumbo gumboc to work with Python 3.13+ - ie. work around backwards incompatible changes in ctypes
• fix Replacement Chooser table to allow for multiple line row heights in Before and After fields (regression)
• prevent too many warnings when no media types provided in OPF by generating the warning collectively
• prevent build warnings by using hunspell's std:string interface (not C char * ones)
• fix files in third party code that used latin-1 encoding to now use utf-8
• fix old use of 'python' in python code header lines to always use 'python3'
• removed user scope installs from winget util they work properly with dependencies
• restore Find&Replace if it was open when the user tries to exit Sigil and then aborts the exit

--------------------------------Notes -----------------------------------

The latest version of the Sigil User Guide can always be downloaded from the Sigil website, or from its own GitHub repository.

Please check the Sigil website for important Sigil support links, additional resource downloads, and platform-specific trouble-shooting tips/requirements.

The MacOS builds are signed AND notarized.

PGP Fingerprint (for signed tags and source archives):

B5A5 6206 AB0F BC1A 24EF AB8A A166 D29A 8FCD AC63

All Sigil binary (and source) downloads can also be found as assets at the bottom of The Sigil-2.4.2 Github Release page.

[DiapDealer]

Post reserved for future use.

[Capricorn]

I have used this new version to edit two epubs. Everything works as I expected.
But I have not used the new feature yet.

[KevinH]

If you have no warnings after loading an epub about unrecognized media types, then there is no need to run the new tool. Your opf manifest media types are all fine.

[DNSB]

I deliberately mislabelled some image files and the tool corrected to the correct media type.

[KevinH]

Originally Posted by DNSB

I deliberately mislabelled some image files and the tool corrected to the correct media type.

Glad to hear it. Thanks for testing it.

[DiapDealer]

For Windows users:

Just a note that Sigil 2.4.2 is now (3 Feb 2025) available via winget. It was already available via Chocolatey, Scoop, and Npackd64.

winget install -e --id Sigil-Ebook.Sigil

choco install sigil

scoop bucket add extras
scoop install extras/sigil

I'm not familiar enough with Npackd to suggest install commands.

[philja]

I've just built Sigil 2.4.2 on my Linux box. This time I used the bundled version of hunspell and didn't see any errors during the make and make install.

However, when I ran the testplugin (v0.2.0) as I usually do, on an epub2 file it produced 4 failures: "Failure - 4 Tests of Plugin Operations Failed". I've not seen such results after other builds.

The epub2 file had 'no problems found' under EPUBCheck 5.2.1.

Verifying selected basic plugin interface elements
  bk.text_iter() works False
  Listing manifested files...
    Text/Section0001.xhtml
    Text/chapter10.xhtml
  bk.manifest_iter() works False
  bk.spine_iter() works False
  bk.other_iter() works False
  reading a non-manifest book file works True
  reading a specific OPF manifest id works True
  writing to a specific OPF manifest id works True
  Launcher Version 20250131
  ePub Version 2.0
  adding your own file to the manifest works True
  basename to id mapping works True
  deleting our added file works True

Next I tried an epub3 file (also 'nff' under EPUBCheck 5.2.1) and got the same results.

What is testplugin trying to tell me?

[Doitsu]

AFAIK, these 4 errors are only shown if you test the plugin with a non-empty epub.

[DiapDealer]

Originally Posted by philja

What is testplugin trying to tell me?

That you're using an outdated version of the test plugin.

Or what Doitsu said.

You also didn't show us the first part of the test plugin's output. The one that shows important paths.

But yes... the proper procedure is to open Sigil with the default empty epub and immediately run the test plugin.

[philja]

Originally Posted by DiapDealer

That you're using an outdated version of the test plugin.

Or what Doitsu said.

You also didn't show us the first part of the test plugin's output. The one that shows important paths.

But yes... the proper procedure is to open Sigil with the default empty epub and immediately run the test plugin.

Thanks Doitsu and DiapDealer. The testplugin is the latest. But I don't know why I thought (this time) that I had to run that plugin with a file open in Sigil. My mistake.

When I run it with the default empty epub, it's perfect.

Sorry about that.

[DiapDealer]

No trouble. I've made that mistake too. And scratched my head trying to figure out what was wrong.

[Vanguard3000]

Okay, I think I've found steps to recreate the disappearing Find & Replace widget I brought up in the previous version's thread.

1) Open a file and open F&R.
2) In F&R, enter a search term that would be found on a different xml file than the one currently opened in the editor. In other words, clicking the find button should open a new tab or switch to a different one.
2) Open a second instance of Sigil - even a new document by middle-clicking the taskbar item. The new instance should have F&R opened, as expected.
3) Close the second instance and return to the first one.
4) Click the Find button. When the new tab opens the F&R widget will be dismissed.

I guess it's a bit of a weird edge case, but it comes up for me a lot as I'm often opening multiple files for reference. If my steps are unclear or whatever I can see about doing a recording if necessary.

[KevinH]

Both Sigils are sharing a single settings ini file. And when one Sigil changes a setting on closing it will alert the other instance of Sigil to update itself as the ini files are watched.

So that is expected behaviour not a bug. And not something I am going to try and change as it would require Sigil to know if another instance exises and change behaviour in what it saves to settings.

[DiapDealer]

I agree it's an edge case that may not warrant a ton of work, but if the second instance of Sigil is merely being opened and then closed (without closing the F&R), what changes are being written to the ini that would cause the F&R widget to close when clicking the Find button (after a new xhtml tab opens) in the original instance? Are the F&R parameters themselves being altered by the second instance opening?

If F&R can be made to disappear by a new tab opening (not an image tab) this way, then I'm guessing a way could be found without involving a second instance of Sigil. If so, that would be a bug, no?