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
The use of the <unclear> tag in Demotic and Arabic texts is unproblematic in XML. When it is round tripped with xSugar to Leiden+ problems arise.
Instead of using underdots (which are obviously unacceptable in both language representations) we propose to the the unicode points U+2E22 and U+2E23.
Since walking from XML to Leiden+ is the challenge, the idea of some sort of preprocessing based on the parent xml:lang value of ar or egy-Egyd was floated.
In order to make entry easier there was also a proposal to think about adding a tab in the editor next to the UnderDot tag. It might be called Unclear Arabic Demotic or whatever is less clumsy and space taking.
The text was updated successfully, but these errors were encountered:
The use of the
<unclear>
tag in Demotic and Arabic texts is unproblematic in XML. When it is round tripped with xSugar to Leiden+ problems arise.Instead of using underdots (which are obviously unacceptable in both language representations) we propose to the the unicode points U+2E22 and U+2E23.
Since walking from XML to Leiden+ is the challenge, the idea of some sort of preprocessing based on the parent xml:lang value of ar or egy-Egyd was floated.
In order to make entry easier there was also a proposal to think about adding a tab in the editor next to the
UnderDot
tag. It might be calledUnclear Arabic Demotic
or whatever is less clumsy and space taking.The text was updated successfully, but these errors were encountered: