[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #66000] [mm] early .CS call makes top page margin wrong thereafter
From: |
Dave |
Subject: |
[bug #66000] [mm] early .CS call makes top page margin wrong thereafter |
Date: |
Wed, 17 Jul 2024 12:00:04 -0400 (EDT) |
URL:
<https://savannah.gnu.org/bugs/?66000>
Summary: [mm] early .CS call makes top page margin wrong
thereafter
Group: GNU roff
Submitter: barx
Submitted: Wed 17 Jul 2024 10:59:59 AM CDT
Category: Macro package mm
Severity: 2 - Minor
Item Group: Incorrect behaviour
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Wed 17 Jul 2024 10:59:59 AM CDT By: Dave <barx>
A post to the email list in early March
(http://lists.gnu.org/r/groff/2024-03/msg00001.html) identified some bugs and
possible bugs in -mm. This macro package has seen a huge number of changes
since then, so it's hard to identify what might have already been addressed.
But here's my stab at it.
* "Judging by the DWB 3.3 troff manual, this looks like the way the `SG` macro
is supposed to work for memorandum type 0. Memorandum type 4 should redefine
it to be a no-op. groff mm's implementation evidently doesn't."
* This looks like it was addressed by
[http://git.savannah.gnu.org/cgit/groff.git/commit/?id=774bac73c commit
774bac73c].
* "moving the `CS` macro call earlier, right after `MT`, did not produce the
results I expected; the abstract did not appear on the cover page. However,
checking it against Heirloom and that formatter's ancestor DWB 3.3 troff, I
see that that appears to be consistent with historical practice. (It _still_
may be a bug, however.)"
* This seems to be an open question.
* "Another problem I get when relocating the `CS` call early in the document
is that the top page margin is wrong thereafter. DWB and Heirloom don't mess
that up so it looks like a groff mm bug to me."
* If this has been done, I can't identify it: No contrib/mm/m.tmac
commit
messages of 2024 mention either CS or margins.
* "If I add an `AF` call to the document, I get appropriate results with groff
mm but not DWB or Heirloom--they're 'stuck' with the default. While a
difference, I do not consider this a bug in groff mm. It may be a difference
worth noting in the groff_mm(7) man page, however."
* Appears not to have been done: the entirety of the text about .AF in
groff_mm(7) is, "Specify a memorandum's organizational affiliation. At most
one can be declared; _org-name_ is used by memorandum types and available to
cover sheets." However, the "may" above implies "or may not," so this is also
a potentially open question.
I've based this bug report's summary on the .CS issue that seems a clear and
unresolved bug. The two maybes above could potentially be swept up here also,
or I can open separate reports for them if that seems warranted. I'm adding
the original reporter of these problems to the cc.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66000>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
- [bug #66000] [mm] early .CS call makes top page margin wrong thereafter,
Dave <=