View Single Post
Old Yesterday, 06:43 AM   #42
Kayadelenium
Addict
Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.Kayadelenium ought to be getting tired of karma fortunes by now.
 
Kayadelenium's Avatar
 
Posts: 203
Karma: 363834
Join Date: Jul 2026
Location: Planet Earth
Device: Kobo Forma
A question for everyone using this plugin, before I add something to it.

In the epubveri thread, JSWolf, DiapDealer and DNSB asked for a warning when an HTML file is larger than 260 KB uncompressed. That is the size calibre splits at, because some older reading systems cannot handle larger files. I have it ready as ADV-013: an advisory note, never an error, that never changes the verdict and only names the file and its size.

The catch is that this plugin shows advisory findings by default. So after the update, a book with a large chapter that is clean today would show one ADV-013 row. And if you use Sigil's automation lists, any row stops the list, including a note.

So which would you prefer?
  1. Show it like the other advisory notes (on by default; the advisory switch in the plugin's preferences turns it off, together with the other advisory notes).
  2. Keep it off unless you switch it on yourself.
  3. Leave it out of the Sigil plugin; Tools / Reports already lists every HTML file's size.
Nothing changes until I have heard from you.
Kayadelenium is offline   Reply With Quote