Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Brian Inglis <Brian.Inglis@Shaw.ca>,
	Linux Man-Pages <linux-man@vger.kernel.org>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: [PATCH] man-pages-posix-2017/man1p/dd.1p: added missing ASCII-EBCDIC tables
Date: Sun, 13 Aug 2023 23:30:30 +0200	[thread overview]
Message-ID: <c68f4010-e732-6519-a777-2744eb057887@kernel.org> (raw)
In-Reply-To: <084cb8c0074b11327c68fb60b9c5c6238eed7df1.1691960082.git.Brian.Inglis@Shaw.ca>


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

Hi Brian!

On 2023-08-13 23:01, Brian Inglis wrote:
> I have an OpenGroup/UNIX.org/Austin Group/POSIX account,
> so added the missing ASCII-EBCDIC tables by copying from the POSIX PDF,
> as copying data is fair use, and the man page copy itself is authorized.
> 
> As an aside to that, those ASCII-EBCDIC tables support characters from
> the old ISO 2033:1983 MICR/OCR character sets now in Unicode OCR block
> U+2440-U+245F, which appears only in a few fonts like Unifont and SIL
> LastResort (and MS Segoe UI Symbol), and are still available as TTF
> (some font formats and support are being dropped in favour of OTF).
> 
> They appear normal on my screen running 'man 1p dd' on my system which
> has those fallback fonts installed.
> 
> Is it sufficient to run the groff addition install-font.sh script on
> those fonts and add them to the config as .special, or is anything else
> required to register and render the glyphs on other devices?
> 
> Or should I take this up on the groff list? 

I guess Branden is reading this, so he'll be able to better answer you.
I have little clue of those things.

> 
> Signed-off-by: Brian Inglis <Brian.Inglis@Shaw.ca>
> Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=215971

Regarding the man-pages-posix project, I don't have in mind releasing any
soon.  In fact, I don't even maintain it, to be honest.  It just happens
that I'm the one with the keys to it.

The problem is that it's generated from scripts, and I don't know how that
project is organized.  I could try to get it working, but it would take
some work, and I don't feel motivated to do it.

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.

Would you mind forwarding my rage towards the Open group, which IMO is not
so open?

Thanks,
Alex

P.S.: Long live bzero(3p)!

-- 
<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 21:30 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 [this message]
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
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=c68f4010-e732-6519-a777-2744eb057887@kernel.org \
    --to=alx@kernel.org \
    --cc=Brian.Inglis@Shaw.ca \
    --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