[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #63366] groff.texi: clarify handling of special fonts
From: |
Dave |
Subject: |
[bug #63366] groff.texi: clarify handling of special fonts |
Date: |
Mon, 21 Nov 2022 04:24:32 -0500 (EST) |
Follow-up Comment #3, bug #63366 (project groff):
[comment #1 comment #1:]
> Now, why this vector of special fonts isn't reported as the
> global_special_fonts list, I don't know. I'm not certain
> they're _supposed_ to be the same thing.
I'm not either, hence filing this as a documentation bug under the assumption
that the code is working right, just not explained well. (Pre-groff behavior
can illuminate only so much, since troff historically lacked a .special
request. CSTR #54 does speak of "one or more special fonts," suggesting there
was some mechanism for adding them; perhaps this was a hardware operation.)
Since learning that special fonts are irrelevant to the issue I was trying to
understand in bug #63354, my desire to poke more at this now has dwindled, but
I'll let the bug report linger until you work your way down to this part of
the docs.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63366>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/