-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
From @hcayless
<expan><abbr>d</abbr><ex>uum</ex><abbr>v</abbr></expan><expan><ex>irum</ex></expan><lb/>is a line beginning, so the first one should be at the start of the first line.- I wouldn't wrap
<gap/>s in<w>, because we don't know what was in them. To be honest, I probably wouldn't use<w>at all, or only in cases where it might be ambiguous whether something was a word or not.
<expan><abbr>d</abbr><ex>uum</ex><abbr>v</abbr></expan><expan><ex>irum</ex></expan>should be
<expan><abbr>d</abbr><ex>uum</ex><abbr>v</abbr><ex>irum</ex></expan>ae<supplied reason="lost"><expan><abbr>d</abbr><ex>ilem</ex></expan></supplied>should be
<expan><abbr>ae<supplied reason="lost">d</supplied></abbr><ex>ilem</ex></expan>o<supplied reason="lost">ro</supplied></w> <w n="6"><supplied
reason="lost"><expan><abbr>v</abbr><ex>os</ex></expan></supplied></w>
<w n="7"><expan><abbr>[f</abbr><ex
cert="low">aciatis</ex><abbr>]</abbr></expan>should be
o<supplied reason="lost">ro
<expan><abbr>v</abbr><ex>os</ex></expan><expan><abbr>f</abbr><ex
cert="low">aciatis</ex></expan></supplied>The latter highlights a reason maybe not to do <w>, because things like <supplied> can run across words. If you really want to mark words, you'll need to bridge the gaps in the sliced up with @prev/@next.
Metadata
Metadata
Assignees
Labels
No labels