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
Unicode points that are used as the "equivalent" form of one of our glyph definitions should never appear in bare unicode strings in the source TEI; they should always be marked up as glyphs and use the "modern" mapping for their literal text content. That is, for every glyph definition, report any uses of the "unicode" mapping in TEI text content.
Eg. a text node containing "ſmall example" would be reported, since it should be marked up as <g ref="g_longS">s</g>mall example.
The text was updated successfully, but these errors were encountered:
Unicode points that are used as the "equivalent" form of one of our glyph definitions should never appear in bare unicode strings in the source TEI; they should always be marked up as glyphs and use the "modern" mapping for their literal text content. That is, for every glyph definition, report any uses of the "unicode" mapping in TEI text content.
Eg. a text node containing "ſmall example" would be reported, since it should be marked up as
<g ref="g_longS">s</g>mall example
.The text was updated successfully, but these errors were encountered: