Re: Issue in man page mount_namespaces.7

["G. Branden Robinson" <g.branden.robinson@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]

Hi Helge,

At 2023-01-22T21:01:33+0100, Helge Kreutzmann wrote:
> This is the represenation we see (like B<> for bold, I<> for italics).
> It most likely does not look like this in groff.

Thanks for the quick follow up.  I wondered about this but since I
didn't see "\n" in any of your other reports, I thought that you thought
this character sequence was appearing literally in the man page sources.

> > 1ae6b2c7b8 (Alejandro Colomar   2022-03-18 20:25:09 +0100 1016) .I util\-linux
> > b324e17d32 (Alejandro Colomar   2022-12-04 20:38:06 +0100 1017)  2.27) in turn reverses the step performed by
> 
> At this point I see a hard line break as well when I read the english 
> page in man.

Yes!  This is a good catch.  Beginning a text line with space characters
forces a break (a new output line) in *roff.  That is clearly a mistake
and should be corrected.

+1 for sure.

> > That is why I suspect a problem with your tool.
> 
> I can mark it as such, i.e. a po4a problem.

Since so much of a report is automatically generated, perhaps a glossary
would be helpful.  Your reporting dialect seems to be drawn from
Perl::Pod, but I'm not clear on whether it's a _strict_ subset or if you
have your own conventions as well.

Something like:

B<foo>		foo is in boldface
I<bar>		bar is in italics or an oblique face
\n		indicates each break when breaking is surprising

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]