Closed ebeshero closed 1 year ago
Another option: We could choose to normalize typesetter errors like this, and preserve this as an example to discuss in the Methods page on the site. Since it's not an intentional change, just a mistake in the press, I think this fits the other kinds of things that we purposefully normalize for the sake of reading for meaningful variation. If we normalize it, it literally means supplying the missing letter u
and removing the accidental space, and that should be marked appropriately in our TEI (we can do this). Let's think about it and revisit C08
as needed.
In at least one place in this project, there’s a
<comment>
element that we may want to make visible in the edition interface. There’s a printing error (literally on the paper) of the 1823 edition at one point in C08, and one of our original team, @Rikkm , marked this on checking with an XML comment. I didn’t want to lose comments like that, so I output them as<comment>
elements. Here’s what we have in C08:Our Python collation script is instructed to ignore
<comment>
elements (good b/c they aren’t part of MWS’s writing). I have an idea to convert anything that’s formatted like this into a special<note>
element for display in the interface, except we need to be very clear it’s not MWS’s note but one of us commenting.