1Assume that anything that doesn't work or behaves oddly is a bug.
2The documentation should be taken as the authoritative source for
3how things ought to be.
4
5Post to the groff mailing list with bug reports, questions and
6suggestions, or contact me directly at:
7
8    peter@faustus.dyn.ca
9    or
10    ptpi@golden.net
11
12If writing me directly, please include the word "groff" or "mom" in
13the Subject line or you risk my spam filters nuking your message.
14Also, please--no html email.  That, too, gets nuked.
15
16--Peter Schaffter
17
18========================================================================
19
20Version 1.3
21===========
22
23Persistent error in html coding of docs (<nobr> tag).
24---Fixed---
25
26Version 1.2-f
27============
28
29Multiple line subheads near page bottom sometimes printing one line
30of subhead at page bottom, and subsequent lines on next page.
31---Fixed---
32
33Post-quote spacing still wonky when paragraph spacing is turned on.
34---Fixed--- (for good would be nice)
35
36RULE not always resetting quad and quad value.
37---Fixed---
38
39Version 1.2-e
40=============
41
42Some string definitions in om.tmac had superfluous spaces after
43them (e.g. $COVERTITLE).
44---Fixed---
45
46Spacing under quotes not correct when paragraph spacing is turned
47on.
48---Fixed---
49
50
51First word of last line before footnotes is getting chopped.
52---Fixed---
53
54Version 1.2-d
55=============
56
57HEADER_FAMILY not changing header family.
58---Fixed---
59
60FAMILY, after COLLATE, not changing the family of all and every
61page element or tag.
62---Fixed---
63
64Heads and subheads at the start of docs are printing one line lower
65than they should.
66---Fixed---
67 
68Gaps are appearing at the bottom of pages when there's a linebreak
69followed by a subhead.
70---Fixed---
71
72When LS is invoked after a single text line at the top of a page
73containing a T_MARGIN (set with T_MARGIN or PAGE), mom is performing
74spacing adjustments as if the first line doesn't exist.
75---Fixed---
76
77Changes made to ALD and LS in version 1.2-c should not apply when
78the document processing macros are used.  There is a significant
79conflict with the internal use of ALD when the docheader is only
80one line long (as, for example, when DOCTYPE is CHAPTER).
81---Fixed, pending discovery of further conflicts---
82
83Version 1.2-c
84=============
85
86Deferred footnotes not always being output, and groff complains
87"ending diversion FN_OVERFLOW on exit."
88---Fixed---
89
90First .LS call after a top margin has been set (with .T_MARGIN
91or .PAGE) causing mom to move off the top margin baseline.  Also,
92there are conflicts between ALD, LS and T_MARGIN.
93---Fixed---
94
95DROPCAP not properly restoring a running \*[COND] or \*[EXT] after
96COND or EXT are given as arguments to DROPCAP.
97---Fixed---
98
99Version 1.2
100===========
101
102.PAD not co-operating with mom's fontstyles, esp. when a full
103family+fontstyle is given to .FT.
104---Fixed---
105
106.DROPCAP -- ditto the above.
107---Fixed---
108
109Version 1.1.9
110=============
111
112Footnote markers not resetting properly on new pages when COLUMNS
113is enabled.
114---Fixed---
115
116When overflowed footnote material is the only footnote material on
117the page or in the column, no footnotes are output.
118---Fixed---
119
120The AUTOLEAD used in FOOTNOTE not being disabled after FOOTNOTES
121are output, or after PROCESS_FN_LEFTOVER/PROCESS_FN_IN_DIVER.
122---Fixed---
123
124COL_NEXT and COL_BREAK, when invoked during the last column on a
125page, are overprinting the last column instead of breaking to a new
126page when there are footnotes in the column.
127---Fixed---
128
129BR_AT_LINE_KERN not "break-and-spreading" text when used in
130justified copy.
131---Fixed---
132
133Version 1.1.8
134=============
135
136BLOCKQUOTE_FAMILY not changing blockquote family.
137---Fixed---
138
139FOOTNOTE, whether in column mode or not, was using
140#FN_COUNT_FOR_COLS for all footnote markers and handling.
141---Fixed---
142
143Deferred footnotes that occured on the second to last page of
144documents not printing.
145---Fixed---
146
147Version 1.1.7-a
148===============
149
150Suite number in DOCTYPE LETTER not printing.
151---Fixed---
152
153Footer elements not always vertically aligning.
154---Fixed---
155
156Footer rule gap not always correctly observed.
157---Fixed---
158
159Page numbering, when at top of page, not always falling on
160HDRFTR_MARGIN.
161---Fixed---
162
163Default page numbering style for COPYSTYLE draft is DIGIT instead
164of roman.
165---Fixed---
166
167Hyphens around page numbering when style is DIGIT, ROMAN or ALPHA
168not vertically centered.
169---Fixed---
170
171EXT arg not working with DROPCAP.
172---Fixed---
173
174DOC_QUAD not automatically set immediately after START
175---Fixed--
176
177Tabs behaving erratically during document processing.
178---Fixed---
179
180Version 1.1.7
181=============
182
183When DOCHEADER OFF <distance> is given, if <distance> falls short
184of the top margin of running text, <distance> is not respected and
185bottom margin falls low.
186---Fixed---
187
188
189Version 1.1.6-e
190===============
191
192The " mark (doublequote), when entered while not in document
193processing mode (i.e. just straightforward typesetting), outputs
194nothing unless SMARTQUOTES is invoked explicitly.
195---Fixed---
196
197Version 1.1.6-c
198===============
199
200In document processing mode, docs that use *none* of the
201docprocessing tags being ignored.
202---Fixed---
203
204Version 1.1.6-b
205===============
206
207String tabs not picking up #L_MARGIN when #L_MARGIN not explicitly
208set with L_MARGIN, PAPER or PAGE.
209---Fixed---
210
211Infinite loop when B_MARGIN is set lower than FOOTER_MARGIN during
212doc processing.
213---Fixed---
214
215Version 1.1.6-a
216===============
217
218Mom partially broken when run with groff 1.19.1.  Don't know yet
219what this is, whether bad coding in mom, or a problem with 1.19.1.
220Only solution for now: run mom 1.1.6 with groff 1.18.
221----Fixed---
222
223Top margin of endnotes pages after the first endnotes page when
224PRINTSTYLE is TYPEWRITE and endnotes single-spacing is turned on
225falling one line too high.
226---Fixed---
227
228Version 1.1.6
229=============
230
231DOCHEADER OFF (distance) not being respected.
232---Fixed---
233
234FINIS killing ENDNOTES page numbering and heads.
235---Fixed---
236
237Version 1.1.5
238=============
239
240Draft and revision not appearing in page headers.
241---Fixed---
242
243\*[RULE] not working properly with indents and justified copy.
244---Fixed---
245
246Post-epigraph spacing in TYPEWRITE causing some first pages to run too
247deep.
248---Fixed---
249
250Spacing of docheaders in TYPEWRITE not always consistent.
251---Fixed---
252
253Version 1.1.4
254=============
255
256Blockquotes that span pages running too deep.
257---Fixed---
258
259Version 1.1.3
260=============
261
262Footnotes not outputting on final page of document body when ENDNOTES
263is invoked.
264---Fixed---
265
266Pad not working properly and/or spitting out warnings when fill mode is
267on.
268---Fixed---
269
270Version 1.1.2
271=============
272
273PAGENUM_STYLE being ignored unless entered after START.
274---Fixed---
275
276Version 1.1
277===========
278
279String tabs not working as advertised when set from within other tabs.
280---Fixed---
281
282.COLLATE sometimes depositing a header on the first page of a subsequent doc.
283---Fixed with workaround BREAK_QUOTE---
284
285.UNDERLINE_QUOTES in PRINTSTYLE TYPEWRITE not on by default as advertised.
286---Fixed---
287
288.TI not cooperating with other indent styles.
289---Fixed---
290
291.WS and .SS not cooperating.
292---Fixed---
293
294.RW and .EW not working.
295---Fixed---
296
297========================================================================
298
299KNOWN PROBLEMS
300--------------
301
302The indent macros from the typesetting macro set may not always
303perform well in conjunction with the document processing macros,
304especially when documents are set in columns.  Mostly, this is the
305result of inadequate testing.  There are only so many "who'd want to
306do this anyway?" scenarios I can think of on my own.
307
308Epigraphs at the bottoms of page may sometimes run exactly one line
309deeper than they should.  The alternative (from my point of view) is
310to have them run 1 line shorter than they should.  The problem stems
311from the fact the epigraphs are leaded differently than all other text,
312and there's only so much adjusting that can be done with the whitespace
313surrounding them to get them to bottom align.  Since stylistically,
314epigraphs should never appear at the bottom of a page/column without at
315least some running text beneath them in order to make sense of the role
316they play in page layout, this not likely to be fixed for some time.
317
318