From: Helge Kreutzmann <debian@helgefjell.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: Errors in man pages, here: gethostbyname(3): Space/Formatting
Date: Mon, 20 Apr 2020 21:48:56 +0200 [thread overview]
Message-ID: <20200420194855.GE19913@Debian-50-lenny-64-minimal> (raw)
In-Reply-To: <2318ec0f-bc6b-c202-3fca-42c10c714372@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
Hello Michael,
On Sun, Apr 19, 2020 at 10:09:16PM +0200, Michael Kerrisk (man-pages) wrote:
> On 4/19/20 8:48 AM, Helge Kreutzmann wrote:
> > **
> >
> > Space between true and (1) and mark up
> >
> > "The B<sethostent>() function specifies, if I<stayopen> is true (1), that a "
> > "connected TCP socket should be used for the name server queries and that the "
> > "connection should remain open during successive queries. Otherwise, name "
> > "server queries will use UDP datagrams."
>
> I don't understand this report. Can you elaborate please.
We translator understood the "(1)" as the section number for the man
page of true. So actually it should also contain markup, i.e.
true (1) → B<true>(1)
And there is no space between the man page name and the section. If
another meaning was intended, then we translators misunderstood this
sentence completly.
Best regards
Helge
--
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-20 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 6:48 Errors in man pages, here: gethostbyname(3): Space/Formatting Helge Kreutzmann
2020-04-19 20:09 ` Michael Kerrisk (man-pages)
2020-04-20 19:48 ` Helge Kreutzmann [this message]
2020-04-20 20:01 ` Michael Kerrisk (man-pages)
2020-04-21 19:02 ` 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=20200420194855.GE19913@Debian-50-lenny-64-minimal \
--to=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--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).