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
Presently, if there is a <choice><unclear>abcd</unclear><unclear>dgef</unclear></choice>, both options underline, as though the individual letters were unclear. It would be good to ensure that when the child of does not display with an underline. However, if is the grandchild of , then it SHOULD display.
See, for example, line four of caes0004 and line four of idum0001.
To be honest, I think this is something that should be changed in the next version of EpiDoc, as we are presently unable to nest within an . This is frustrating because the uncertain choice is often because of unclear letters. My suggestion is that rather than having an uncertain choice be indicated by <choice><unclear>, that it be encoded with an entirely different attribute that serves only that purpose (e.g., <indeterminate>). Multi-purpose attributes can create problems, as in this case.
The text was updated successfully, but these errors were encountered:
Presently, if there is a
<choice><unclear>abcd</unclear><unclear>dgef</unclear></choice>
, both options underline, as though the individual letters were unclear. It would be good to ensure that when the child of does not display with an underline. However, if is the grandchild of , then it SHOULD display.See, for example, line four of caes0004 and line four of idum0001.
To be honest, I think this is something that should be changed in the next version of EpiDoc, as we are presently unable to nest within an . This is frustrating because the uncertain choice is often because of unclear letters. My suggestion is that rather than having an uncertain choice be indicated by
<choice><unclear>
, that it be encoded with an entirely different attribute that serves only that purpose (e.g.,<indeterminate>
). Multi-purpose attributes can create problems, as in this case.The text was updated successfully, but these errors were encountered: