[bug #66040] [troff] no longer warns about unrecognized .hcode input

[Dave]

Follow-up Comment #11, bug #66040 (group groff):

Fuller reply later, when I've had time to digest all this, but to get the ball
rolling:

[comment #10 comment #10:]
> What I gather is that what bug #42870, and you, are asking for
> is that we be able to substitute special characters for these
> ordinary ones.

Correct.  (Or, to be more specific, able to substitute special characters for
the second character of each pair; .hcode has long accepted them for first of
each pair.)

> I think the only reason it hasn't been done is because there
> was no good answer for "what character code does a special
> character have"?

I figured there had to be some complication under the hood, because the UI
change seems so trivial that Werner would have knocked it out in an hour a
decade or two ago.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?66040>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

signature.asc
Description: PGP signature