Follow-up Comment #10, bug #55154 (group groff):
[comment #0 original submission:]
> .tr a
> .tr b\~
> .tr c\
> .tr d\|
> .tr e\^
> .tr f\0
>
> This attempts to translate six alphabetic characters to six
> different types of space characters. What it does instead is
> accept the first two translations and reject the last four:
Bizarrely, while it accepts the second translation, it doesn't actually honor
it.
$ cat tr-test
.tr b\~
abc cba\p
$ nroff tr-test | cat -s
a c c a
$
I'm not sure what to think of this. On the one hand, comment #2 argues this
shouldn't work; even the texinfo manual says a .tr target should be a glyph,
which \~ isn't. On the other hand, given that fact, the translation failing
outright (as the subsequent lines of the original submission do) would make
sense, whereas silently converting a stretchable space to an unstretchable one
surely does not.
The deprecation proposed in bug #64337 would make this moot.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?55154>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
