bug-groff
[Top][All Lists]
Advanced

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

[bug #63018] font/devps/ZD: make glyphs accessible via their Unicode spe


From: Dave
Subject: [bug #63018] font/devps/ZD: make glyphs accessible via their Unicode spellings
Date: Mon, 5 Sep 2022 06:17:14 -0400 (EDT)

URL:
  <https://savannah.gnu.org/bugs/?63018>

                 Summary: font/devps/ZD: make glyphs accessible via their
Unicode spellings
                 Project: GNU troff
               Submitter: barx
               Submitted: Mon 05 Sep 2022 05:17:12 AM CDT
                Category: Font devps
                Severity: 1 - Wish
              Item Group: Feature change
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Mon 05 Sep 2022 05:17:12 AM CDT By: Dave <barx>
Only two glyphs in ZD have names (\[OK] and \[rh]); the rest must be accessed
with the \N escape.

But all of these glyphs have Unicode code points.  The font description file
ought to recognize those names (in \[uXXXX] format) as well.

The work here has already been done, submitted on the email list a while back
(http://lists.gnu.org/r/groff/2021-01/msg00061.html); it remains only to
integrate this into groff.

The devps/ZD that that post points to is nearly a drop-in replacement (minus a
few header lines) for font/devps/ZD in git, so I'm tempted to characterize
this ticket as a [PATCH].  However, for completeness, at least one additional
thing could be done: defining aliases (probably in tmac/ps.tmac) for \[OK] and
\[rh] so that they can also be represented respectively by \[u2713] \[u261E]
(the forms that, for instance, preconv will emit).







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63018>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

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