Closed cfhaak closed 1 month ago
on the other hand, this means cluttering the files … if at least the apps had ids, my possibilities might be better. I could just prevent any processing by using a barricade like:
<xsl:template match="tei:w/tei:app/tei:rdg"/>
<xsl:template match="tei:app/tei:rdg[ancestor::tei:app//tei:lem/tei:w and not(ancestor::tei:w)]"/>
<xsl:template match="tei:app/tei:rdg[not(ancestor::tei:app//tei:lem/tei:w) and not(ancestor::tei:w)]"/>
then I could process the isolated the lemmas as anchors, and create anchors for the cases where no w can be used to get an id …
seems no longer necessary
as stated here the xml is too inconsistent and complicated to just handle it with xslt. So tackle the whole app by a) linking app and relation beforehand b) create an extra div, containing the linked variants only, which then can be processed in an orderly manner