Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	Eric Blake <eblake@redhat.com>
Cc: Brian Inglis <Brian.Inglis@Shaw.ca>,
	Linux Man-Pages <linux-man@vger.kernel.org>
Subject: Re: [PATCH] man-pages-posix-2017/man1p/dd.1p: added missing ASCII-EBCDIC tables
Date: Mon, 14 Aug 2023 00:27:54 +0200	[thread overview]
Message-ID: <033cf8fb-5c84-d9eb-a01e-caff597a951b@kernel.org> (raw)
In-Reply-To: <20230813222035.a5ybcqbpnzlapraz@illithid>


[-- Attachment #1.1: Type: text/plain, Size: 2752 bytes --]

[+= Eric]

Hi Branden, Eric,

On 2023-08-14 00:20, G. Branden Robinson wrote:
> At 2023-08-13T23:30:30+0200, Alejandro Colomar wrote:
>> And also, I don't even have the sources, which makes things more
>> complex.
>>
>> I wish that POSIX allowed us to have a copy of the original source
>> code of the POSIX manual in the git repository.  With that, I'd find
>> it more interesting to maintain the project again.
>>
>> I'd also like to know what's the original source code of POSIX's
>> manual, because it may very well be roff(7).  If that happens to be
>> true, I'd like to have access to that source, instead of the HTML.
> 
> My understanding from hermetic comments to the Austin Group mailing list
> over the years is that:
> 
> 1. they have used groff for many years (a decade or more);
> 2. they don't use man(7) for their man pages (I was told this directly);
> 
> and
> 
> 3. they use (a customized version of) mm(7)--or I _think_ I saw someone
>    say this, but I have no citation and I am not even sure it was an
>    Open Group employee who claimed it.

I'd love to have the ms(7) source then.  That way I would have a reason
to learn ms(7).  :)
It would certainly be better than the HTML files.  It would be
interesting to adapt the Linux man-pages build system to also support
ms(7) pages.

> 
> We fixed a bunch of bugs in GNU mm for groff 1.23.0.[1]  I wonder if
> they will be cross with me about that.  Even if they didn't rely on any
> erstwhile misbehavior, the source churned, some internals changed, and
> if they patched the package, I wouldn't count on the patches still
> applying cleanly.
> 
>> Would you mind forwarding my rage towards the Open group, which IMO is
>> not so open?
> 
> Maybe scrape off the rage first, or you might get a response from Robert
> Elz, who is even more cantankerous and writes at even greater length
> than I do.  ;-)

I promise to scrape the rage if I get a name and an email of who to talk
to.  Maybe Eric can help.  :)

Cheers,
Alex

> 
> Some time ago I solicited bug reports against groff from them.  So far,
> nothing, unless they filed anonymously.
> 
> Regards,
> Branden
> 
> [1] https://savannah.gnu.org/bugs/index.php?go_report=Apply&group=groff&func=browse&set=custom&msort=0&report_id=225&advsrch=0&bug_id=&summary=&submitted_by=0&resolution_id=1&assigned_to=0&bug_group_id=0&status_id=3&severity=0&category_id=121&plan_release_id=103&history_search=0&history_field=0&history_event=modified&history_date_dayfd=13&history_date_monthfd=8&history_date_yearfd=2023&chunksz=50&spamscore=5&boxoptionwanted=1#options

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-08-13 22:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-13 21:01 [PATCH] man-pages-posix-2017/man1p/dd.1p: added missing ASCII-EBCDIC tables Brian Inglis
2023-08-13 21:30 ` Alejandro Colomar
2023-08-13 22:20   ` G. Branden Robinson
2023-08-13 22:27     ` Alejandro Colomar [this message]
2023-08-13 22:29       ` Alejandro Colomar
2023-08-17 15:23         ` Eric Blake
2023-08-17 20:03           ` Alejandro Colomar
2023-08-17 20:11           ` Brian Inglis
2023-08-17 20:21           ` Alejandro Colomar
2023-08-17 23:49           ` G. Branden Robinson
2023-08-18 13:52             ` Eric Blake
2023-08-13 22:07 ` G. Branden Robinson

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=033cf8fb-5c84-d9eb-a01e-caff597a951b@kernel.org \
    --to=alx@kernel.org \
    --cc=Brian.Inglis@Shaw.ca \
    --cc=eblake@redhat.com \
    --cc=g.branden.robinson@gmail.com \
    --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