Follow-up Comment #9, bug #68261 (group groff): On Tuesday, 12 May 2026 18:53:02 BST you wrote: > Follow-up Comment #8, bug #68261 (group groff): > > One might argue that this is okay, because what we're trying to do is > deprecate use of those _names_ in the document. > > On the other hand, by remapping the names, the user is effectively > communicating their awareness of the issue and doing something about it. > By that reasoning, we shouldn't be diagnosing here. They can translate > 'C' to 'SUPERCALIFRAGILISTICEXPIALIDOCIOUS' on their system and, if > they've set up font description files such that that font name can be > resolved and mounted, then it's none of groff's business. > > So I might need to revisit > [https://cgit.git.savannah.gnu.org/cgit/groff.git/commit/?id=5011cd1d5a > commit 5011cd1d5a]. > > What do you think? > Whilst it is only a deprecation and works (by switching to CR as it always has), I'm not too bothered, it is educating the users away from using a pseudo
font (and the actual warning can be suppressed as you explained). My concern
was if, at the end of the deprecation, you intended to convert the warning to
an error, since it would mean that users who decide to tell troff which font
to use instead of the pseudo (i.e. have heeded the warning by adding:-
.if t .if \n(.g .ftr C CR
To a startup file to point troff to a real font) will be miffed.
Cheers
Deri
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68261>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
