DRE: Wrap in-dialogue stage directions (modern text) in brackets

[JackWilton1594]

When stage directions appear in the dialogue of modern texts, they should be rendered in italics and wrapped in brackets.

Here are two examples from the opening scene of 1HW:

These should render as:

• (To the Duke) I do arrest thee, murderer.
• (To Attendants) Set down,

The guidelines ask editors not to add parentheses or italics in their texts because they will be rendered this way by the system.

It's important that the brackets that wrap SDD are themselves rendered in italics – that way, they will be distinguishable from parentheses in dialogue.

[martindholmes]

I've accomplished this through CSS in rev 18085. This adds CSS parentheses around stage directions which are tagged as delivery. In the results, I see some already have hard-coded parentheses in 1HW, so they now show as doubled. @JackWilton1594 Can you check to see if the results are what you expected?

[JackWilton1594]

Thanks, Martin. It isn't only delivery SDD that need wrapping. It's any SDD embedded in dialogue rather than appearing on their own line.

I appreciate we'll have to go through and remove hard-coded parentheses where they are in the text.

Of course, this is just for DRE/NISE – other anthologies may wish to continue with practice of using square brackets. We just don't think SDD require extra signalling in this way when we don't use square brackets in dialogue.

[JanelleJenstad]

QME will need some kind of override because they wanted to keep their square brackets around child <supplied> elements in <stage>. Our processing resulting in square brackets and round parentheses, which they didn't like. I know we sorted it out for their release in the fall. We just need to check that these new changes don't have any fall-out for QME's beta site.

[JackWilton1594]

Confusingly, there are double parentheses in some SDD. Here in AHDM, for example:

There aren't any hard-coded parentheses in the XML:

`

Lemot

           <p>
              <stage type="delivery" xml:id="emdAHDM_M_s2_sd3"><anchor xml:id="emdAHDM_M_anc_136"/>Aside to Colinet<anchor xml:id="emdAHDM_M_anc_137"/></stage> See where he comes. Now must I say, <foreign xml:lang="la"><anchor xml:id="emdAHDM_M_anc_138"/>Lupus est in fabula<anchor xml:id="emdAHDM_M_anc_139"/></foreign>, for these Latin ends are part of a gentleman and a good scholar.</p>
        </sp>`

[martindholmes]

Maybe we already had a rule to distinguish asides by using parentheses; adding them to non-asides would remove that distinction, so I suspect we need to think again. This needs a decision by everyone on what the various types of stage directions should look like. I'll remove the change I made in rev 18085 and wait for a consensus and a detailed outline of the various stage direction types, contexts, and display rules. We can worry about QME later.

[martindholmes]

Reversed in rev 18266. This ticket's now waiting on a taxonomy of stage-direction types and contexts, with guidelines on display for each type/context.

[JanelleJenstad]

@JackWilton1594: We'll need to meet to decide on further instructions for Martin.

[JackWilton1594]

@JanelleJenstad Sounds good. Apologies for only catching up on these tickets now!

[JackWilton1594]

@JanelleJenstad I don't think we covered this topic in our meeting. My sense is that in-line directions -- that is, @stage within @p or @l -- should inherit the alignment of the line/paragraph and rendered (enclosed within italicised parentheses).

Any directions that require their own line -- e.g. entrances and exits -- shouldn't be included in @p or @l