Sigil-0.9.16 Released

[mcdummy]

Hi,

could you please also add a portable (e.g., self extracting zip) version of sigil to the binary releases. So far only Windows installers are downloadable. I'm working on several computers and so it would be easier for me to put sigil on a USB stick.

I know that there is a version on portable apps. But the current program is still version 9.10 and there do not seem to be any updates.

Regards,

McDummy

[lwalper]

And that's a problem?

Originally Posted by KevinH

Yes, exactly like all other Sigil "Open With" editors.

[Vroni]

Maybe the underline formatting bottom is a candidate to drop it? Sigil is inserting the <u> Element which is not supported by most ereaders.

Whereas text-decoration in a class works well, but cant be accomplished by a single button unless using an inline style which i don't like.

[BetterRed]

Windows 10 Pro 1809

When I tried to set my Inspector widget theme to Dark I got this error:

Error info: Critical: Error saving setting with name: inspectorVersion, value length: 2. Error: Cannot set property 'inspectorVersion' of null
Sigil version: 0.9.16
Runtime Qt: 5.12.3
Compiled Qt: 5.12.3
Platform: Windows SysInfo ID 192

I had to hit Close multiple times to get out of it, at a guess the number of tabs (Elements, Console, ... Audits) times.

And I can't dock it. I'm sure I used to have it under the PV window, but I may be thinking of the calibre ebook-editor.

Had a similar problem in PageEdit, but somehow I got it to use the Dark theme, but I am not sure how - hitting close multiple times and restarting PE were involved. I can dock it in Page Edit, but if I want on the side I have to go full screen. But it doesn't restore the Inspector windows next time I use PE.

BR

[DiapDealer]

The inspector widget in Sigil 0.9.15+ is not a dockwidget. and you didn't have it docked under Preview in previous versions. It was permanently affixed to Preview in previous versions. You could only hide/show it by dragging the splitter bar between them up or down..

I honestly didn't even know that the Inspector HAD theming capabilities. I'll look into it.

The inspector widget in PageEdit IS a dockwidget, however. And though you can't save it so it's always open by default, it will automatically retain it's dimensions and dock location (left, right, top, bottom) from session to session. I have the inspector docked on the right side of PageEdit (without being in full screen) and that position is retained from session to session.

[DiapDealer]

Originally Posted by mcdummy

Hi,

could you please also add a portable (e.g., self extracting zip) version of sigil to the binary releases. So far only Windows installers are downloadable. I'm working on several computers and so it would be easier for me to put sigil on a USB stick.

I know that there is a version on portable apps. But the current program is still version 9.10 and there do not seem to be any updates.

Regards,

McDummy

Creating a portable Windows version of Sigil is not at all a straightforward proposition (as evidenced by the lack of a recent version on PortableApps). It was much easier back when Microsoft's C/C++ runtime was a single dll that could be easily included. But it doesn't work that way any more. An official portable version is just not something we're going to actively pursue at this time.

[DiapDealer]

Originally Posted by Vroni

Maybe the underline formatting bottom is a candidate to drop it? Sigil is inserting the <u> Element which is not supported by most ereaders.

Do you have any definitive examples of devices/apps that will not properly render a <u> tag? Or are you merely basing your statement on the fact that <u> was deprecated for XHTML 4.01? I only ask because <u> has been fully restored as of HTML5, and I've yet to run into a rendering system--browser, ebook reader, or reading app, epub2/3--that didn't correctly render a <u> tag.

[DiapDealer]

Originally Posted by BetterRed

Windows 10 Pro 1809

When I tried to set my Inspector widget theme to Dark I got this error:

Error info: Critical: Error saving setting with name: inspectorVersion, value length: 2. Error: Cannot set property 'inspectorVersion' of null
Sigil version: 0.9.16
Runtime Qt: 5.12.3
Compiled Qt: 5.12.3
Platform: Windows SysInfo ID 192

I had to hit Close multiple times to get out of it, at a guess the number of tabs (Elements, Console, ... Audits) times.

And I can't dock it. I'm sure I used to have it under the PV window, but I may be thinking of the calibre ebook-editor.

Had a similar problem in PageEdit, but somehow I got it to use the Dark theme, but I am not sure how - hitting close multiple times and restarting PE were involved. I can dock it in Page Edit, but if I want on the side I have to go full screen. But it doesn't restore the Inspector windows next time I use PE.

BR

