Update of bug #67547 (group groff):

                Severity:              3 - Normal => 1 - Wish
                  Status:                    None => Invalid
             Open/Closed:                    Open => Closed

    _______________________________________________________

Follow-up Comment #1:

This ticket is completely pointless.

Obviously, implementing the .Tg macro in groff(1) is utterly impossible
because groff has none of the prerequisite infrastructure that would be
required, and implementing the prerequisite infrastructure would be extremely
hard and arguably far outside the scope of groff: groff is a general-purpose
typesetting system and not a manual page search & display system - in
GNU-based systems, the latter function is typically filled by man-db, not by
groff.  Just as it is unreasonable to expect that mandoc can do everything
that groff can do, it is unreasonable to assume that groff can do everything
that mandoc can do.  The reason why mandoc can usefully implement .Tg is
because mandoc combines the relevant functionality of nroff -mdoc, the
relevant functionality of nroff -man, all functionality of man-db, and
additional functionality provided by none of these programs in one single,
tightly integrated program.

The macro name .Tg was chosen to not clash with anything in groff, and the
semantics of the .Tg macro was specifically designed such that it can simply
be ignored with no adverse effect by software that cannot implement it.

When a user specifically ask for all warnings (-ww), it is completely
reasonable to tell them that a manual page uses a macro that groff does not
support, even if ignoring the macro does no harm and groff cannot reasonably
implement it.  The benefit of the warning for the user is that they are
essentially told "if you use a different tool than groff for processing this
manual page, you may or may not get additional functionality from this page
that you won't get with groff."

Once again, just because a warning occurs does not mean that anything is
broken and/or can be improved.
Some warning just reflect reality and are there to stay, quite likely for
good.


    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to