MobileRead Forums - View Single Post

Kayadelenium · 09-04-2026, 02:43 PM

epubveri for calibre 0.3.0 — everything asked for in this thread yesterday, plus two things that turned out to be my fault.

https://github.com/veripublica/epubv...calibre-v0.3.0

thiago.eec's four (post 19) and Doitsu's additions (post 20):

Severity colours are back, and the light set is Doitsu's to the byte — the same pale red, yellow and cyan, so the two plugins look alike rather than nearly alike. In a dark theme the same three families are used at dark lightness instead, and your theme's own text colour is left alone.

Columns sort. The first one is called Severity now, and it sorts by rank rather than alphabetically, so a fatal is never below an error. Line sorts as a number, so line 9 comes before line 10. Each severity group still reads top to bottom in book order. The panel opens severest first; Preferences has a box to change that to least-severe-first or to the order the findings occur in the book, and a header click beats it for the session.

The settings are in the editor now. The toolbar button still validates when you click it; its arrow opens Validate now, Show the results panel, and the settings. The results panel's right-click menu has them too. Changing anything re-lists the run you already have instead of asking you to validate again.

The dock no longer comes back on screen at startup. It remembers where you put it and not whether it was open.

Rows select with Ctrl+click and Shift+click, Ctrl+C copies them as tab-delimited text, and the right-click menu exports: CSV of the table as you are looking at it, or epubveri's whole JSON report, filtered by nothing — that second one is the file to attach if something looks wrong.

PeterT's install error was not a false alarm (post 18). Doitsu's plugin keeps its copy of the binary in a file called plugins/epubveri, and that is exactly the name this plugin wanted for a folder — on Linux and macOS, not Windows. Each was in the other's way: his file stopped our folder being created, and our folder would have stopped his plugin executing its binary. Ours has moved to plugins/epubveri-data, a folder left by 0.2.0 is moved there on first use, and a file at the old name is his and is never touched. Anyone coming from his plugin on Linux or macOS would have hit this.

And we were breaking his plugin in his own settings file. calibre keys preferences by plugin name and both plugins are called epubveri, so the two share one plugins/epubveri.json. Nine keys of ten are distinct; last_update_check is not. His is time.time(); ours was an ISO string, which made his update check raise TypeError for anyone who ran ours and then his. It now writes the number he expects and reads both. Sorry, Doitsu — and it could only ever have shown up on your side.

Tested on macOS only, again. Windows and Linux reports welcome, especially the dock and the two export dialogs.

09-04-2026, 02:43 PM	#22
Kayadelenium Zealot Posts: 129 Karma: 200000 Join Date: Jul 2026 Location: Planet Earth Device: Kobo Forma	epubveri for calibre 0.3.0 — everything asked for in this thread yesterday, plus two things that turned out to be my fault. https://github.com/veripublica/epubv...calibre-v0.3.0 thiago.eec's four (post 19) and Doitsu's additions (post 20): Severity colours are back, and the light set is Doitsu's to the byte — the same pale red, yellow and cyan, so the two plugins look alike rather than nearly alike. In a dark theme the same three families are used at dark lightness instead, and your theme's own text colour is left alone. Columns sort. The first one is called Severity now, and it sorts by rank rather than alphabetically, so a fatal is never below an error. Line sorts as a number, so line 9 comes before line 10. Each severity group still reads top to bottom in book order. The panel opens severest first; Preferences has a box to change that to least-severe-first or to the order the findings occur in the book, and a header click beats it for the session. The settings are in the editor now. The toolbar button still validates when you click it; its arrow opens Validate now, Show the results panel, and the settings. The results panel's right-click menu has them too. Changing anything re-lists the run you already have instead of asking you to validate again. The dock no longer comes back on screen at startup. It remembers where you put it and not whether it was open. Rows select with Ctrl+click and Shift+click, Ctrl+C copies them as tab-delimited text, and the right-click menu exports: CSV of the table as you are looking at it, or epubveri's whole JSON report, filtered by nothing — that second one is the file to attach if something looks wrong. PeterT's install error was not a false alarm (post 18). Doitsu's plugin keeps its copy of the binary in a file called plugins/epubveri, and that is exactly the name this plugin wanted for a folder — on Linux and macOS, not Windows. Each was in the other's way: his file stopped our folder being created, and our folder would have stopped his plugin executing its binary. Ours has moved to plugins/epubveri-data, a folder left by 0.2.0 is moved there on first use, and a file at the old name is his and is never touched. Anyone coming from his plugin on Linux or macOS would have hit this. And we were breaking his plugin in his own settings file. calibre keys preferences by plugin name and both plugins are called epubveri, so the two share one plugins/epubveri.json. Nine keys of ten are distinct; last_update_check is not. His is time.time(); ours was an ISO string, which made his update check raise TypeError for anyone who ran ours and then his. It now writes the number he expects and reads both. Sorry, Doitsu — and it could only ever have shown up on your side. Tested on macOS only, again. Windows and Linux reports welcome, especially the dock and the two export dialogs.