From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Brian Inglis <Brian.Inglis@Shaw.ca>
Cc: Linux Man-Pages <linux-man@vger.kernel.org>,
Alejandro Colomar <alx.manpages@gmail.com>
Subject: Re: [PATCH] man-pages-posix-2017/man1p/dd.1p: added missing ASCII-EBCDIC tables
Date: Sun, 13 Aug 2023 17:07:07 -0500 [thread overview]
Message-ID: <20230813220707.vis3pmy57fj4bfew@illithid> (raw)
In-Reply-To: <084cb8c0074b11327c68fb60b9c5c6238eed7df1.1691960082.git.Brian.Inglis@Shaw.ca>
[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]
Hi Brian,
At 2023-08-13T15:01:44-0600, 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?
That sounds correct to me.
> Or should I take this up on the groff list?
See if the gropdf(1) and/or grops(1) pages in groff 1.23.0 get the
essential information across; if either one doesn't (independently of
the other), please report a bug against groff.
> +.sp
Just use a paragraphing macro call here, like `.P`.
> +.TS
> +centre;
> +l cB sB cB sB cB sB cB sB cB sB cB sB cB sB cB sB
> +l _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> +nB | n l | n l | n l | n l | n l | n l | n l | n l |
> +.
> +\& 0 1 2 3 4 5 6 7
> +\&
> +0000 0000 NUL 0001 SOH 0002 STX 0003 ETX 0067 EOT 0055 ENQ 0056 ACK 0057 BEL
[...]
I guess it's hard to change the tab character for this ultra-wide table
since every printable ASCII character is represented in it, and tbl
affords no mechanism to escape the tab character.
> +.TE
> +.IP
> +.SB Note:
There's no reason to use `SB` (a SunOS extension) anymore since groff
1.22.4 (2018) and mandoc 1.14.2 (2017).
.IP
.SM
.B Note:
will work fine.
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-08-13 22:07 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
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 [this message]
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=20230813220707.vis3pmy57fj4bfew@illithid \
--to=g.branden.robinson@gmail.com \
--cc=Brian.Inglis@Shaw.ca \
--cc=alx.manpages@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