I've found that with Sigil and PageEdit, changing the inspector theme will work regardless of any errors that are produced. The change just won't take effect until Inspector is relaunched (or in the case of PageEdit; until PageEdit itself is relaunched).

Why each of those inspector errors are being intercepted by Sigil's own inherent error dialog system is something we'll have to look into. But either way, you should be able to use the dark theme by dismissing all the errors in Sigil and closing/relaunching inspector. In PageEdit, you'll need to relaunch PageEdit entirely for the theme change to take effect.

This is all on Windows, by the way. I've not tested on other platforms.

[Vroni]

Originally Posted by DiapDealer

Do you have any definitive examples of devices/apps

Sony PRS505, Sony PRS 650, Tolino Shine, Tolino Epos

Apps: Bookari based om RMSDK wich is close to ADE 2.x. So i guess each Ap based on this RMSDK doesnt interpret <u>.

[DiapDealer]

Originally Posted by Vroni

Sony PRS505, Sony PRS 650, Tolino Shine, Tolino Epos

Apps: Bookari based om RMSDK wich is close to ADE 2.x. So i guess each Ap based on this RMSDK doesnt interpret <u>.

Are you absolutely certain? I just sent a quick epub test to my Bookari app (been a Mantano/Bookari user for years) and the u tags I've included render just fine. Tested both the epub2 RMSDK renderer, and the epub3 Readium renderer. I even forced the epub3 to be read with the epub2 rmsdk renderer and couldn't get it to mess up.

You've tested each of these devices/apps personally to see if u tags are rendered?

EDIT: just checked with ADE 2.01 Desktop and no problems.

[KevinH]

Originally Posted by Vroni

Maybe the underline formatting bottom is a candidate to drop it? Sigil is inserting the <u> Element which is not supported by most ereaders.

Whereas text-decoration in a class works well, but cant be accomplished by a single button unless using an inline style which i don't like.

Just add css to use the textdecoration you want for all u tags. All readers should handle that.

[Vroni]

Yes i'm sure, i've all of these devices and Bookari Premium.None of them interpret <u>.

At least epub2, and all of my books/tests are epub2 because the sonys cant handlöe epub3. Maybe eub3 will behave different.

I just mentioned this as a possible candidate which might leave the Style Buttons. If you have some (more or less) important devices/apps/reasons to keep it, just keep it, i dont care. I myself never saw this element working. Same with margin: auto which should be a replacement for centering, but can be ignored by spec

And no, i will not add a style to my css to format <u> correctly. If i really really need it i will create a more suitable css rule.

[DiapDealer]

Originally Posted by Vroni

Yes i'm sure, i've all of these devices and Bookari Premium.None of them interpret <u>.

I have Bookari Premium and u works fine for me (with no css of any kind applied). If it doesn't work for you, then clearly something else is in play here.

I'm not trying to start a war or anything, but since I've verified to my own satisfaction that adobe's RMSDK and ADE, and Readium's (and thus Bookari/Montano) rendering engines are fully capable of rendering u tags properly, I'm simply going to have to see some corroborating evidence that there are multiple scenarios where u tags fall down.

I'm starting a new thread with a test epub attached so we can gather more info.

[Mister L]

Hello, thanks again for the new version, looks like some very interesting new features are included which I haven't yet fully explored.

I have a question, is there a way to save my toolbar preferences?

Specifically, I dragged the plugins next to the "change case" button in the second row for easier access both to them and to my clips, but every time I close and re-launch they are back down in the clips bar. Is there a way to get them to stay there (or, if I change my mind in future, a different place, but definitely not the clips bar)?

I'll attach a screenshot to show what I mean.

In a similar vein, I'd love to be able to save my preferred configuration for the preview panel especially now that bookview is gone, so that it's always open and where I want it when I launch (undocked, next to the main Sigil window). It sounds like you have some ideas on that topic so hopefully that will be coming soon.

Thanks again for all the hard work, very greatly appreciated.

Edit : forgot to mention, thanks in particular for the checkmark in the semantics dialogue and the epub3 backwards compatibility tools. Backwards compatibility is very important to me.

[DiapDealer]

All toolbar arrangements and widget placement should be restored when re-launching Sigil. Just know that if you have multiple instances of Sigil open simultaneously, the last configuration of the last instance closed is going to be the one that's saved. All of the toolbar/widget settings are saved/restored from the Sigil.ini file.