Syd Bauman wrote:
>>I understand that my <seg type="hemistichA/B"> is not the most
>>efficient solution, any advice as to improve it is more than
> Oh it may well be the best way to go. In fact, it's what P4 suggests
> at the beginning of 9.3 "Components of the Verse Line" (P4:2002-03 p.
> 225; http://www.tei-c.org/P4X/VE.html#VESE); one of the examples even
> has type="hemistich". But before committing resources, I'd suggest at
> least considering other options. With the caveat that I am not a
> literature scholar in any way, here's a brief overview of some.
> Using <caesura>
> ----- ---------
> The verse base tag set provides an element for caesuras (same section
> as above), which if I understand correctly is the pause between two
> half-lines of verse (primarily in old English). But if what you're
> dealing with isn't truly a caesura, then this would not be a good
Unfortunately your assumption is right: it isn't really a caesura, i.e.
there's no (metric) pause between the two half-lines.
> Using part= on <l>
> ----- ----- -- ---
> Especially if your two hemistichs are separated because they are in
> different voices or spoken by different characters in a drama, it
> might make sense to divide the <l> element.
This also doesn't seem to apply.
> Syntactic Sugar
> --------- -----
> If you're really going to encode two <seg type=hemistich>s in each
> and every <l>, there is some advantage to creating a new element
> (<hemistich> or <hs>) just to make it easier on you. This would also
> allow you to redefine the <l> element so that it would enforce the
> two-hemistich-children rule:
> <!ELEMENT l ( (%m.Incl;)*, hs, (%m.Incl;)*, hs, (%m.Incl;)* ) >
> Thus encoders using structured editors would not be permitted to put
> anything other than 2 <hs> elements (perhaps with interspersed globally
> available elements like <pb>), and a good editor would even insert
> them for you. And in any case validation would catch those <l>
> elements that did not conform.
> If you need help making such extensions to the TEI DTDs feel free to
> ask here, but preferably on a different thread.
I see you've expanded on this one, so i'll comment about it elsewhere in
>>> Why do you have "hemistichA" and "hemistichB"? Is order of
>>> occurence within the <l> insufficient?
>>Unfortunately, it is: a single germanic verse can be split in two
>>hemistichs, or half-verses, which are tied by alliteration. The
>>latter follows different rules in h. A vs. B, which means that if I
>>want to perform searches relating to alliteration I'd have better
>>to distinguish between the two. Furthermore, it could be
>>interesting to investigate formulas as they occur in h. A and B.
> I may be being dense here, but I still am not sure why it is so much
> easier to distinguish between the first and second hemistichs of a
> line in
> <hsA>The first hemistich</hsA>
> <hsB>came out to play,</hsB>
> <hsA>Upon the world-wide</hsA>
> <hsB>web one day.</hsB>
> than in
> <hs>She had such</hs>
> <hs>enormous fun,</hs>
> <hs>She called for another</hs>
> <hs>hemistich to come.</hs>
> Yes, the latter must require an extra step (probably of Xpath
> expression in your style-sheet -- can some XSLTer verify?), but it
> still shouldn't be that hard.
Don't worry, it's not you being dense :) it's my limited knowledge of
XSLT and its capabilities that made me assume it's better to explicitly
mark the first and the second half-line. Actually I don't need to
differentiate them because of style-sheet/HTML production reasons, but
to perform separate searches in the first and second half-line: see D.
O'Donnel second message to know why this is necessary for metrical
analysis of OE metre.
Many thanks for your comments.
Roberto Rosselli Del Turco e-mail: [log in to unmask]
Dipartimento di Scienze [log in to unmask]
del Linguaggio Then spoke the thunder DA
Universita' di Torino Datta: what have we given? (TSE)
Hige sceal the heardra, heorte the cenre,
mod sceal the mare, the ure maegen litlath. (Maldon 312-3)