[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Dave
Subject: [bug #63360] kern U+2011 (nonbreaking hyphen) the same as U+2010 (hyphen)
Date: Sun, 13 Nov 2022 20:15:12 -0500 (EST)


                 Summary: kern U+2011 (nonbreaking hyphen) the same as U+2010
                 Project: GNU troff
               Submitter: barx
               Submitted: Sun 13 Nov 2022 07:15:10 PM CST
                Category: Core
                Severity: 2 - Minor
              Item Group: Rendering/Cosmetics
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


Follow-up Comments:

Date: Sun 13 Nov 2022 07:15:10 PM CST By: Dave <barx>
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.tmac
<http://git.savannah.gnu.org/cgit/groff.git/tree/tmac/fallbacks.tmac>.  Bug
#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.


Reply to this item at:


Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]