Where one or more witnesses have a gap or a nonsense reading that could be disambiguated as more than one substantive reading, this situation should be encoded in a TEI-friendly way. The TEI Guidelines (https://www.tei-c.org/release/doc/tei-p5-doc/en/html/TC.html#TCAPWD) describe a witDetail element parallel to lem and rdg elements that would be suitable for this purpose: the element includes a wit attribute (for one or more witnesses described by its detail) and a target attribute (which can point to one or more readings that might disambiguate it). For example:
While the pointers in the wit and target attributes should technically point to unique elements (which, within the XML collation document, would be xml:id values prefixed by the # character), in practice, we may assume the pointers to refer to n values (for witnesses or readings within the same app element) if they do not start with the # prefix. (This is especially convenient for New Testament textual critics, who use Gregory-Aland numbers to refer to manuscripts; XML guidelines prohibit xml:ids that begin with numbers.) So the following should also be supported (even if it is not strictly valid TEI):
In addition, per the TEI guidelines: "without a target attribute, [witDetail] refers to the closest preceding lem or rdg." So if a witDetail element has no target attribute, then its target should be set to the last lem or rdg element by default.
All right, I have this feature implemented in tei_collation_converter.py, and it is working as expected with witDetail elements in the example XML file. I will now close this issue.
Where one or more witnesses have a gap or a nonsense reading that could be disambiguated as more than one substantive reading, this situation should be encoded in a TEI-friendly way. The TEI Guidelines (https://www.tei-c.org/release/doc/tei-p5-doc/en/html/TC.html#TCAPWD) describe a
witDetail
element parallel tolem
andrdg
elements that would be suitable for this purpose: the element includes awit
attribute (for one or more witnesses described by its detail) and atarget
attribute (which can point to one or more readings that might disambiguate it). For example:While the pointers in the
wit
andtarget
attributes should technically point to unique elements (which, within the XML collation document, would bexml:id
values prefixed by the#
character), in practice, we may assume the pointers to refer ton
values (for witnesses or readings within the sameapp
element) if they do not start with the#
prefix. (This is especially convenient for New Testament textual critics, who use Gregory-Aland numbers to refer to manuscripts; XML guidelines prohibitxml:id
s that begin with numbers.) So the following should also be supported (even if it is not strictly valid TEI):