[bug #62983] [troff] want diagnostic if '\o' encountered while formatting for nroff device

[Dave]

Follow-up Comment #1, bug #62983 (project groff):

"grotty can't overstrike" doesn't appear to be an accurate characterization. 
grotty cheerfully produces overstruck characters:

$ printf '\o"+o"\n' | nroff | head -1 | od -c
                                                1.   +  \b   o  \n
0000004

And depending on where that output goes, the overstriking can happen:

$ printf '\o"+o"\n' | nroff | lp -o raw
request id is officejet-553 (0 file(s))

This emits a page from my printer with an "o" and "+" on top of each other. 
(And I seem to recall a time before some CUPS upgrade when I could get
overstruck characters without the "-o raw" option.)

It is extant terminal emulators, not grotty, that fail to overstrike
characters.  But I don't think anything theoretically prevents, say, a new
xterm fork from supporting the capability.


    _______________________________________________________

Reply to this item at:

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

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