[bug #63011] [troff] spurious warning from "do_overstrike"

[G. Branden Robinson]

Update of bug #63011 (project groff):

                  Status:                    None => Confirmed              
                 Summary: troff/input.cpp: wrong warning from "do_overstrike"
=> [troff] spurious warning from "do_overstrike"

    _______________________________________________________

Follow-up Comment #3:

Confirmed.  The warning is spurious.  The documentation is pretty bit-rotted,
or maybe started that way, and the logic in src/roff/troff/input.cpp is harder
to follow than it needs to be.

Per the source code, four escape sequences permit newlines as delimiters.

I can check three of these against V7 Unix troff behavior, but \X is a
device-independent troff innovation.

Interestingly (to me), \X is not documented even in the "Unix 4.0" version of
CSTR #54, the earliest documentation of device-independent troff known to
date.

https://lists.gnu.org/archive/html/groff/2022-06/msg00033.html

So it is really not clear to me whether it _should_ accept a newline as a
delimiter.  But, groff seems to have accepted it basically forever...

I'm working on a fix for the diagnostic messages.


    _______________________________________________________

Reply to this item at:

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

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