URL:
<https://savannah.gnu.org/bugs/?65403>
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: 2 - Minor
Item Group: Documentation
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Sat 02 Mar 2024 04:40:39 PM CST By: Dave <barx>
Branden said in bug #59962: "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.... People familiar with groff may
wonder about this claim given the existence of '.if c', '.fchar', and similar.
As I understand it, these work at the interface between groff language input
and the output driver."
In short, ".if c" doesn't do what you'd probably expect in grotty. This
simple test (originally posted in bug #56015) seems to bear this out:
$ cat bullet_test
.if c\[bu] .tm Bullet exists.
$ groff -Tutf8 bullet_test
Bullet exists.
$ groff -Tascii bullet_test
Bullet exists.
However, this seems un(der)documented. All the "Operators in Conditionals"
section of the Texinfo manual says about what 'c GLYPH' tests is "True if
GLYPH is available." Particularly, "available" is not defined, and may seem
too obvious to need defining, but the above shows the "obvious" interpretation
doesn't apply to grotty.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65403>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
