bugGNU roff - Bugs: bug #59932, allow characters defined with...

 
 

bug #59932: allow characters defined with .*char requests to be kerned

Submitter:  Dave <barx>
Submitted:  Sat 23 Jan 2021 04:14:08 PM UTC
   
 
Category:  Core Severity:  1 - Wish
Item Group:  Feature change Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 23 Nov 2022 10:20:37 PM UTC, comment #1: 

Updates to the "two real-world cases" in the original submission:

Dave <barx>
Group Member
Sat 23 Jan 2021 04:14:08 PM UTC, original submission:  

The Texinfo manual clearly states: "Only the current font is checked for ligatures and kerns; neither special fonts nor entities defined with the 'char' request (and its siblings) are taken into account."

This limitation seems the wrong default.  If kerning were done by default for .char-defined characters, users who want to disable kerning before or after such a character could do so with \&.  Instead, currently such kerning is inactive by default, and there is really no way to tell groff to turn it on.

Two real-world cases where this matters:

  • Bug #59839: the proffered rfc1345.tmac is a list of nearly 1700 character aliases defined with .char.  With the current restriction, no character specified with one of these aliases will be kerned.
  • Bug 58930 comment 9


On the email list, I proposed changing this behavior (http://lists.gnu.org/archive/html/groff/2021-01/msg00031.html), and while responses were extremely limited, no one opposed the idea.

Dave <barx>
Group Member

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by barx (Submitted the item)
  •  

    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.

     

    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code