From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: Errors in man pages, here: dsp56k(4): Formatting
Date: Mon, 6 Jul 2020 12:06:36 +0200 [thread overview]
Message-ID: <CAKgNAkhHKEDTGQGfW+=MTKZR_uOf=2FR4mkRMX=m+xzht3mPyA@mail.gmail.com> (raw)
In-Reply-To: <fd828f05-acd5-c848-431b-5e12f4587da3@gmail.com>
Hello Helge,
On Mon, 20 Apr 2020 at 08:35, Michael Kerrisk (man-pages)
<mtk.manpages@gmail.com> wrote:
>
> On 4/19/20 8:47 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.
> >
> > **
> >
> > The formatting is inconsistent and incomplete:
> >
> > a) Formatting bold?
> >
> > msgid "#include E<lt>asm/dsp56k.hE<gt>\n"
> >
> >
> > b) In this string the formatting for dspk56k seems missing:
> > "The dsp56k device is a character device with major number 55 and minor "
> > "number 0."
> >
> >
> > c) No formatting, italic?
> > msgid "/dev/dsp56k"
Thanks for checking this!
Okay -- somewhere along the way I messed up. I had fixed (1) but not
(b) and (c). Fixed now.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-07-06 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 6:47 Errors in man pages, here: dsp56k(4): Formatting Helge Kreutzmann
2020-04-20 6:35 ` Michael Kerrisk (man-pages)
2020-07-05 19:34 ` Helge Kreutzmann
2020-07-06 10:06 ` Michael Kerrisk (man-pages) [this message]
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='CAKgNAkhHKEDTGQGfW+=MTKZR_uOf=2FR4mkRMX=m+xzht3mPyA@mail.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).