From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 215971] New: dd(1p) manpage contains empty ASCII to EBDIC tables
Date: Thu, 12 May 2022 18:15:19 +0000 [thread overview]
Message-ID: <bug-215971-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215971
Bug ID: 215971
Summary: dd(1p) manpage contains empty ASCII to EBDIC tables
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: ben@bvnf.space
Regression: No
The POSIX standard includes at the end of the `OPERANDS` section tables
displaying "the octal number character values used for the ascii and ebcdic
conversions (first table) and for the ibm conversion (second table)."
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/dd.html#tagtcjh_25
In the above HTML edition of POSIX.1-2018, these tables are images, but are
generated from troff source. In the man-pages-posix converted manpage `dd(1p)`,
the tables are empty; only the titles are present:
```
...
.ce 1
\fBTable 4-7: ASCII to EBCDIC Conversion\fR
.bp
.sp
.ce 1
\fBTable 4-8: ASCII to IBM EBCDIC Conversion\fR
.SH STDIN
...
```
Perhaps the tables could be preprocessed with `tbl` and included in the
manpages?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-05-12 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 18:15 bugzilla-daemon [this message]
2022-05-14 14:52 ` [Bug 215971] dd(1p) manpage contains empty ASCII to EBDIC tables bugzilla-daemon
2022-05-14 15:04 ` bugzilla-daemon
2022-05-14 15:12 ` bugzilla-daemon
2022-05-14 18:07 ` bugzilla-daemon
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=bug-215971-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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