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

[G. Branden Robinson]

Update of bug #62983 (project groff):

                  Status:                    None => Postponed              
                 Summary: [troff] want diagnostic if '\o' encountered while
formatting for nroff device => [troff] want diagnostic if '\o' encountered
while formatting for non-overstriking device

    _______________________________________________________

Follow-up Comment #2:

Hi Dave,

[comment #1 comment #1:]
> "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
> 0000000   +  \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.

Fair point.

This will probably have to wait for the terminfo-enhanced grotty I've been
dreaming about.


    _______________________________________________________

Reply to this item at:

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

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