bugGNU troff - Bugs: bug #63360, kern U+2011 (nonbreaking hyphen)...

 
 

bug #63360: kern U+2011 (nonbreaking hyphen) the same as U+2010 (hyphen)

Submitter:  Dave <barx>
Submitted:  Mon 14 Nov 2022 01:15:10 AM UTC
 
Category:  Core Severity:  2 - Minor
Item Group:  Rendering/Cosmetics Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Planned Release:  None
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

Wed 23 Nov 2022 10:25:17 PM UTC, comment #1: 

Fixing bug #59932 would probably also resolve this problem, and is a more general solution than focusing solely on \[u2011].

Dave <barx>
Project Member
Mon 14 Nov 2022 01:15:10 AM UTC, original submission:  

Over in bug #58930, we discussed a kerning problem with the \[u2011] solution implemented there (its comments 9 and 12 give examples to show the problem), but decided to kick that can down the road.  This ticket serves to make sure the can gets picked up again at some point.

\[u2011] was (ultimately) defined in tmac/fallbacks.tmacBug #63354 suggests some tweaks to that file.  But I don't think this problem falls into that realm, because I'm not convinced it's fixable in macro space.  Even a roff request to define new kernpairs (as bug #44244 asks for) wouldn't be sufficient without also a mechanism to query a font's existing kernpairs, in order to duplicate them for a new character.

Thus, unless I'm overlooking a more elegant solution, the fix would seem to require the underlying engine to recognize that U+2011 is a variant of U+2010 with different breaking properties but that should use the same kerning data.

Dave <barx>
Project 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.9