[Mister L]

Originally Posted by DNSB

For what it may be worth, the epubcheck plugin for Sigil installs in the Sigil configuration directory. On my Windows 11 machine, this would be C:\Users\<username>\AppData\Local\sigil-ebook\sigil\plugins\EpubCheck.

Thanks, that's good to know.

Originally Posted by DiapDealer

People tend to confuse/conflate the Sigil plugin with a download from the official EpubCheck website that has "plugin" in the name.

I do understand the plugin and epubcheck are 2 separate things. Both were out of date, in this instance. I updated the Sigil plugin manually, and it then (automatically) updated its copy of epubcheck, from github.

Originally Posted by Doitsu

Older plugins came with the EPUBCheck java files, but since the file size of the latest EPUBCheck version has become too large, the latest plugin version no longer comes with the .java files and tries to automatically download the EPUBCheck .java files from Github. It'll automatically display the generic update dialog.

Yes, I remember this change. But usually, when there is a new version (of the plugin, or of epubcheck) it will tell me about it, and (at least for epubcheck) automatically install the new version (this is what happened today, after I manually installed the latest version of the plugin: the first time I ran it, it updated epubcheck). That that didn't happen for the latest version, and I'm wondering why.

Originally Posted by Doitsu

As for the deleted locale code, you most likely made a mistake when editing the .json file, and if the plugin can't load entries from the .json file because of syntax errors, it'll re-create the .json file from scratch.

If you add a "locale": "fr", entry, make sure to add it a the top after the open curly brace:

{
  "locale": "fr",

because if you add it at the end, you'll need to add a comma to the last entry and remove the comma after "fr".

I don't have a copy of the old preferences file anymore but I do remember the locale line was the first one. I don't remember changing anything else, but if I did, would that explain why the plugin didn't check for / install the update? (To be clear, this worked before, and I don't remember changing anything else, but it's possible I did and forgot about it. I just would like to understand the cause of the problem to hopefully avoid it in future because it's a bit embarassing to send a file I think is valid to a client and get it returned due to a validation error I missed. )


Thanks all for the help