Very hasty reply ...
> <sp who="Fool">
> <speaker>Fool</speaker> <lg>blabla</lg>
> <???>Fool</???> <lg>blabla</lg>
> ... I thought about using <fw>, as this <speaker>-heading-repeat is
> not unsimilar to a catch-word. But <fw> is not included in the
> content model of <sp>,
This, imho, is simply an error. Clearly anywhere there can be a PB
there can be an FW. This (using FW) solution seems the best to me,
although the repeated "Fool" speaker-like-thing you are encoding is
not really part of the forme. Here at the WWP we have renamed FW to
MW (for "metawork"), included it wherever PB can go, and use it for
this very kind of thing.
> Splitting the speech at the page-break and re-linking it seems a
> bit excessive to me.
Nonetheless, it is a perfectly reasonable solution.
> So I may need to put a modified version of the <sp> content in the dtd
> extension file. <sp>'s content model is a bit to complex ...
When making modifications to the DTD, one generally doesn't have to
deal with a content model in its raw form as you get it back from the
pizza chef. Rather, you can (and should) modify it in its source
form. In this case, the declaration for SP is (note that I am using
P3 SGML DTDs):
<!ELEMENT %n.sp; - O ((%n.speaker)?, (%n.p; | %n.l; |
%n.lg; | %n.seg; | %n.stage;)+) >
Note that there is no reference to the globally included stuff like
PB, LB, and MILESTONE. Those things are actually part of an inclusion
exception on the TEXT element. So, presuming you want to add FW to
the list of elements in the global inclusion exception on TEXT, you
would put the following declaration in your TEI.extensions.ent file:
<!ENTITY % x.globincl '%n.fw;' >
What this does is put FW (or whatever it has been renamed to) into
the x-dot class for the globally included elements class. The x-dot
class is automatically included in the corresponding m-dot class. (I
realize this can be confusing -- see chapter 27. and I can try to
write a more coherent explanation in a few weeks, but am very busy
If recollection serves, this is all you have to do. (In many cases
you would also have to remove FW from some other class, to avoid
ambiguous content models.)
> Or have I overlooked an element that I could use?
How about SEG? E.g., <seg type="metawork" subtype="repeat-heading">
Hope this helps.