Follow-up Comment #21, bug #42870 (group groff): So, as I read this, the upshot is that .hw has always (for some value of "always") accepted special character escapes. When using them seemed to have no effect (as in comment #16, clarified in comment #17), it's because the appropriate .hcodes had not been established.
This matches results from groff 1.22.4.
$ file hw_test
hw_test: troff or preprocessor input, ISO-8859 text
$ iconv -f iso-8859-1 hw_test
.hcode á á
.hw h\['a]-worth
.ll 5n
Jack H\['a]worth is an agent of destruction.
$ groff --version | head -1
GNU groff version 1.22.4
$ nroff -Wbreak hw_test | cat -s
Jack
Há-
worth
is an
agent
of
de-
struc-
tion.
In fact, unlike .hcode, whose input-character restrictions have long been
documented, nothing in .hw's documentation has ever mention such a
restriction. The .hw claim seems to originate in Werner's email cited in
comment #0.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?42870>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
