Sigil-0.9.14 Released

[DiapDealer]

Sigil-0.9.14

For the impatient, the installer files (and source) can be found as assets at the bottom of the Github Release page.

---------------------------------------------------------------------------

This Sigil release is primarily to address performance issues and memory leaks, but there are a still some new features and other bug fixes as described below.

Bug Fixes

• flush all changes to disk before creating a Report so that files sizes are correct
• stop writing python bytecode to Program Files on Windows
• remember cover semantics if cover image replaced by Add Existing...
• fix issues with the Plugin Framework documentation epub
• more memory leaks plugged
• minor code cleanups

New Features

• updated to Qt 5.12.3 with Annulen Webkit 5.212 with extra QtCursor memory leak fixes
• updated to Python 3.7.2
• updated build docs for macOS, Linux and Windows
• build system now uses GNUInstallDirs to determine the best installation libdir on Linux
• updated desktop integration for Linux
• reduce PCRE cache size to help lower memory footprint
• improve mapping of hunspell dictionary names to actual language names (thanks BeckyDTP)
• add warning during import if unmanifested files exist in the epub zip archive
• no longer requires use of non-breaking space entities (or any entities at all!)
• special spaces are now visisble via syntax highlighting in CodeView
• dropping epubs on Sigil.app no longer opens an extra empty epub on macOS
• reload Preview only when needed to help prevent screen flicker and lower memory use
• enabled Windows automated builds using Apppveyor
• Windows releases now compiled with Visual Studio 2017
• characters in HTML files report now uses gumbo for speed
• allow user's custom plugin icons to survive a plugin update

Sigil 0.9.14 will mark the last version that uses QtWebKit, and will be the last version to support editing in BookView. More here.

Be aware that Sigil-0.9.14 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.

---------------------------------------------------------------------------

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

Sigil-0.9.14 release page and downloads.

[odamizu]

As always,

[Doitsu]

Originally Posted by DiapDealer

New Features

• no longer requires use of non-breaking space entities (or any entities at all!)
• special spaces are now visible via syntax highlighting in CodeView

Thanks for this helpful new feature!

Is it possible to change the non-breaking space replacement characters by applying a Qt stylesheet or source code modifications?

[Horus68]

Windows-x32 pack missing from the release page

[DiapDealer]

Originally Posted by Horus68

Windows-x32 pack missing from the release page

I plan to get it added soon. But please take note of the various notices (here and on Github) that I will not be providing a Windows 32-bit installer for very much longer.

[DiapDealer]

Originally Posted by Doitsu

Thanks for this helpful new feature!

Is it possible to change the non-breaking space replacement characters by applying a Qt stylesheet or source code modifications?

I'm not entirely certain the place-holder underline style/color can be modified via qss, but there are a few options if you modify the source.

It's set in Misc/XHTMLHighlighter.cpp around line 85. It's the .setUnderLineStyle method of special_space_formats. Available choices can be found here: https://doc.qt.io/qt-5/qtextcharform...lineStyle-enum

[najgori]

great job! thanx!

[BeckyEbook]

Originally Posted by Doitsu

Is it possible to change the non-breaking space replacement characters by applying a Qt stylesheet or source code modifications?

QSS IMHO will not work.

The non-breaking space is a space, so you can really apply just underlining. For me default thin underlining seems too delicate.

File: Misc\XHTMLHighlighter.cpp [here]

Original code:

Spoiler:

    special_space_format  .setUnderlineColor(m_codeViewAppearance.xhtml_entity_color);
    special_space_format  .setUnderlineStyle(QTextCharFormat::DashUnderline);

My idea:

Spoiler:

    QPen outline(special_space_format.textOutline());
    outline.setBrush(m_codeViewAppearance.xhtml_entity_color);
    outline.setWidthF(1.0);
    outline.setStyle(Qt::SolidLine);
    special_space_format.setTextOutline(outline);
    special_space_format.setUnderlineColor(m_codeViewAppearance.xhtml_entity_color);
    special_space_format.setUnderlineStyle(QTextCharFormat::SingleUnderline);

[DiapDealer]

Too "delicate" as compared to nothing at all?, or ...

[KevinH]

Please remember that new syntax highlighting is shared by all special spaces and not just nbsp.

static const QString SPECIAL_SPACE_BEGIN = "[\\x{00A0}\\x{2000}-\\x{200A}\\x{202F}\\x{3000}]+";

so if you need to distinguish among the special spaces while editing, selected preserve entities can be set and a Mend on that file or across all files can be done to display them as entities if needed. Clearing the preserve entities and rerunning Mend will remove the entities restoring the character version.

Obviously search and replace can be used to do the same thing but Preserve Entities and Mend will be easier if many different special spaces are used throughout your book.

[BeckyEbook]

Sure. I really like it. I use this for two months from the time you added this feature to the code.

I assigned the F1 key to the Mend command, and Shift-F1 to Mend and Prettify.

When I want to see (some) entities I prefer to use the ShadyCharacters plugin. Continuous changing Preferences / Preserve Entites takes too long.

Now I'm only doing F1 (Mend), and when I want to see (some) entities, I run the plugin (one click). Quickly and efficiently!

In the target file, I prefer not to have a special spaces entities, since Sigil now displays them so nicely in the Code View, which makes reading easier.

The most important thing is that such a feature has appeared. And thank you very much for that.

[DiapDealer]

Originally Posted by BeckyEbook

The most important thing is that such a feature has appeared. And thank you very much for that.

I'm pretty tickled with it, myself. Thanks for figuring it out, Kevin!

[DiapDealer]

allow user's custom plugin icons to survive a plugin update

In case anyone is unclear on this feature: instead of putting your custom icons for plugins in the actual plugin folder (which can get overridden when updating a plugin), you should put them in the plugin's preference folder. Sigil will look there first for the icon to display on the plugin shortcuts toolbar. If none is there, it will then check the plugin folder to see if there's a "plugin.png" included by the plugin's creator.

[lumpynose]

I'm getting aberrant behavior from the pulldowns at the bottom of the search box, its three Mode: pulldowns. I have two monitors, Sigil is full screen on the right monitor, and when I click on the last one, the Up/Down one, its menu briefly appears on the left monitor where it would be if Sigil was full screen on that monitor. That happens consistently. Sometimes the other two will appear on the left monitor and stay there and if I click again on the down arrow they'll reappear in the correct location on the right monitor.

When I click on the TOC button its window appears partly on the left monitor and partly on the right monitor.

[KevinH]

Yes Qt has some issues with true "full screen" on many platforms. Especially if you try to grow the original window after going full screen. Take it out of full screen, then hit the mode button to make everything show, the re-enable full screen. Did that help?