[bug #60372] remove obsolete (and somewhat misleading) Y2K info from groff(7)

[Dave]

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

                 Summary: remove obsolete (and somewhat misleading) Y2K info
from groff(7)
                 Project: GNU troff
            Submitted by: barx
            Submitted on: Sun 11 Apr 2021 05:48:45 AM CDT
                Category: Core
                Severity: 2 - Minor
              Item Group: Documentation
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None

    _______________________________________________________

Details:

We should no longer need to explicitly document Y2K compliance.  (If anything,
we should document Y2K38 compliance, as we're closer to that year than to
2000.)

And the way man/groff.7.man currently documents it is not even accurate.  Of
the yr register it says, "Current year minus 1900.  For Y2K compliance use
register 'year' instead."  But register yr is fully Y2K compliant; it is
merely, as documented, offset by 1900.  In 2021 it holds the correct value of
121.

Thus the attached patch removes all mentions of Y2K on this man page.  (I
don't know groff's Y2K38 readiness, so I didn't add anything about that.)



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Sun 11 Apr 2021 05:48:45 AM CDT  Name: groff.7.man.y2k.patch  Size: 379B
  By: barx

<http://savannah.gnu.org/bugs/download.php?file_id=51243>

    _______________________________________________________

Reply to this item at:

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

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