[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #64592] [troff] registers .m and .M contain no initial value
From: |
G. Branden Robinson |
Subject: |
[bug #64592] [troff] registers .m and .M contain no initial value |
Date: |
Fri, 25 Aug 2023 09:35:14 -0400 (EDT) |
Update of bug #64592 (project groff):
Item Group: Incorrect behaviour => Warning/Suspicious
behaviour
Status: None => Need Info
Assigned to: None => gbranden
Summary: Registers .m and .M contain no initial value =>
[troff] registers .m and .M contain no initial value
_______________________________________________________
Follow-up Comment #1:
Hi Deri,
I was able to confirm the initial emptiness of these registers at formatter
startup.
The registers seem to be behaving as documented.
\n[.m] Stroke color (string‐valued); see .gcolor and \m.
Empty if the stroke color is the default.
\n[.M] Fill color (string‐valued); see .fcolor and \M.
Empty if the fill color is the default.
Also, there is a color named "default".
Each output device has a color named 'default', which cannot be
redefined. A device's default stroke and fill colors are not
necessarily the same. For the 'dvi', 'html', 'pdf', 'ps', and 'xhtml'
output devices, GNU 'troff' automatically loads a macro file defining
many color names at startup. By the same mechanism, the devices
supported by 'grotty' recognize the eight standard ISO 6429/EMCA-48
color names.(1) (*note Colors-Footnote-1::)
I don't know that we have access via the _roff_ language to what that default
is.
I also don't know if we can just assume that the default stroke and fill
colors are black, though it seems likely to me that that's extremely common.
What is your use case?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64592>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/