This option makes me feel decidedly queasy. If you want to mark up the
page breaks inside the sequence of end notes, then you are interested in
the physical organization of the text, primarily, and you are just
making life needlessly complicated by putting the <note> elements
inline. There's no rule that says they *have* to be in line. Au
contraire, you should put them where processing them is going to be
least work. What's wrong with putting them in a div of their own and
pointing to them from the text, with <ptr/> (or <ref> if you care about
how the referencing is done)?
I don't want to be the one who tells Sebastian (or equivalent) to hack
his <pb/> handling stylesheets so that they do something special with
<pb/>s which happen to occur inside a <note type="foot"/> when the moon
is full and there's an R in the month....
James Cummings wrote:
>Greg Murray wrote:
>>That's reasonable, but you should consider leaving the page breaks in
>>the note elements and making your conversion script/stylesheet smart
>>enough simply to ignore <pb> when it occurs in <note>. If that's not an
>>option, then at least comment out the page breaks rather than deleting
>>them. At some future time you (or someone else) may want to change your
>>decision about how to handle this problem.
>I'd second this. Matching <pb> inside <note> is simple, especially if
>you just want to ignore them. Something (untested) like:
><xsl:template match="tei:note//tei:pb" />
>Should do it if you are using XSLT anywhere in the processing chain.
>Dr James Cummings, Oxford Text Archive, University of Oxford