[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented
From: |
Dave |
Subject: |
[bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented |
Date: |
Sat, 16 Apr 2022 17:30:57 -0400 (EDT) |
Follow-up Comment #12, bug #58962 (project groff):
[comment #7 comment #7:]
> The tmac files for the various input encodings remap the soft
> hyphen with a `tr` request. I plan to take that stuff out.
For completeness, I note this has also been done:
commit 03eee8bfb62d63aa1a989ee01d5c49ca7fafb57b
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date: Thu Apr 14 18:52:21 2022 +1000
[tmac]: Stop remapping input soft hyphen chars.
* tmac/cp1047.tmac:
* tmac/latin1.tmac:
* tmac/latin2.tmac:
* tmac/latin5.tmac:
* tmac/latin9.tmac: Stop remapping input soft hyphen characters with
`tr` requests in character encoding macro files. The formatter does
this for us now.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?58962>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented, Dave, 2022/04/13
- [bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented, G. Branden Robinson, 2022/04/13
- [bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented, Dave, 2022/04/13
- [bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented, G. Branden Robinson, 2022/04/13
- [bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented, Dave, 2022/04/14
- [bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented, G. Branden Robinson, 2022/04/14
- [bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented, G. Branden Robinson, 2022/04/16
- [bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented, Dave, 2022/04/16
- [bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented,
Dave <=