diff options
author | 2014-08-14 00:31:43 +0000 | |
---|---|---|
committer | 2014-08-14 00:31:43 +0000 | |
commit | 3b9ecd40b6ed9cef16a4ce87cfc12713cd7c97e9 (patch) | |
tree | d639fc4ebeb49b6248f31790a827858216e0562b /st.in | |
parent | 438eebf7ec01fbc8167f69287d4b4ab43d49e8d8 (diff) | |
download | mandoc-3b9ecd40b6ed9cef16a4ce87cfc12713cd7c97e9.tar.gz mandoc-3b9ecd40b6ed9cef16a4ce87cfc12713cd7c97e9.tar.zst mandoc-3b9ecd40b6ed9cef16a4ce87cfc12713cd7c97e9.zip |
Revert previous, as requested by kristaps@.
The .Bf block can contain subblocks, so it has to render as an
element that can contain flow content. But <em> cannot contain
flow content, only phrasing content. Rendering .Em and .Bf differently
would by unfortunate, and closing out .Bf before subblocks and
re-opening it afterwards would merely complicate both the C code
of the program and the generated HTML code. Besides, converting
.Em to semantic HTML markup would require some content to be put
into <em> and some into <i>, but we cannot automatically distinguish
which is which, so strictly speaking, we can't use semantic HTML
here but have to fall back to physical markup. Wonders of HTML...
Diffstat (limited to 'st.in')
0 files changed, 0 insertions, 0 deletions