From: Helge Kreutzmann <debian@helgefjell.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Errors in NFS man pages
Date: Wed, 15 Sep 2021 20:37:48 +0200 [thread overview]
Message-ID: <20210915183748.GA26324@Debian-50-lenny-64-minimal> (raw)
In-Reply-To: <20210915183321.GA10712@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 2856 bytes --]
Hello Bruce,
On Wed, Sep 15, 2021 at 02:33:21PM -0400, J. Bruce Fields wrote:
> On Sun, Sep 12, 2021 at 08:07:46AM +0200, Helge Kreutzmann wrote:
> > Dear NFS maintainer,
> > the manpage-l10n project maintains a large number of translations of
> > man pages both from a large variety of sources (including NFS) 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. I'm not repeating the
> > errors reported 2020-05-16, 2021-05-29, if you would like a full
> > report, please let me know. If future reports should use another
> > channel, please let me know as well.
>
> This is probably fine.
>
> But if it's possible to make these into patches against nfs-utils
> (http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=summary), and send
> them to steved@redhat.com, cc'd to this list--that would probably get
> the fastest response.
Sorry, given more than > 100 upstreams and very limited man power this
is not possible. I would be really glad if you could handle them, even
if this takes more time (better late than never).
Thanks for taking care!
Greetings
Helge
--
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 --]
next prev parent reply other threads:[~2021-09-15 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 6:07 Errors in NFS man pages Helge Kreutzmann
2021-09-15 18:33 ` J. Bruce Fields
2021-09-15 18:37 ` Helge Kreutzmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-29 10:55 Errors in nfs " Helge Kreutzmann
2020-05-16 15:50 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=20210915183748.GA26324@Debian-50-lenny-64-minimal \
--to=debian@helgefjell.de \
--cc=bfields@fieldses.org \
--cc=linux-nfs@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).