bugGNU roff - Bugs: bug #51020, groff_char(7) manual: fix table...

 
 

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

Submitter:  None
Submitted:  Sat 13 May 2017 08:21:51 PM UTC
   
 
Category:  Core Severity:  3 - Normal
Item Group:  Incorrect behaviour Status:  Fixed
Privacy:  Public Assigned to:  bgarrigues
Open/Closed:  Closed Planned Release:  1.22.4
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 15 Jun 2022 06:23:29 PM UTC, comment #3: 


commit b4a395687f3caadf7c5615fe3ea5702b7b11a3e7
Author:     Ingo Schwarze <schwarze@usta.de>
AuthorDate: Mon Aug 28 23:31:47 2017 +0200
Commit:     Bertrand Garrigues <bertrand.garrigues@laposte.net>
CommitDate: Mon Aug 28 23:31:47 2017 +0200

    groff_char(7) manual: fix table "7-bit Character Codes"

    See bug at https://savannah.gnu.org/bugs/?51020.


G. Branden Robinson <gbranden>
Group administrator
Tue 29 Aug 2017 09:41:22 PM UTC, comment #2: 

Commited on master.

Bertrand Garrigues <bgarrigues>
Group administrator
Sat 13 May 2017 08:24:27 PM UTC, comment #1: 

Oops, sorry, i failed to notice that my login session had died when posting.  This patch came from me.

Ingo Schwarze <schwarze>
Group Member
Sat 13 May 2017 08:21:51 PM UTC, original submission:  

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 <groff@gnu.org>.

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.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #40678:  groff_char.patch added by None (2KiB - text/x-patch)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by gbranden (Posted a comment)
  • -email is unavailable- added by bgarrigues (Posted a comment)
  • -email is unavailable- added by schwarze (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-06-15 gbranden CategoryNone Core
        Assigned toNone bgarrigues
        Planned ReleaseNone 1.22.4
    2017-08-29 bgarrigues StatusNone Fixed
        Open/ClosedOpen Closed
    2017-05-13 None Attached File- Added groff_char.patch, #40678

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code