epubcheck plugin for Sigil

[Gregg Bell]

Doitsu, I was getting the message that Epub Chek 4.1 was available in Sigil. So I followed your instructions on the first page of this thread but I wasn't able to select the "Bundled" python. Still I was able to get 4.1, so that's okay, right? And I was looking in the General Settings--should I be using the CSS Level 2.1. (I don't do any epub3s.) Thanks.

[Doitsu]

Originally Posted by Gregg Bell

So I followed your instructions on the first page of this thread but I wasn't able to select the "Bundled" python.

On Linux machines, the Use Bundled Python option is not available. As DiapDealer has already pointed out, you'll need to click the Auto button, if the ≥Python 3.4: box is empty. If it already contains a path, there's nothing you need to do. I.e., if one plugin works, most other plugins will work, too. (Some require additional Python libraries, though.)

Originally Posted by Gregg Bell

And I was looking in the General Settings--should I be using the CSS Level 2.1.

The CSS Level setting is ignored by the EpubCheck plugin; it only affects the Tools > Validate Stylesheets With W3C menu option. (For epub2 books, you should select CSS Level 2.1.)

[Gregg Bell]

Originally Posted by Doitsu

On Linux machines, the Use Bundled Python option is not available. As DiapDealer has already pointed out, you'll need to click the Auto button, if the ≥Python 3.4: box is empty. If it already contains a path, there's nothing you need to do. I.e., if one plugin works, most other plugins will work, too. (Some require additional Python libraries, though.)


The CSS Level setting is ignored by the EpubCheck plugin; it only affects the Tools > Validate Stylesheets With W3C menu option. (For epub2 books, you should select CSS Level 2.1.)

Thanks Doitsu. I'm all good then.

[jcsalomon]

Can the EPUBCheck v4.2.0 (alpha 1) test relese be dropped-in on my installation, or would the plugin need to be updated?

[Doitsu]

Originally Posted by jcsalomon

Can the EPUBCheck v4.2.0 (alpha 1) test relese be dropped-in on my installation, or would the plugin need to be updated?

The plugin will also work with the EPUBCheck v4.2.0 (alpha 1) release. Simply rename or delete epubcheck.jar and the lib folder and copy epubcheck.jar and the lib folder from the alpha version to the plugin folder.

[odamizu]

Greetings!

I'm trying to get the validation results window to dock at the top of the main window instead of the bottom.

I tried moving it to the top of the window but I can't get it to stick/dock up there. However, I am able to get other widgets, like Book Browser, Preview, and Table of Contents to dock at the top.

Any idea what am I doing wrong?

Thank you!

[BeckyEbook]

Originally Posted by odamizu

Any idea what am I doing wrong?

It was on purpose.
Validation results window can be docked only to bottom.

setAllowedAreas(Qt::BottomDockWidgetArea);

[odamizu]

Okay, thank you. This is in the Sigil app code rather than the plugin code? (If so, it's definitely beyond my limited tech skills )

[BeckyEbook]

Originally Posted by odamizu

Okay, thank you. This is in the Sigil app code rather than the plugin code? (If so, it's definitely beyond my limited tech skills )

Yes, it's code from ValidationResultsView.cpp file.
A small change is enough:

setAllowedAreas(Qt::BottomDockWidgetArea | Qt::TopDockWidgetArea);

I checked today and it turns out that validation window on top is pretty cool.
When making corrections, you do not look at the bottom of the screen, but under the toolbars and over Code View.

[Doitsu]

Originally Posted by BeckyEbook

I checked today and it turns out that validation window on top is pretty cool.

Can you create an official Sigil Github pull request? If it's just a simple change @KevinH or @DiapDealer will most likely approve it for the next version.

[odamizu]

Originally Posted by BeckyEbook

Yes, it's code from ValidationResultsView.cpp file.
A small change is enough:

setAllowedAreas(Qt::BottomDockWidgetArea | Qt::TopDockWidgetArea);

I checked today and it turns out that validation window on top is pretty cool.
When making corrections, you do not look at the bottom of the screen, but under the toolbars and over Code View.

Thank you! I found ValidationResultsView.cpp, but building Sigil is definitely beyond my skill set.

What's the best way to request this change in the next Sigil release? Should I start a new thread? PM DiapDealer and KevinH? Figure out how to post on GitHub?

Oops! Doitsu beat me to this. Thank you!

[DiapDealer]

https://github.com/Sigil-Ebook/Sigil...b3acd3a4331a50

[odamizu]

Thank you muchly everyone!

[Doitsu]

The DAISY Consortium has released a new version: EPUBCheck v4.2.1.

To get this update, go to the EpubCheck preferences folder (Edit > Preferences > Open Preferences Location), Edit EpubCheck.json, add/change the following entry:

  "github": true,

save EpubCheck.json and run the EpubCheck plugin. This should initiate the auto-update code that I added in the last version, which'll automatically download the latest EPUBCheck version from the W3C Github website.

[lumpynose]

Originally Posted by Doitsu

The DAISY Consortium has released a new version: EPUBCheck v4.2.1.

As Bill and Ted would say: Excellent!

I also turned on the clipboard thing; I've always wanted to see those messages that flew by.

What does the usage flag do when it's on?