[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #65829] Want way to translate a character to \~
From: |
Dave |
Subject: |
[bug #65829] Want way to translate a character to \~ |
Date: |
Mon, 3 Jun 2024 01:06:58 -0400 (EDT) |
URL:
<https://savannah.gnu.org/bugs/?65829>
Summary: Want way to translate a character to \~
Group: GNU roff
Submitter: barx
Submitted: Mon 03 Jun 2024 12:06:58 AM CDT
Category: Core
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 03 Jun 2024 12:06:58 AM CDT By: Dave <barx>
Comments 10 and 11 of bug #55154 point out that due to the way .tr and .char
and their ilk handle translations, there is no way to translate an input
character to a stretchable unbreakable space.
The use case presented there (of working around the now-fixed bug #62300 in
older preconvs) would not be helped by a fix to this bug, since this fix would
not be available in older groffs. But there are other reasons one might want
to translate an input character to \~.
As Bjarni points out in bug #65654, many common Unix text-display tools make
U+0020 and U+00A0 visually indistinguishable, so the user might choose to have
a different character represent U+00A0 and let groff translate it
appropriately. While this is a simple translation to preprocess before groff
sees the input, it's such a simple translation that groff ought to be able to
handle it itself.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65829>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [bug #65829] Want way to translate a character to \~,
Dave <=