Skip to content

epubveri for Sigil 0.3.1

Choose a tag to compare

View all tags
@bariskayadelen bariskayadelen released this 09 Sep 10:14
· 2 commits to main since this release
sigil-v0.3.1
044a647

  • A new plugin icon, and it is a pair of colours rather than one. The old
    mark was a teal page with a white tick, and teal #1b5f7a measured
    2.00:1 on a dark editor ground — the case DiapDealer had warned about.
    No single colour clears 3:1 against both mid grey and black; the luminance
    windows do not overlap. Ink for light grounds and yellow for dark ones does,
    and the worst of five grounds measured is now 6.71:1.

    Deliberately not green, red or amber: the icon is the tool, not the verdict
    — it looks the same whether your book is valid or broken — and those three
    are already this plugin's severities.

  • Corrected: Sigil's results panel has no type column, and the README used
    to imply it did.     The claim sat in two places — the plugin source, where it
    was the stated reason for showing every severity by default, and the README
    section on what is in the report. Sigil's ValidationResultsView sets four
    columns, File / Line / Offset / Message, and carries the severity only as
    a row colour: a pale tint in a light theme, coloured text in a dark one.
    With a single row in the panel there is nothing for that tint to be compared
    against.

    What is actually true is that this plugin writes the label, because the
    message is the only column a plugin controls — so USAGE OPF-088: … is ours,
    not Sigil's. The README now says so, and tells a reader comparing the panel
    against epubcheck to read the first word of each line, since epubcheck hides
    USAGE without -u and has no ADVISORY at all.

    No behaviour changed. Every edit to plugin.py is a comment. What an
    editor panel should do with findings that are not defects is a live question
    in MobileRead thread 374286, deliberately left to the thread because it sets
    the rule for the command line, both plugins, epubsana and later
    integrations; the default stays as it shipped until that is answered.

    Worth keeping: it was drift rather than ignorance. This same repository
    already stated the truth twice — the README's sorting section and the
    CHANGELOG entry for 0.3.0 both say there is no severity column. Only the
    copy being used as an argument went wrong.

Nothing in the plugin's behaviour changed. The plugin.py that Sigil runs
is byte-for-byte what 0.3.0 shipped — verified by unpacking the published
0.3.0 asset and diffing it against this one with comments stripped. Only the
icon, the README, the CHANGELOG and the version differ.

Install

Download epubveri_sigil_v0.3.1.zip and add it in Sigil under
Plugins → Manage Plugins → Add Plugin. Do not rename the file: Sigil
derives the plugin's folder name from the part of the filename before the
first _, and a mismatch is refused outright.

Verify it first if you like:

shasum -a 256 epubveri_sigil_v0.3.1.zip

against SHA256SUMS.txt below.

Assets 4
Loading