linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: ioctl_tty.2
Date: Mon, 26 Jul 2021 01:18:30 +0200	[thread overview]
Message-ID: <CAKgNAki_BpL-qGX=mfYJiWLz-AoDTy2VK9uvFGjQSnYi31b_eA@mail.gmail.com> (raw)
In-Reply-To: <20210725170726.GA16503@Debian-50-lenny-64-minimal>

Fixed as suggested. Thanks,Helge.

Cheers,

Michael

On Sun, 25 Jul 2021 at 19:07, Helge Kreutzmann <debian@helgefjell.de> wrote:
>
> Dear Linux manpages maintainer,
> the manpage-l10n project maintains a large number of translations of
> man pages both from a large variety of sources (including Linux
> Manpages) 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. If future reports
> should use another channel, please let me know.
>
> Man page: ioctl_tty.2
> Issue: Solaris, Linux → Solaris and Linux
>
> "(SVr4, UnixWare, Solaris, Linux treat I<tcsendbreak(fd,arg)> with nonzero "
> "I<arg> like I<tcdrain(fd)>.  SunOS treats I<arg> as a multiplier, and sends "
> "a stream of bits I<arg> times as long as done for zero I<arg>.  DG/UX and "
> "AIX treat I<arg> (when nonzero) as a time interval measured in "
> "milliseconds.  HP-UX ignores I<arg>.)"
>
> --
>       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/



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2021-07-25 23:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-25 17:07 Errors in man pages, here: ioctl_tty.2 Helge Kreutzmann
2021-07-25 23:18 ` Michael Kerrisk (man-pages) [this message]
2021-07-25 23:19   ` Michael Kerrisk (man-pages)
  -- strict thread matches above, loose matches on Subject: below --
2021-07-25 17:07 Helge Kreutzmann
2021-08-10  1:54 ` Michael Kerrisk (man-pages)
2021-07-25 17:07 Helge Kreutzmann
2021-07-25 23:17 ` 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='CAKgNAki_BpL-qGX=mfYJiWLz-AoDTy2VK9uvFGjQSnYi31b_eA@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).