Hi,
Anton Lindqvist wrote on Mon, Jan 09, 2017 at 09:02:37AM +0100:
> The following paragraph from the SHA1(3) man-page looks odd in its HTML
> representation:
>
> $ sed -n 214p /usr/src/lib/libcrypto/man/SHA1.3
> .Pq Fa len No bytes at Fa data .
>
> The No macro causes "bytes at" to be wrapped inside a code-tag and not
> be rendered as unformatted text.
Wait, that's an outright bug in the mandoc(1) HTML formatter:
schwarze@isnote $ echo .Em italic , Sy bold , No and roman | \
> mandoc -mdoc -Thtml -Ofragment
[...]
<span class="emph">italic</span>, <span class="symb">bold</span>,
<code class="none">and roman</code><table class="foot">
Whereas the mdoc manual very clearly says:
No
Normal text. Closes the scope of any preceding in-line macro.
When used after physical formatting macros like Em or Sy,
switches back to the standard font face and weight.
Can also be used to embed plain text strings in macro lines
using semantic annotation macros.
Examples:
.Em italic , Sy bold , No and roman
> Splitting the line solves the problem:
It seems a matter of taste whether you prefer the more compact
form or the more verbose five-line form, but it shouldn't make
a difference for the markup produced.
Yours,
Ingo
> Index: SHA1.3
> ===================================================================
> RCS file: /cvs/src/lib/libcrypto/man/SHA1.3,v
> retrieving revision 1.4
> diff -u -p -r1.4 SHA1.3
> --- SHA1.3 2 Dec 2016 19:28:41 -0000 1.4
> +++ SHA1.3 8 Jan 2017 19:31:13 -0000
> @@ -211,7 +211,11 @@ structure.
> .Pp
> .Fn SHA1_Update
> can be called repeatedly with chunks of the message to be hashed
> -.Pq Fa len No bytes at Fa data .
> +.Po
> +.Fa len
> +bytes at
> +.Fa data
> +.Pc
> .Pp
> .Fn SHA1_Final
> places the message digest in
