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
You have quite a number of verse lines that begin with in explicitly typed quotation mark, to represent direct speech continuing over multiple lines, even over multiple stanzas. Example:
<lg xml:id="kakavin_25.06" n="6">
<l n="a">nān liṅ saṅ nrəpaputra saṅ hyaṅ ikanaṅ kaḍatvan avarah</l>
<l n="b">“saṅkeṅ rājya vita ṅhulun munus avak pva tan kahuniṅan</l>
<l n="c">“de saṅ pāṇḍava tan rumakṣa saviśeṣa riṅ kadi kami</l>
<l n="d">“durnītiṅ karatun kəneṅ dyuta vikalpa tan tuhu viku</l>
</lg>
The absence of semantic tagging for direct speech is non compliant with TEI.
When Axelle and I were writing EGC, this subject did not come up in a significant way, so we only have a somewhat basic suggestion in EGC 3.5.2, without any example. Then in 8.3.2 we also offer <q> but without stoppinbg to cinsider your kind of scenario where quoted direct speech extends across block boundaries.
I hope @michaelnmmeyer can advise us on how to encode your kind of scenario and then help you implement it in your edition in an automated fashion.
The text was updated successfully, but these errors were encountered:
@andreaacri —
You have quite a number of verse lines that begin with in explicitly typed quotation mark, to represent direct speech continuing over multiple lines, even over multiple stanzas. Example:
The absence of semantic tagging for direct speech is non compliant with TEI.
When Axelle and I were writing EGC, this subject did not come up in a significant way, so we only have a somewhat basic suggestion in EGC 3.5.2, without any example. Then in 8.3.2 we also offer
<q>
but without stoppinbg to cinsider your kind of scenario where quoted direct speech extends across block boundaries.I hope @michaelnmmeyer can advise us on how to encode your kind of scenario and then help you implement it in your edition in an automated fashion.
The text was updated successfully, but these errors were encountered: