Re: [PATCH] man-pages-posix-2017/man1p/dd.1p: added missing ASCII-EBCDIC tables

[Brian Inglis <Brian.Inglis@Shaw.ca>]

On 2023-08-17 09:23, Eric Blake wrote:
> On Mon, Aug 14, 2023 at 12:29:23AM +0200, Alejandro Colomar wrote:
>> On 2023-08-14 00:27, Alejandro Colomar wrote:
>>> 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.
> 
> 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.

Hi Eric,

I've had an OG login for a few years and some Austin Group material access, but 
can only see OG gitlab Projects, and Austin Group group, but no projects or 
subgroups, so that appears to be separately authorised - perhaps by repo and 
login or via Plato visibility level: the Mailing List appears to be Public level 
and Drafts are subject to terms.

>>>> 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.

Perhaps originally from AT&T 6th edition sources in mm?

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

I've found OG and Austin Group info and docs to be freely accessible for 
personal use (not necessarily easy to navigate and find), unlike WG14 C F/DIS 
(Final/Draft Intl Std) which are (now) locked in password protected zips prior 
to ISO publication.

> I'm not forwarding this email directly, but I'm happy to be a liaison
> to connect you with other Austin Group members.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry