[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #62691] [troff] character translations should be associated with th
From: |
G. Branden Robinson |
Subject: |
[bug #62691] [troff] character translations should be associated with the environment |
Date: |
Sun, 23 Oct 2022 16:18:45 -0400 (EDT) |
Follow-up Comment #3, bug #62691 (project groff):
[comment #2 comment #2:]
> Would this be a new .tr-like request that would define per-environment
character translations, or are you looking to alter the behavior of the
existing (three) .tr(s)? 'Cause I can see how someone might be dismayed by
the results in your example, but I can also see how someone might want the
translation to be global. Consider a user who finds \[oq] and \[cq] both
clunky to type and ugly in text, and also knows they'll never use curly braces
in their document. They'd likely want a mapping of the latter to the former
to apply everywhere.
>
>
> .tr {\[oq]}\[cq]
> .ev title
> .tl ''The {header}''
> .ev
> This is in {single quotes.}
>
It is a distinction I am considering creating. `char` mappings would be
global, `tr` mappings would be per-environment.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62691>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/