linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arkadiusz Drabczyk <arkadiusz@drabczyk.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
	Ian Hunter <ian@ianhunter.me>
Subject: Re: Error in read.1p
Date: Fri, 27 Sep 2019 14:27:34 +0200	[thread overview]
Message-ID: <20190927122734.GA8085@comp.lan> (raw)
In-Reply-To: <20190926204500.yywdgn3dnxnkzigu@localhost.localdomain>

On Fri, Sep 27, 2019 at 06:45:02AM +1000, G. Branden Robinson wrote:
> Hi Ian & Arkadiusz,
> 
> There are a few issues here.
> 
> At 2019-09-26T20:17:54+0200, Arkadiusz Drabczyk wrote:
> > On Wed, Sep 25, 2019 at 09:41:30PM -0500, Ian Hunter wrote:
> > > Hello,
> > > 
> > > The man page for read.1p incorrectly uses a unicode minus ("−")
> > > instead of a hyphen ("-") in places where flags are being used or
> > > described.
> 
> First is that the above pages are not maintained by the Linux man-pages
> project.  They are maintained by the Austin Group, the folks behind the
> POSIX standard.  They have an issue reporting site[1].

Good to know, I couldn't find read.1p in the repository.  But at the
bottom of read.1p it says:

"Any typographical or formatting errors that appear in this page are
most likely to have been introduced during the conversion of the
source files to man page format.  To report such errors, see
https://www.kernel.org/doc/man-pages/reporting_bugs.html. "

I think this might make people want to report such bugs here.  Also, I
also wasn't able to find any mention of austingroupbugs.net neither in
man-pages-posix-2013-a/README nor at
https://www.kernel.org/doc/man-pages except for this
http://man7.org/linux/man-pages/changelog.html (at least using
Google's site: operator).  Could this information be put somewhere?

> I believe you will have to register on the site to actually file a
> report, however.  (Issues can be _viewed_ anonymously.)

Here http://austingroupbugs.net/view.php?id=1158 someone says that the
issue is already solved in `troff source' but I don't know where to
get it.

> For instance, adding the line:
> 
> .char \- \N'45'
> 
> to an appropriate configuration file (like /etc/groff/man.local) could
> do the trick, but this is a crude fix and I think I can come up with
> better solutions if I know a little bit more.

That didn't work for me because /etc/groff/man.local is never opened:

$ strace -f /usr/bin/man ./read.1p |& grep 'man.local'
[pid 13682] open("/home/ja/man.local", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 13682] open("/usr/lib64/groff/site-tmac/man.local", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 13682] open("/usr/share/groff/site-tmac/man.local", O_RDONLY) = 5

Adding .char \- \N'45' to ~/man.local didn't help.  And I already have
this in /usr/share/groff/site-tmac/man.local:

.  \" Map \- to the Unicode HYPHEN-MINUS character, to make
.  \" searching in man pages easier.
.  if '\*[.T]'utf8' \
.    char \- \N'45'

I have a hard time trying to understand the whole process and need
some reading on the subject.

> What *roff implementation are you using (Ian, Arkadiusz)?  If you don't
> know how to ask the system, try "troff -v" at the shell prompt.

$ troff -v
GNU troff (groff) version 1.22.3

-- 
Arkadiusz Drabczyk <arkadiusz@drabczyk.org>

  reply	other threads:[~2019-09-27 13:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26  2:41 Error in read.1p Ian Hunter
2019-09-26 18:17 ` Arkadiusz Drabczyk
2019-09-26 18:23   ` Arkadiusz Drabczyk
2019-09-26 20:45     ` G. Branden Robinson
2019-09-27 12:27       ` Arkadiusz Drabczyk [this message]
2019-09-27 17:45         ` G. Branden Robinson
2019-09-28 19:35           ` Arkadiusz Drabczyk

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=20190927122734.GA8085@comp.lan \
    --to=arkadiusz@drabczyk.org \
    --cc=g.branden.robinson@gmail.com \
    --cc=ian@ianhunter.me \
    --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).