I'm nearly there, thank you all for your help.
As I said, I've defined %chowder to refer to the assorted fishy bits we
are using for content markup. Now all I have to do is enable our dtd to
be attached to the TEI chain. It's probably in the docs (heh) but I don't
have time to RTFM right now, so excuse what may seem to be dim questions.
The TEI constructs assume (I think, or rather, sgmls needs):
[SGML.dec]
[TEI1.dtd]--->[lots of other TEI dtd files]
and eventually
<TEI.1><TEI.header>etc etc</TEI.header>
<text>
the encoded text itself
</text></TEI.1>
Correct? OK, where do I slip in our own mods? Currently I have
[SGML.dec]
[curia.dtd]--->[TEI1.dtd and lots of other TEI dtd files]
but we need to go
<TEI.1><TEI.header>etc etc</TEI.header>
<text>
<ms>
the encoded text itself
</ms></text></TEI.1>
or something like, because at some stage we need to escape from the
construct of
<text><front>...</front><body><divn>...</divn></body></text>
so that we can branch off into
<text><ms><incipit>stuff</incipit><textus>lotsa stuff</textus></ms></text>
How do I make this branch out of the TEI framework into our own? Clearly, I
could bodge TEIbase1.dtd but I don't want to do that. What's the TEI.additional
entry there for? Can I slip things in here, and if so, how can I still make
<text> branch out of its <front><body><back> stuff without doing damage to
people wanting to read other TEI-compliant files than our own? Or is is as
simple as
<!ELEMENT text - - (front?, (body|ms), back?)...
<scream type=silent>
///Peter
</scream>
|
