I've worked through most of the curly-braced entities and built on the taxonomy JT created for glyphs, splitting it into two (ligatures and single chars), just to aid in clarity; I've created equivalences in the form of choice elements in a list in a TEI file, and that can be plugged into any transformation. The idea would be to order the items by length descending, so the long ones are done first, and have a template that matches text() and runs all the equivalent replace things using analyse-string. We may have to build the analyze-string element mechanically. Alternatively, we could just run a scripted cli replace thing.
This entry was posted by and is filed under Activity log.