Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Eric Blake <eblake@redhat.com>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	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: Thu, 17 Aug 2023 22:03:13 +0200	[thread overview]
Message-ID: <e37fb06c-4c4f-3cb3-9c7f-81c64ae3644f@kernel.org> (raw)
In-Reply-To: <34ywwugg3sgxlmyrnovuh2co5qbok2dk32hug4r2drfcu3bp33@g62hj2icprgf>


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

Hi Eric!

On 2023-08-17 17:23, Eric Blake wrote:
> 
> I'm not sure if the POSIX original is quite roff, but I just confirmed
> that I have access to the repository where Issue 8 is being worked on
> (it required me to have an Open Group login, so you may not be able to
> access this page):
> 
> https://gitlab.opengroup.org/the-austin-group/sus_base/-/commits/Issue8/
> 
> I can also recommend contacting Andrew Josey (ajosey@opengroup.org -
> admin) and/or Geoff Clare (gwc@opengroup.org - most active committer
> in that project) of the Austin Group, to figure out if there is a way
> for you to get access to that repository.
> 
>>>>
>>>> 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).  :)
>>
>> Oops, mm(7).
> 
> Based on my quick perusal, it is indeed .mm files that form the bulk
> of the content in that repository.  For example, even if you can't
> access the repository yet, I don't think there is any problem under
> the fair use doctrine for sharing a snippet of a recent commit:
> 
> | commit 7fad34c5f734d7a54c6a5fa8124baf819c2b8de5
> | Author: Geoff Clare <gwc@opengroup.org>
> | Date:   Tue Aug 8 10:52:54 2023 +0100
> | 
> |     Applied bug 1741
> | 
> | diff --git a/Base/Text/Functions/getlocalename_l.mm b/Base/Text/Functions/getlocalename_l.mm
> | index 13af2a5..339bfc5 100644
> | --- a/Base/Text/Functions/getlocalename_l.mm
> | +++ b/Base/Text/Functions/getlocalename_l.mm
> | @@ -12,7 +12,9 @@ const char *getlocalename_l(int \f6category\fP, locale_t \f6locobj\fP);
> |  .sE
> |  .yE
> |  .mH DESCRIPTION
> | -The
> | +If
> | +.Ar category
> | +is not LC_ALL, the
> |  .Fn getlocalename_l
> |  function shall return the locale name for the given locale category of
> |  the locale object
> | ...
> 
>>> 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.  :)
> 
> I'm not forwarding this email directly, but I'm happy to be a liaison
> to connect you with other Austin Group members.
> 

-- 
<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-17 20:04 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
2023-08-13 22:29       ` Alejandro Colomar
2023-08-17 15:23         ` Eric Blake
2023-08-17 20:03           ` Alejandro Colomar [this message]
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=e37fb06c-4c4f-3cb3-9c7f-81c64ae3644f@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