Skip to content

Sigil-0.9.12
Compare
Choose a tag to compare
@dougmassay dougmassay released this 19 Feb 21:59
· 2436 commits to master since this release
0.9.12
This tag was signed with the committer’s verified signature.
dougmassay Doug Massay
GPG key ID: 56CD953D30E1BBCD
Learn about vigilant mode.
2c70d2e

This is a buggy version of Sigil. Don't use it. If you have good backups of your Sigil 0.9.10 (or earlier) preferences, roll back to Sigil 0.9.10 and restore your backed up preferences. If you don't have backups of your Sigil 0.9.10 (or earlier) preferences, roll back to Sigil 0.9.10 anyway and recreate your preferences as best you can from within Sigil's UI. Those preferences will be usable with the release of Sigil that follows 0.9.12.

This Sigil release is primarily to address bugs introduced by the upgrade to Qt5.11.2 and Python 3.7 in the previous release.

Bug Fixes

  • fix typo in cssreformatter that caused errors with @ fontface (issue #394)
  • workaround for qt bug affecting tab close buttons on Mac (commit f3b9399)
  • fix Mac Qt5 plugin dylibs that macdeployqt broke in Sigil-0.9.11

Be aware that Sigil-0.9.12 still enforces the need for epub3 to have and support an NCX so that it generates as backward a compatible epub as possible. This may be relaxed in future releases.

Starting with Sigil-0.9.11, Sigil's ini preference files will be utf-8 encoded to more easily allow users to manually edit them. NOTE: before upgrading to Sigil-0.9.11, please make and save a backup of your preferences files. There is no issue with the conversion moving forward, but if, for whatever reason, you need to roll back to an earlier version of Sigil, utf-8 encoded unicode characters in your ini files will not work with earlier versions of Sigil. So please be safe and make a backup just in case.

The decision to move to utf-8 encoded preference files was reverted and will be back to normal starting with Sigil v0.9.13

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

Assets 5
Loading