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
we find <g> interrupting words. Is any special measure required to ensure indexability of such words, or can Michaël's machine be taught to ignore any <g> altogether?
On the encoding side, what you have done is sufficient, but there's the option of flagging it as <orig>, which I would recommend, and for the second item, also the option of normalising it, which I would also recommend.
The applicable EGD bits are at the end of §4.2.1 (before the example with paṁcaviṁśati<choice><orig>|n</orig><reg>M|</reg></choice> tat-putro). The situation is also essentially the same as with space in your <l n="a">jayatīndrādidevāsya<space/>ś</l><l n="b">śrīmān yajñapatīśvaraḥ</l>, which is in EGD §4.3.3, though flagging/normalisation is not mentioned there (though perhaps it should; I've made a note of that for myself).
The EGD does not specifically address cases like this in verse, but here is one from my VengiCalukya0078:
@danbalogh @michaelnmmeyer —
in cases like
or
(both examples taken from DHARMA_INSCIC00141 — https://dharmalekha.info/texts/INSCIC00141)
we find
<g>
interrupting words. Is any special measure required to ensure indexability of such words, or can Michaël's machine be taught to ignore any<g>
altogether?does EGD address such cases at all, Dan?
(cc to @salomepichon and @chhomkunthea for their information)
The text was updated successfully, but these errors were encountered: