linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>
Subject: Re: Errors in man pages, here: shmop.2
Date: Wed, 18 Aug 2021 00:20:01 +0200	[thread overview]
Message-ID: <144bc32d-4519-918d-b41e-895275baa754@gmail.com> (raw)
In-Reply-To: <20210817135116.GD12220@Debian-50-lenny-64-minimal>

Hello Helge,

On 8/17/21 3:51 PM, Helge Kreutzmann wrote:
> Hello Michael,
> On Mon, Jul 26, 2021 at 01:02:10AM +0200, Michael Kerrisk (man-pages) wrote:
>>> Man page: shmop.2
>>> Issue: file → files
>>>
>>> "The following header file is included by the \"reader\" and \"writer\" "
>>> "programs."
>>
>> The existing text looks correct to me. Please let me know further
>> details if you still think there's a problem after reviewing.
> 
> Probably we do not understand the sentence correctly, so bear with me.
> Currently, the man page reads as follows:
> 
>    Program source: svshm_string.h
>        The following header file is included by the "reader" and "writer" programs.
> 
>            #include <sys/types.h>
>            #include <sys/ipc.h>
>            #include <sys/shm.h>
>            #include <sys/sem.h>
>            #include <stdio.h>
>            #include <stdlib.h>
>            #include <string.h>
> 
>            #define errExit(msg)    do { perror(msg); exit(EXIT_FAILURE); \
>                                    } while (0)
> 
> The sentence in question seems to refer to the next paragraph, i.e.
> the beginning of the program source. There 7 header files (from
> types.h up to string.h) are mentioned. In the translation we also
> replaced the full stop by a colon. Since there are 7 header files, we
> assume that it needs to be plural.
> 
> Now explaining this and reading it again, I think I understand the
> sentence now (better). The header file is "svshm_string.h" and thus
> singular. So logically (but it does not work in the overall formatting
> of the man page), the first two lines above would need to be read in a
> different order. 
> 
>        The following header file is included by the "reader" and "writer" programs.
>    Program source: svshm_string.h
> 
> If this interpetation is correct, maybe the following change could be
> made:
> 
>    Program source: svshm_string.h
>        This header file is included by the "reader" and "writer" programs:
>        ~~~~~~~~~~                                                       ~~
> 
> Once I've your confirmation, I'll align the translation.

Thanks for the clarification. I have applied the following patch.

Cheers,

Michael

diff --git a/man2/shmop.2 b/man2/shmop.2
index c9bd92986..2cc49933c 100644
--- a/man2/shmop.2
+++ b/man2/shmop.2
@@ -324,10 +324,14 @@ Hello, world
 .in
 .\"
 .SS Program source: svshm_string.h
-The following header file is included by the "reader" and "writer" programs.
+The following header file is included by the "reader" and "writer" programs:
 .PP
 .in +4n
 .EX
+/* svshm_string.h
+
+   Licensed under GNU General Public License v2 or later.
+*/
 #include <sys/types.h>
 #include <sys/ipc.h>
 #include <sys/shm.h>

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

  reply	other threads:[~2021-08-17 22:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-25 17:09 Errors in man pages, here: shmop.2 Helge Kreutzmann
2021-07-25 23:02 ` Michael Kerrisk (man-pages)
2021-07-26  6:44   ` Jakub Wilk
2021-08-10  1:48     ` Michael Kerrisk (man-pages)
2021-08-17 13:51   ` Helge Kreutzmann
2021-08-17 22:20     ` Michael Kerrisk (man-pages) [this message]
2021-08-18  6:55       ` Helge Kreutzmann
  -- strict thread matches above, loose matches on Subject: below --
2021-07-25 17:09 Helge Kreutzmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=144bc32d-4519-918d-b41e-895275baa754@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).