[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #57583] [PATCH] s.tmac: Test the default number for warnings for nr
From: |
G. Branden Robinson |
Subject: |
[bug #57583] [PATCH] s.tmac: Test the default number for warnings for nroff |
Date: |
Tue, 4 Feb 2020 02:47:40 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 PureBrowser/60.9.0 |
Update of bug #57583 (project groff):
Status: None => Need Info
Assigned to: None => gbranden
_______________________________________________________
Follow-up Comment #1:
If I understand this patch correctly, I'm not sure I agree with it.
Rewriting the proposed commit message in my own words, I have:
"tmac/s.tmac: Disable font warnings in nroff mode."
If that's accurate then I don't think I agree. I think ms document authors
_should_ get warnings if they try to "mount" other font families when they're
rendering to a terminal, which can't (generally) perform this action.
People _love_ to use font family changes to communicate semantic content. The
warning reminds them of what they're losing in nroff-mode output. If they
want to avoid the warnings they should `.if n` or `.ie n` in their source
document. They can supply alternative information to replace what would have
been communicated by the font family change.
Or they can shut the warning off themselves.
Or they can do this at the top of their ms document:
.if n .ab TERMINALS GO HOME
What do other people think?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57583>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [bug #57583] [PATCH] s.tmac: Test the default number for warnings for nroff,
G. Branden Robinson <=