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
{{ message }}
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
when the <orig> element appears alone, and not as a child of <choice> the content should be ignored. Characters inside that type of <orig> are not words. They represent something that is not recognizable as a word.
Examples:
masa0836 has the string <orig>CB</orig> this appears in the word list
same in masa0838
caes0062 has the string <orig>C</orig> and <orig>DO</orig> seems to not be in the list
The text was updated successfully, but these errors were encountered:
yes, the xml:ids help with context for parsing (so orig not useful) and
also for creating kwic views, where the orig will be useful.orig not
useful) and also for creating kwic views, where the orig will be useful.
If it's in the segmented div, it should have an xml:id. orig doesn't have
an xml:lang, and num probably should, so that will have to be copied as for
<w>
when the
<orig>
element appears alone, and not as a child of<choice>
the content should be ignored. Characters inside that type of<orig>
are not words. They represent something that is not recognizable as a word.Examples:
masa0836 has the string
<orig>CB</orig>
this appears in the word listsame in masa0838
caes0062 has the string
<orig>C</orig>
and<orig>DO</orig>
seems to not be in the listThe text was updated successfully, but these errors were encountered: