From: Helge Kreutzmann <debian@helgefjell.de>
To: "\"Kai Mäkisara (Kolumbus)\"" <kai.makisara@kolumbus.fi>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>,
"Mario Blättermann" <mario.blaettermann@gmail.com>
Subject: Re: Errors in man pages, here: st(4): Content
Date: Sat, 25 Apr 2020 12:15:51 +0200 [thread overview]
Message-ID: <20200425101551.GA22709@Debian-50-lenny-64-minimal> (raw)
In-Reply-To: <168DA6F5-D54B-48E4-A8E1-3FF081ABE6BC@kolumbus.fi>
[-- Attachment #1: Type: text/plain, Size: 2610 bytes --]
Hello Kai,
On Mon, Apr 20, 2020 at 09:51:11PM +0300, "Kai Mäkisara (Kolumbus)" wrote:
> > On 20. Apr 2020, at 21.29, Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> wrote:
> > On Mon, 20 Apr 2020 at 17:51, "Kai Mäkisara (Kolumbus)"
> > <kai.makisara@kolumbus.fi> wrote:
> >>> On 20. Apr 2020, at 11.13, Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> wrote:
> >>>
> >>> [CC += Kai]
> >>>
> >>> (Kai, I got a pile of queries from a downstream translation project)
> >>>
> >>> On 4/19/20 8:48 AM, Helge Kreutzmann wrote:
> >>>> Dear manpages maintainers.
> >>>>
> >> ...
> >>>> We cannot understand the last sentence. What is "forward spacing"?
> >>>>
> >>>> "This option causes the B<MTEOM> operation to be sent directly to the drive, "
> >>>> "potentially speeding up the operation but causing the driver to lose track "
> >>>> "of the current file number normally returned by the B<MTIOCGET> request. If "
> >>>> "B<MT_ST_FAST_EOM> is false, the driver will respond to an B<MTEOM> request "
> >>>> "by forward spacing over files."
> >>>
> >>> Perhaps Kai can help. I do not have a good explanation.
> >>>
> >> Spacing in tape terminology means going to the next file (or record or set mark).
> >> The drives usually support a command to go to the end of the tape. The
> >> drawback is that no information is obtained about the number of files skipped.
> >> If the driver spaces forward over files one by one, it can count how many
> >> files have been skipped.
> >>
> >> This is the technical description. But the text also says what is the consequence
> >> for a user that does not care about technology. Spacing is mentions also
> >> earlier in the text.
> >
> > So, no text changes needed here, right?
> >
> I don’t think changes are needed. But the discussion in my other answer applies
> also here.
Thanks for the explanation. I added a note in the translation file,
updated the translation accordingly and put the current translator in
charge in CC so he is aware of this discussion.
So for my side this issue can be closed.
Greetings
Helge
P.S. For this issue I tried to search for the term "space over" but
did not find the right pages, including Wikipedia (but I might
have missed the right search keys).
--
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:[~2020-04-25 10:15 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: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 [this message]
2020-04-19 6:48 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)
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=20200425101551.GA22709@Debian-50-lenny-64-minimal \
--to=debian@helgefjell.de \
--cc=kai.makisara@kolumbus.fi \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.com \
--cc=mtk.manpages@gmail.com \
/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).