[bug #51020] groff_char(7) manual: fix table "7-bit Character Codes"

[anonymous]

URL:
  <http://savannah.gnu.org/bugs/?51020>

                 Summary: groff_char(7) manual: fix table "7-bit Character
Codes"
                 Project: GNU troff
            Submitted by: None
            Submitted on: Sat 13 May 2017 08:21:51 PM UTC
                Severity: 3 - Normal
              Item Group: Incorrect behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None

    _______________________________________________________

Details:

In the REFERENCE section of the groff_char(7) manual, there is a table listing
"7-bit Character Codes 32-126".

It is, however, not quite clear whether the intention is to list the rendering
of printable ASCII *input* characters or to list *output* glyphs that match
characters in the printable ASCII range.

If the former, then a number of renderings are plainly wrong in the "Output"
column.  If the latter, then the "Input" column lacks the escaping that is
explained right above the table.

I think it makes sense to show *both* of the above in the table.  The attached
patch does that.

Note three details:

1. I also fix the input character for MINUS SIGN shortly before the table to
use the current font, as recently explained by Doug McIlroy on
<address@hidden>.

2. Strictly speaking, "\-" is ASCII HYPHEN-MINUS neither on the "Input" nor on
the "Output" side.  Including it anyway makes sense because an input character
that renders as ASCII HYPHEN-MINUS across all output devices simply doesn't
exists, "\-" comes closest, and should also be listed here because it is so
important.

3. U+02DC SMALL TILDE is unusual in so far as no named character escape
sequence exists that resolves to it, and using the unescaped ASCII TILDE in
the "Output" column would be wrong because the man(7) macros override the very
rule we are trying to document here and would render it wrongly as U+0060
TILDE for the -Tutf8 output device.  So the best way (admittedly kludgy) is to
use a Unicode character escape sequence for this weird case.



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Sat 13 May 2017 08:21:51 PM UTC  Name: groff_char.patch  Size: 2kB   By:
None

<http://savannah.gnu.org/bugs/download.php?file_id=40678>

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51020>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/