From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
"Kai Mäkisara" <kai.makisara@kolumbus.fi>
Subject: Re: Errors in man pages, here: st(4): Content
Date: Mon, 20 Apr 2020 10:11:03 +0200 [thread overview]
Message-ID: <532e2c98-09ca-ee0c-be4b-0c51d4b42eef@gmail.com> (raw)
In-Reply-To: <20200419064828.GA32141@Debian-50-lenny-64-minimal>
[CC += Kai]
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.
>
> **
>
> Is the statement true or is it swapped (locked when closed)?
>
> "When this option is true, the drive door is locked when the device is opened "
> "and unlocked when it is closed."
I do not know. Perhaps Kai can help.
Kai, the text in question is
MT_ST_AUTO_LOCK (Default: false)
When this option is true, the drive door is locked
when the device is opened and unlocked when it is
closed.
I believe Helge asks whether the text should read:
MT_ST_AUTO_LOCK (Default: false)
When this option is true, the drive door is locked
when the device is CLOSED and unlocked when it is
OPEN.
Can you help?
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-04-20 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 6:48 Errors in man pages, here: st(4): Content Helge Kreutzmann
2020-04-20 8:11 ` Michael Kerrisk (man-pages) [this message]
2020-04-20 15:42 ` "Kai Mäkisara (Kolumbus)"
2020-04-20 18:28 ` Michael Kerrisk (man-pages)
-- strict thread matches above, loose matches on Subject: below --
2020-04-19 6:48 Helge Kreutzmann
2020-04-20 8:13 ` Michael Kerrisk (man-pages)
2020-04-20 15:51 ` "Kai Mäkisara (Kolumbus)"
2020-04-20 18:29 ` Michael Kerrisk (man-pages)
2020-04-20 18:51 ` "Kai Mäkisara (Kolumbus)"
2020-04-25 10:15 ` 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=532e2c98-09ca-ee0c-be4b-0c51d4b42eef@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=kai.makisara@kolumbus.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.