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

[Dave]

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

In the meantime, it's probably useful for the documentation to warn nroff
users that (1) few (no?) modern terminal emulators support overstruck
characters, and (2) if they must use \o, they should think about the order in
which they specify the characters, as only the last one is likely to end up
visible.  (And maybe (3) that if they want to use \o for accented characters,
there are more robust ways to achieve that.)


    _______________________________________________________

Reply to this item at:

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

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