public inbox for bzip2-devel@sourceware.org
 help / color / mirror / Atom feed
From: Helge Kreutzmann <debian@helgefjell.de>
To: bzip2-devel@sourceware.org
Subject: Errors in man pages
Date: Sun, 20 Dec 2020 10:20:19 +0100	[thread overview]
Message-ID: <20201220092019.GA21300@Debian-50-lenny-64-minimal> (raw)

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

Dear bzip2 maintainer,
the manpage-l10n project maintains a large number of translations of
man pages both from a large variety of sources (including bzip2) 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
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 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
them.

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

Man page: bzexe.1
Issue: ``bzexe /bin/cat'' → B<bzexe /bin/cat>

"The I<bzexe> utility allows you to compress executables in place and have "
"them automatically uncompress and execute when you run them (at a penalty in "
"performance).  For example if you execute ``bzexe /bin/cat'' it will create "
"the following two files:"
--
Man page: bzexe.1
Issue: File name markup missing, e.g. /bin/cat~ → I</bin/cat~>

"/bin/cat~ is the original file and /bin/cat is the self-uncompressing "
"executable file.  You can remove /bin/cat~ once you are sure that /bin/cat "
"works properly."

-- 
      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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2020-12-20  9:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20201220092019.GA21300@Debian-50-lenny-64-minimal \
    --to=debian@helgefjell.de \
    --cc=bzip2-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).