[bug #63635] [troff] support `hydefault` register or similar

Follow-up Comment #2, bug #63635 (group groff): Its intended use would seem to call for making the hydefault value global. Can you speak to the rationale for making it environment-specific? ___ Reply to this item at:

[bug #65403] Meaning of ".if c" in nroff mode undocumented

URL: Summary: Meaning of ".if c" in nroff mode undocumented Group: GNU roff Submitter: barx Submitted: Sat 02 Mar 2024 04:40:39 PM CST Category: Core Severity:

[bug #59962] soelim(1) man page uses pic diagram--should it?

Follow-up Comment #15, bug #59962 (group groff): [comment #6 comment #6:] > grotty(1), the output driver for terminal devices--has no way to > query the terminal device regarding its repertoire of supported > glyphs or Unicode code points[1]. > > [1] People familiar with groff may wonder about th

[bug #63635] [troff] support `hydefault` register or similar

Follow-up Comment #3, bug #63635 (group groff): [comment #2 comment #2:] > Its intended use would seem to call for making the hydefault value global. Can you speak to the rationale for making it environment-specific? Sure. A) The hyphenation mode itself is already a property of the environment.

[bug #65403] Meaning of ".if c" in nroff mode undocumented

Follow-up Comment #1, bug #65403 (group groff): Yes. An unfortunate property of the "unicode" directive documented in _groff_font_(5) is that it causes this test to always succeed. ___ Reply to this item at:

[bug #65403] Meaning of ".if c" in nroff mode undocumented

Follow-up Comment #2, bug #65403 (group groff): [comment #1 comment #1:] > An unfortunate property of the "unicode" directive documented in > _groff_font_(5) is that it causes this test to always succeed. Be that as it may, the test for \[bu] also succeeds in devascii, despite font/devascii/DESC

[bug #65403] Meaning of ".if c" in nroff mode undocumented

Follow-up Comment #3, bug #65403 (group groff): [comment #2 comment #2:] > [comment #1 comment #1:] > > An unfortunate property of the "unicode" directive documented in > > _groff_font_(5) is that it causes this test to always succeed. > > Be that as it may, the test for \[bu] also succeeds in de

[bug #63635] [troff] support `hydefault` register or similar

Follow-up Comment #4, bug #63635 (group groff): [comment #3 comment #3:] > A) The hyphenation mode itself is already a property of the > environment. True, but this to me doesn't argue either for or against having the _default_ also be per-environment. (The .hy default before this change was glo

[bug #65403] Meaning of ".if c" in nroff mode undocumented

Follow-up Comment #4, bug #65403 (group groff): [comment #3 comment #3:] > Right, because \[bu] is defined for that output device with > `fchar`, in tty.tmac. Oh. Right. I knew that, of course. *fidgets awkwardly with shirt cuffs* ___

[bug #63635] [troff] support `hydefault` register or similar

Follow-up Comment #5, bug #63635 (group groff): [comment #4 comment #4:] > [comment #3 comment #3:] > > A) The hyphenation mode itself is already a property of the > > environment. > > True, but this to me doesn't argue either for or against having the _default_ also be per-environment. (The .hy