Toolset 3.0.2 released

[Alex Cabal]

Upgrade with `pipx upgrade standardebooks`.

Besides completely type hinting the codebase, this is mostly a bug fix
release.

Changelog:

# 3.0.2

## General

- Fully type hint codebase and switch from `mypy` to `pyright`

- Simplify list/int accumulations with dictionaries using `defaultdict`.
Thanks to Andrew Paseltiner

- Fix f-string errors causing some crashes

## se build

- Don't hyphenate Kobo builds after all, because it breaks the dictionary

- Process MathML compatibility before simplifying CSS to ensure classes
are correct

- Correctly generate class name without spaces when simplifying CSS selector

## se build-toc

- Correctly get inner XML of a ToC item node

## se create-draft

- Omit `src` directory for white-label drafts. Thanks to Andrew Paseltiner

## se lint

- Add m-089, gnore rule ignores the same line more than once.

- Don't apply t-030 to personal names

- Resolve paths to ensure they are compared consistently in m-045.
Thanks to Andrew Paseltiner

- Improve c-019

[David]

I'm enjoying the `lint` enhancements. Meanwhile, I've run into a potential oddity while prepping Romola.

I have an endnote entirely in Italian, and had it marked up like this (line-breaks added for presentation here):

```

<li id="note-21" epub:type="endnote" xml:lang="it">
  <p>“Quando una donna è grande, ben formata, porta ben sua
  persona, siede con una certa grandezza, parla con gravità,
  ride con modestia, e finalmente getta quasi un odor di Regina;
  allora noi diciamo quella donna pare una maestà, ella ha una
  maestà.” <cite>—Firenzuola: <i epub:type="se:name.publication.book">Della
  Bellezza delle Donne</i></cite>
  <a href="chapter-19.xhtml#noteref-21" epub:type="backlink">↩</a></p>
</li>
```

I *thought* the "top level" language declaration would cover the whole note, but I needed to add an extra `xml:lang="it"` to the italics wrapper of the book title for lint to be happy. Otherwise it complained about titlecasing.

Is this expected? or should the "top level" language declaration cover the `<cite>` as well?

[Vince]

This is not related to the new version of the toolset; it’s always been like this.

I don’t know what’s “correct” from an SE perspective, but Gibbon has hundreds of these, and I always used separate italics for the quote and the publication, because, as in this instance, there is material that should not get the tag. E.g., here Firenzuola should not be italicized or have a tag.

[David Reimer]

Makes sense! Scary to think in terms of "hundreds" of these. :/

On Fri, 13 Mar 2026 at 16:3, Vince wrote:
>
> This is not related to the new version of the toolset; it’s always been like this.
>
> I don’t know what’s “correct” from an SE perspective, but Gibbon has hundreds of these, and I always used separate italics for the quote and the publication, because, as in this instance, there is material that should not get the tag. E.g., here Firenzuola should not be italicized or have a tag.
>