[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #64937] [troff] officially support composite character unmapping
|
From: |
G. Branden Robinson |
|
Subject: |
[bug #64937] [troff] officially support composite character unmapping |
|
Date: |
Tue, 28 Nov 2023 20:07:29 -0500 (EST) |
URL:
<https://savannah.gnu.org/bugs/?64937>
Summary: [troff] officially support composite character
unmapping
Group: GNU roff
Submitter: gbranden
Submitted: Wed 29 Nov 2023 01:07:26 AM UTC
Category: Core
Severity: 1 - Wish
Item Group: Warning/Suspicious behaviour
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Wed 29 Nov 2023 01:07:26 AM UTC By: G. Branden Robinson <gbranden>
You can set up composite character mappings.
The stock file _composite.tmac_ does so.
But can you _unmap_ or cancel these mappings?
It turns out, yes.
Observe:
$ nl ATTIC/composite-unmap.groff
1 .nf
2 \[a $] \" not a defined composite character combination; no warning
3 \[a aa]
4 .composite aa \" will warn with -ww, but _does_ undo the mapping
5 \[a aa]
6 .pl \n[nl]u
$ nroff -ww ATTIC/composite-unmap.groff
troff:ATTIC/composite-unmap.groff:4: warning: missing identifier
a
รก
a
So all we really need to do is remove the diagnostic message and document the
behavior.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64937>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #64937] [troff] officially support composite character unmapping,
G. Branden Robinson <=