In the entry for ἅγιος, e.g., in the original style using @n:
<entry n="ἅγιος|G40|G39">
In the 'lemma' file, the first Strong's number stays with the headword in the @lemma attribute, while only the second Strong's number is moved to the @strong attribute:
<entry lemma="ἅγιος|G40" strong="G39">
Would the answer be to to have all Strong's numbers in the @strong attribute, separated by |?
Once we decide how to handle these cases, I may be able to implement a way to derive the @lemma form of the dictionary (which cannot validate against our schema) from the @n form of the text, thus avoiding the possibility of content differences between the two.
In the entry for ἅγιος, e.g., in the original style using
@n:In the 'lemma' file, the first Strong's number stays with the headword in the
@lemmaattribute, while only the second Strong's number is moved to the@strongattribute:Would the answer be to to have all Strong's numbers in the @strong attribute, separated by
|?Once we decide how to handle these cases, I may be able to implement a way to derive the
@lemmaform of the dictionary (which cannot validate against our schema) from the@nform of the text, thus avoiding the possibility of content differences between the two.