[bug #65955] [troff] enable "input" warning category by default and add one-off alert

[G. Branden Robinson]

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

                 Summary: [troff] enable "input" warning category by default
and add one-off alert
                   Group: GNU roff
               Submitter: gbranden
               Submitted: Fri 05 Jul 2024 08:15:02 AM 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: Fri 05 Jul 2024 08:15:02 AM UTC By: G. Branden Robinson <gbranden>
As I noted in a
[https://lists.gnu.org/archive/html/groff/2024-07/msg00011.html response to
Colin Watson on the list]:


2a. Drop cp1047.tmac, de-document it, and NEWS its withdrawal.

    See:

    https://lists.gnu.org/archive/html/groff/2023-03/msg00113.html
    https://lists.gnu.org/archive/html/groff/2023-04/msg00000.html
    https://lists.gnu.org/archive/html/groff/2024-05/msg00028.html

2b. [troff] emit special diagnostic on first occurrence of input
    character code > 127

    This would tell people that EBCDIC support is gone, that they
    need to load one of the specialized macro files for character
    encoding support, and that those will be going away too in groff
    1.25 in favor of support for UTF-8 input, so they need to look into
    preconv(1).

    In my opinion we need something like this since the semantics of
    input code points > 127 will change from groff 1.23 to 1.25.
    People/distributors skipping over 1.24 won't get warning,
    unfortunately.

    Unless they do something crazy like read the release notes.


Item 2a is already filed as bug #65724.

The idea here is that the one-off alert would explain to users why giving GNU
_troff_ ISO 8859-x or KOI8-R input produces (probably) a lot of warnings about
invalid character codes.  The individual warnings would help them to clean
their input document of those codes.

It's important to bring _preconv_(1) to people's attention.









    _______________________________________________________

Reply to this item at:

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

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

signature.asc
Description: PGP signature