From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Kai Mäkisara (Kolumbus)" <kai.makisara@kolumbus.fi>
Cc: Helge Kreutzmann <debian@helgefjell.de>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: Errors in man pages, here: st(4): Content
Date: Mon, 20 Apr 2020 20:28:51 +0200 [thread overview]
Message-ID: <CAKgNAki5L+=G+HeMfxVcAjbSPtyKru1N_fC8r+rY09GAEpYL8w@mail.gmail.com> (raw)
In-Reply-To: <C47149A4-47DA-4E85-A9D0-E9A4229B58C4@kolumbus.fi>
Hello Kai,
On Mon, 20 Apr 2020 at 17:42, "Kai Mäkisara (Kolumbus)"
<kai.makisara@kolumbus.fi> wrote:
>
>
>
> > On 20. Apr 2020, at 11.11, Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> wrote:
> >
> > [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
> ...
> >
> > 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.
> >
> The orginal text is correct. This is section 4 man page meaning that it
> describes the programming interface, Opening the device means
> opening the device file, i.e., starting to use the device from the
> computer and the drive should be closed when the drive is operating.
> It can be opened when the device file is closed and the device is
> not in use.
>
> This might be clearer if the text would say “when the device file is
> opened”? I admit that the original text, while correct, may not be
> obvious to non-programmers.
Thanks. And I made your suggested wording change, which I think is
helpful to prevent misunderstandings.
Cheers,
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 18:29 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)
2020-04-20 15:42 ` "Kai Mäkisara (Kolumbus)"
2020-04-20 18:28 ` Michael Kerrisk (man-pages) [this message]
-- 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='CAKgNAki5L+=G+HeMfxVcAjbSPtyKru1N_fC8r+rY09GAEpYL8w@mail.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 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).