[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #66051] [troff] permit special characters to have bespoke hyphenati
From: |
Dave |
Subject: |
[bug #66051] [troff] permit special characters to have bespoke hyphenation codes |
Date: |
Wed, 31 Jul 2024 19:13:18 -0400 (EDT) |
Follow-up Comment #6, bug #66051 (group groff):
[comment #4 comment #4:]
> Whereas *this* one will make possible:
>
> .hcode \[ss] \[ss]
>
> The fix I have in mind for bug #42780 does not.
s/bug #42780/bug #42870/
If ultimately both are to be fixed, I suppose it's academic how the individual
tickets get scoped. But I don't read anything in the #42870 description that
would rule out the .hcode line above. (Werner even contemplates entities of
the form \[u00AD], which would let .hcode process text that preconv has
already gotten its mitts on--one element of the real-world problem in the
email thread that spawned the ticket.)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66051>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
- [bug #66051] [troff] permit special characters to have bespoke hyphenation codes, G. Branden Robinson, 2024/07/31
- [bug #66051] [troff] permit special characters to have bespoke hyphenation codes, G. Branden Robinson, 2024/07/31
- [bug #66051] [troff] permit special characters to have bespoke hyphenation codes, Dave, 2024/07/31
- [bug #66051] [troff] permit special characters to have bespoke hyphenation codes, Dave, 2024/07/31
- [bug #66051] [troff] permit special characters to have bespoke hyphenation codes, G. Branden Robinson, 2024/07/31
- [bug #66051] [troff] permit special characters to have bespoke hyphenation codes, G. Branden Robinson, 2024/07/31
- [bug #66051] [troff] permit special characters to have bespoke hyphenation codes,
Dave <=