Closed cfhaak closed 3 weeks ago
where should i render them? bottom isn't bad but then image reloading is triggered every time … but its prob the easiest solution, so ill try that first
There are different sorts of variants. Some need to be described, some can be rendered in a conservative way. Annoying:
<w xml:id="tu_132_xTok_000387" pos="NN" join="right" lemma="Ruhestörer" ana="#fs_tu_132_xTok_000387">
Ru
<lb break="no" edRef="#wb1" rend="d"/>
<app>
<lem wit="#wb1">
<fw type="catch">hestöh=</fw>
</lem>
</app>
<pb edRef="#wb1" facs="17940910_Gilofski_d_wb1.jp2" type="primary"/>
hestöhrer
</w>
better:
<w xml:id="tu_132_xTok_000152" pos="VVINF" lemma="stören" ana="#fs_tu_132_xTok_000152">
<app>
<lem wit="#wb1">stören</lem>
<rdg wit="#wb2">stöhren</rdg>
</app>
</w>
stören] wb2: stöhren (and then links to 1. the text segment, 2. the witness with the variant in the metadata, 3. the image containing the variant)
while the pb-vars with catches are really annoying, this example seems to be faulty …
tricky: linebreaks inside the variants app-elements only covering parts of the w-element textnodes sic/corr inside app
edgecases:
[x] pb variants
[x] catches (will need a semantic description, eg. "wb2: [Kustode: "hestöh=")
should be rendered as appartus link from text to app and reverse
link from variant shorthand of witness to the witness in the metadata section