Errors in man pages, here: setpgid.2.po: Inconsistent formatting

Errors in man pages, here: setpgid.2.po: Inconsistent formatting

[Helge Kreutzmann]

Dear manpages maintainers.
the manpage-l10n project maintains a large number of translations of
man pages both from a large variety of sources (including manpages) as
well for a large variety of target languages.

During their work translators notice different possible issues in the
original (english) man pages. Sometiems this is a straightforward
typo, sometimes a hard to read sentence, sometimes this is a convention
not held up and sometimes we simply do not understand the original.

We use several distributions as sources and update regularly (at
least every 2 month). This means we are fairly recent (some
distributions like archlinux also update frequently) but might miss
the latest upstream version once a while, so the error might be
already fixed. We apologize and ask you to close the issue immediately
if this should be the case, but given the huge volume of projects and
the very limited number of volunteers we are not able to double check
each and every issue.

Secondly we translators see the manpages in the neutral po format,
i.e. converted and harmonized, but not the original source (be it man,
groff, xml or other). So we cannot provide a true patch (where
possible), but only an approximation which you need to translate into
your source format.

Finally the issues I'm reporting have accumulated over time and are
not always discovered by me, so sometimes my description of the
problem my be a bit limited - do not hesitate to ask so we can clarify
them.

I'm now reporting the errors for your project. As requested, each
issue is sent in an unique mail for easier tracking on your side. If
future reports should use another channel, please let me know.

**

# FIXME: inconsistant formatting/markup (compared to previous entries)

"B<pid_t getpgrp(pid_t >I<pid>B<);\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ > /* BSD "
"version */"


-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software libre: http://www.ffii.de/

Re: Errors in man pages, here: setpgid.2.po: Inconsistent formatting

[Michael Kerrisk (man-pages)]

On 4/19/20 8:48 AM, Helge Kreutzmann wrote:
> Dear manpages maintainers.
> the manpage-l10n project maintains a large number of translations of
> man pages both from a large variety of sources (including manpages) as
> well for a large variety of target languages.
> 
> During their work translators notice different possible issues in the
> original (english) man pages. Sometiems this is a straightforward
> typo, sometimes a hard to read sentence, sometimes this is a convention
> not held up and sometimes we simply do not understand the original.
> 
> We use several distributions as sources and update regularly (at
> least every 2 month). This means we are fairly recent (some
> distributions like archlinux also update frequently) but might miss
> the latest upstream version once a while, so the error might be
> already fixed. We apologize and ask you to close the issue immediately
> if this should be the case, but given the huge volume of projects and
> the very limited number of volunteers we are not able to double check
> each and every issue.
> 
> Secondly we translators see the manpages in the neutral po format,
> i.e. converted and harmonized, but not the original source (be it man,
> groff, xml or other). So we cannot provide a true patch (where
> possible), but only an approximation which you need to translate into
> your source format.
> 
> Finally the issues I'm reporting have accumulated over time and are
> not always discovered by me, so sometimes my description of the
> problem my be a bit limited - do not hesitate to ask so we can clarify
> them.
> 
> I'm now reporting the errors for your project. As requested, each
> issue is sent in an unique mail for easier tracking on your side. If
> future reports should use another channel, please let me know.
> 
> **
> 
> # FIXME: inconsistant formatting/markup (compared to previous entries)
> 
> "B<pid_t getpgrp(pid_t >I<pid>B<);\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ > /* BSD "
> "version */"

I need more context here. I can't see the problem. (Maybe it
was already fixed upstream?)

Thanks,

Michael



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

Re: Errors in man pages, here: setpgid.2.po: Inconsistent formatting

[Jakub Wilk]

* Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>, 2020-04-20, 08:12:
>># FIXME: inconsistant formatting/markup (compared to previous entries)
>>
>>"B<pid_t getpgrp(pid_t >I<pid>B<);\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ > /* BSD "
>>"version */"
>
>I need more context here. I can't see the problem.

I think it's about comment indentation:
for the BSD functions, it's done with escaped spaces:

   .BI "pid_t getpgrp(pid_t " pid ");\ \ \ \ \ \ \ \ \ \ \ "
   /* BSD version */

whereas for the other functions, plain spaces are used:

   .BR "pid_t getpgrp(void);" "                 /* POSIX.1 version */"

While we can't just remove backslashes, we could do something like this:

   .BI "pid_t getpgrp(pid_t " pid ");\fR            /* BSD version */"

This is more readable IMO, and should make translators happy. :)

-- 
Jakub Wilk

Re: Errors in man pages, here: setpgid.2.po: Inconsistent formatting

[Michael Kerrisk (man-pages)]

Hello Jakub,

On Tue, 21 Apr 2020 at 10:34, Jakub Wilk <jwilk@jwilk.net> wrote:
>
> * Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>, 2020-04-20, 08:12:
> >># FIXME: inconsistant formatting/markup (compared to previous entries)
> >>
> >>"B<pid_t getpgrp(pid_t >I<pid>B<);\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ > /* BSD "
> >>"version */"
> >
> >I need more context here. I can't see the problem.
>
> I think it's about comment indentation:
> for the BSD functions, it's done with escaped spaces:
>
>    .BI "pid_t getpgrp(pid_t " pid ");\ \ \ \ \ \ \ \ \ \ \ "
>    /* BSD version */
>
> whereas for the other functions, plain spaces are used:
>
>    .BR "pid_t getpgrp(void);" "                 /* POSIX.1 version */"

D'oh! What idiot formatted things like tha... ohhhh....

> While we can't just remove backslashes, we could do something like this:
>
>    .BI "pid_t getpgrp(pid_t " pid ");\fR            /* BSD version */"
>
> This is more readable IMO, and should make translators happy. :)

Agreed. Changed as you suggest.

Thanks,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/