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
Many CHIs use either <p>content</p> or <p><emph>content</emph></p> in elements like <bioghist> and <scopecontent>. Some, however, use mixed content, such as
<p>Content <emph>more content</emph> and then some more.</p>
If we mark both /p/ and /p/emph/ as 'include', we end up with a list with the content of <emph> first. If we only mark /p/ as 'include', the content of <emph> is lost.
The parser should support this mixed content and transform elements to what we want when it encounters them. (The ugly solution is to convert mixed content to Markdown equivalents before parsing, which is what I'll do for now.)
The text was updated successfully, but these errors were encountered:
Many CHIs use either
<p>content</p>
or<p><emph>content</emph></p>
in elements like<bioghist>
and<scopecontent>
. Some, however, use mixed content, such asIf we mark both
/p/
and/p/emph/
as 'include', we end up with a list with the content of<emph>
first. If we only mark/p/
as 'include', the content of<emph>
is lost.The parser should support this mixed content and transform elements to what we want when it encounters them. (The ugly solution is to convert mixed content to Markdown equivalents before parsing, which is what I'll do for now.)
The text was updated successfully, but these errors were encountered: