You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@wsalesky, this is not a bug to fix, so please don't change it just now even it if turns out to be a bug.
We are having trouble figuring out why the HTML for http://syriaca.org/place/78.html looks different from the XML (especially the dates).
Specifically, see this section in the HTML:
Christians (attested as early as 201, as late as 201) 1
Syriac (attested as early as 520, as late as 1624)
West Syrian (attested as early as 520, as late as 1624)
Melkite (attested as early as 522, as late as 540, as late as 540)
Syrian Orthodox (attested as early as 520, as late as 1624) 1
Latin (no attestations yet recorded) 1
Jews (no attestations yet recorded) 11
Muslims (no attestations yet recorded) 1
Lastly, the reason we found this issue is that we are wondering how the HTML handles having two TEI:precision elements as children of TEI:state. But perhaps the answer is that it is not?
Thanks!
The text was updated successfully, but these errors were encountered:
@davidamichelson The confessions HTML output is pretty knarly. The XSLT looks for a t:event[@type='attestation'] which references the confession via a t:link[@target="#CONFESSION-ID"], and then uses the date from the tei:event, not the dates in the t:state[@type="confession"]
So the data behind the first confession in place 78:
Christians (attested as early as 201, as late as 201)
@wsalesky, this is not a bug to fix, so please don't change it just now even it if turns out to be a bug.
We are having trouble figuring out why the HTML for http://syriaca.org/place/78.html looks different from the XML (especially the dates).
Specifically, see this section in the HTML:
This does not seem to have the same data for dates as found here: https://github.com/srophe/srophe-app-data/blob/master/data/places/tei/78.xml#L234-L253
Lastly, the reason we found this issue is that we are wondering how the HTML handles having two TEI:precision elements as children of TEI:state. But perhaps the answer is that it is not?
Thanks!
The text was updated successfully, but these errors were encountered: