projectLEMDO / lemdoIssues

Repository for LEMDO issue tracking and related documents.
MIT License
1 stars 0 forks source link

Develop encoding model for interrupting speeches #231

Open JanelleJenstad opened 3 weeks ago

JanelleJenstad commented 3 weeks ago

We have a speech by Ferdinand in LLL F1 with persistent interruptions by the Clowne (Costard). The interruptions are inserted into the speech parenthetically (see image that Sofia will upload) with a speech prefix and the brief speech (Clo Me?).

I'd like an encoding practice that respects the mise-en-page while allowing us to track speeches.

We'll also need to figure out a numbering protocol. My first instinct is to use <spGrp> ... and to not number the interruptions but rather number the container <spGrp>.

sofiawilson commented 3 weeks ago

Screenshot from 2024-06-04 14-25-11

martindholmes commented 3 weeks ago

We could devise something like sp type="inline", but our biggest problem would be that TEI sp cannot be a child of p or l or sp or anything else that might constitute the content of the container speech, so you can't actually reflect the nesting here. This is the problem with semi-diplomatic: if you're going to be at all undiplomatic in the sense of deciding you will identify some things as e.g. speeches, speech-prefixes, and all that, then you're electing to apply the abstract content model to the text, and with that come hierarchical constraints. So for encoding, I would recommend actually splitting the container speech around the contained speeches, and using @next and @prev as we do for other hierarchy violations. That will also make it easier to proof, I think, and to convert to a modern text. We would have to add some signal that the contained speeches are marked off with parentheses (in this case -- maybe not in others), so that the rendering can be faithful. Maybe <sp type="inline" subtype="parenthetical">. But of course sp is not a member of att.typed, so maybe it'd have to be something like <sp rend="inline_parenthetical">.

But the rendering will be a bit gnarly. That'll be a long day.

JanelleJenstad commented 2 weeks ago

Thanks for the suggestion, @martindholmes. I'll mock up some encoding and put in a ticket for processing.