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

[G. Branden Robinson]

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

                 Summary: [troff] want diagnostic if '\o' encountered while
formatting for nroff device
                 Project: GNU troff
               Submitter: gbranden
               Submitted: Mon 29 Aug 2022 07:01:06 PM UTC
                Category: Core
                Severity: 1 - Wish
              Item Group: Warning/Suspicious behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Mon 29 Aug 2022 07:01:06 PM UTC By: G. Branden Robinson <gbranden>
Overstriking is futile on _nroff_ devices, in _groff_, because we don't have
device descriptions for any _nroff_-mode devices that are capable of it.

Consider a diagnostic to emit a warning about this if an overstrike escape
sequence is encountered on the input when in _nroff_ mode.

In the future, if we get an _nroff_-mode driver that _can_ overstrike
(_grotty_ and _grohtml_ can't), we might introduce a new device description
file directive, like "can-overstrike", to reflect this capability, and make
the diagnostic conditional on that.

But for now, no such orthogonality exists.

See thread beginning at
https://lists.gnu.org/archive/html/groff/2022-08/msg00223.html for a
discussion.







    _______________________________________________________

Reply to this item at:

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

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