Re: Errors in man pages, here: getopt(3): Colloquialness

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.
> 
> **
> 
> use of we
> 
> "POSIX.1-2001, POSIX.1-2008, and POSIX.2, provided the environment variable "
> "B<POSIXLY_CORRECT> is set.  Otherwise, the elements of I<argv> aren't really "
> "I<const>, because we permute them.  We pretend they're I<const> in the "
> "prototype to be compatible with other systems."

POatched as below.

Thanks,

Michael

diff --git a/man3/getopt.3 b/man3/getopt.3
index eb840d045..9cedb05d5 100644
--- a/man3/getopt.3
+++ b/man3/getopt.3
@@ -350,10 +350,10 @@ provided the environment variable
 is set.
 Otherwise, the elements of \fIargv\fP aren't really
 .IR const ,
-because we permute them.
-We pretend they're
+because these functions permute them.
+Nevertheless,
 .I const
-in the prototype to be compatible with other systems.
+is used in the prototype to be compatible with other systems.
 .IP
 The use of \(aq+\(aq and \(aq\-\(aq in
 .I optstring



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



[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux