MobileRead Forums - View Single Post - [Plugin] epubveri

Kayadelenium · 09-03-2026, 03:57 PM

DNSB — I cannot reproduce the automation, and I would rather ask than guess at it.

What I can tell you is that a validation which completes returns zero, whether the book is valid or not; there is a test on that now, against a clean book and a broken one. So on an ordinary run Sigil is not being told the plugin failed, and the mechanism DiapDealer describes is not the one you are hitting — which means I am missing something rather than that you are. Three questions, and any one of them may be enough:

Which automation is it, and does it also error on a book with nothing wrong with it? What appears in the plugin's output window when it happens? And does it stop if you comment out the summary line BeckyEbook pointed at?

Your report did turn up a real defect on the way, and a worse one than an exit code. PluginRunner::launch checks the return value before it copies the plugin's results into the wrapper XML. On anything non-zero it writes a failed result and returns early, so every add_result is discarded. Five paths in this plugin report a problem and then return non-zero — there is no binary, its checksum did not match, epubveri would not run, it could not read the book — and each one wrote its explanation into the results table and threw it away. You were told the plugin failed and nothing about why. Those five messages have never been read by anyone.

They are printed now, because standard output reaches the output window on both paths. DiapDealer — that is your #26 applied to a line you did not mean it for, and it was the right advice twice.

BeckyEbook, Doitsu — the summary is switchable in the next version, along with usage notes and advisory findings, all three defaulting to on so that nobody who ignores the settings sees any change. When the summary is off it is printed rather than dropped: the results table is empty, and you can still see that the plugin ran and what it decided. A category you switch off still says so in the summary with its count, because a panel with no usage notes should not read the same as a panel whose usage notes were filtered — and on Sigil that line is the only place the settings can be discovered at all.

Doitsu — the plugin's own version is in that line too now, beside epubveri's. Most of what has gone wrong here so far was the plugin rather than the validator, so it was the more useful of the two numbers to be missing.

DiapDealer — the icon is redrawn and the tile is gone. It is a filled document silhouette with the tick knocked out of it: it still carries its own contrast, so no theme shows through it, but the outline is the mark rather than a rectangle drawn around the mark, which is what lets it sit among glyphs that are strokes on nothing. The old one also put a page about seven pixels wide at 16 with the tick inside that, which is the half of "simpler is best" I had not seen until you said it.

09-03-2026, 03:57 PM	#27
Kayadelenium Groupie Posts: 163 Karma: 363834 Join Date: Jul 2026 Location: Planet Earth Device: Kobo Forma	DNSB — I cannot reproduce the automation, and I would rather ask than guess at it. What I can tell you is that a validation which completes returns zero, whether the book is valid or not; there is a test on that now, against a clean book and a broken one. So on an ordinary run Sigil is not being told the plugin failed, and the mechanism DiapDealer describes is not the one you are hitting — which means I am missing something rather than that you are. Three questions, and any one of them may be enough: Which automation is it, and does it also error on a book with nothing wrong with it? What appears in the plugin's output window when it happens? And does it stop if you comment out the summary line BeckyEbook pointed at? Your report did turn up a real defect on the way, and a worse one than an exit code. PluginRunner::launch checks the return value before it copies the plugin's results into the wrapper XML. On anything non-zero it writes a failed result and returns early, so every add_result is discarded. Five paths in this plugin report a problem and then return non-zero — there is no binary, its checksum did not match, epubveri would not run, it could not read the book — and each one wrote its explanation into the results table and threw it away. You were told the plugin failed and nothing about why. Those five messages have never been read by anyone. They are printed now, because standard output reaches the output window on both paths. DiapDealer — that is your #26 applied to a line you did not mean it for, and it was the right advice twice. BeckyEbook, Doitsu — the summary is switchable in the next version, along with usage notes and advisory findings, all three defaulting to on so that nobody who ignores the settings sees any change. When the summary is off it is printed rather than dropped: the results table is empty, and you can still see that the plugin ran and what it decided. A category you switch off still says so in the summary with its count, because a panel with no usage notes should not read the same as a panel whose usage notes were filtered — and on Sigil that line is the only place the settings can be discovered at all. Doitsu — the plugin's own version is in that line too now, beside epubveri's. Most of what has gone wrong here so far was the plugin rather than the validator, so it was the more useful of the two numbers to be missing. DiapDealer — the icon is redrawn and the tile is gone. It is a filled document silhouette with the tick knocked out of it: it still carries its own contrast, so no theme shows through it, but the outline is the mark rather than a rectangle drawn around the mark, which is what lets it sit among glyphs that are strokes on nothing. The old one also put a page about seven pixels wide at 16 with the tick inside that, which is the half of "simpler is best" I had not seen until you said it.