[Top][All Lists]

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

bug#43107: closed (Errors in man pages)

From: GNU bug Tracking System
Subject: bug#43107: closed (Errors in man pages)
Date: Mon, 31 Aug 2020 23:15:01 +0000

Your message dated Mon, 31 Aug 2020 16:14:17 -0700
with message-id <9d608b5f-04c5-a6dc-2936-5edd7efaa01e@cs.ucla.edu>
and subject line Re: bug#43107: Errors in man pages
has caused the debbugs.gnu.org bug report #43107,
regarding Errors in man pages
to be marked as done.

(If you believe you have received this mail in error, please contact

43107: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=43107
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: Errors in man pages Date: Sun, 30 Aug 2020 07:39:36 +0200 User-agent: Mutt/1.10.1 (2018-07-13)
Dear gzip maintainer,
the manpage-l10n project maintains a large number of translations of
man pages both from a large variety of sources (including gzip) as
well for a large variety of target languages.

During their work translators notice different possible issues in the
original (english) man pages. Sometimes 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

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 in 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 convert 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

I'm now reporting the errors for your project. If future reports
should use another channel, please let me know.

Man page: gzip.1
Issue: Wrong order of entries

"znew(1), zcmp(1), zmore(1), zforce(1), gzexe(1), zip(1), unzip(1), "
Man page: zgrep.1
Issue: Wrong markup of command names, i.e. I<> instead of the proper B<>

"I<Zgrep> invokes I<grep> on compressed or gzipped files.  All options "
"specified are passed directly to I<grep>.  If no file is specified, then the "
"standard input is decompressed if necessary and fed to grep.  Otherwise the "
"given files are uncompressed if necessary and fed to I<grep>."

"If the GREP environment variable is set, I<zgrep> uses it as the I<grep> "
"program to be invoked."

"I<Zgrep> invokes I<grep> on compressed, xz'ed, lzma'ed, bzip2'ed or gzipped "
"files.  All options specified are passed directly to I<grep>.  If no file is "
"specified, then the standard input is decompressed if necessary and fed to "
"grep.  Otherwise the given files are uncompressed if necessary and fed to "

      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/

Attachment: signature.asc
Description: PGP signature

--- End Message ---
--- Begin Message --- Subject: Re: bug#43107: Errors in man pages Date: Mon, 31 Aug 2020 16:14:17 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
On 8/31/20 12:13 PM, Helge Kreutzmann wrote:
But, actually, personally I would not change it, I think the previous
order looks better.

OK, let's leave that alone then.

The remaining proposed changes are to use bold rather than italics for command names so I installed the attached to do that. Closing the bug report.

Attachment: 0001-doc-prefer-bold-to-italics-for-command-names.patch
Description: Text Data

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]