summaryrefslogtreecommitdiff
path: root/contrib/mom/momdoc/docprocessing.html
blob: 371a757662dd4919abba49c55bed58e2c81553c8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
<html>
<head>
<meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
<title>Mom -- Document Processing, Introduction and Setup</title>
</head>
<body bgcolor="#dfdfdf">

<!====================================================================>

<a href="docelement.html#TOP">Next</a>&nbsp;&nbsp;
<a href="inlines.html#TOP">Prev</a>&nbsp;&nbsp;
<a href="toc.html">Back to Table of Contents</a>

<a name="TOP"></a>
<a name="DOCPROCESSING">
	<h1 align="center"><u>DOCUMENT PROCESSING WITH MOM</u>
</h1>
</a>

<a href="#INTRO_MACROS_DOCPROCESSING">Introduction to document processing</a>
<br>
<a href="#DEFAULTS">Some document defaults</a>
<p>
<a href="#LEADING_NOTE">* IMPORTANT NOTE on leading/spacing and bottom margins *</a>
<p>
<ul>
	<li><strong>DOCUMENT SETUP</strong>
	<br>
	<a href="#DOCPROCESSING_TUT">Tutorial -- Setting up a mom document</a>
	<br>
	<ul>
		<li><a href="#REFERENCE_MACROS"><strong>The Reference Macros</strong></a>
		<ul>
			<li><a href="#TITLE">TITLE</a>
			<li><a href="#SUBTITLE">SUBTITLE</a>
			<li><a href="#AUTHOR">AUTHOR</a>
			<li><a href="#CHAPTER">CHAPTER</a>
			<li><a href="#DRAFT">DRAFT</a>
			<li><a href="#REVISION">REVISION</a>
		</ul>
		<li><a href="#DOCSTYLE_MACROS"><strong>The Docstyle Macros</strong></a>
		<ul>
			<li><a href="#DOCTYPE">DOCTYPE</a>
			<li><a href="#PRINTSTYLE">PRINTSTYLE</a>
			<li><a href="#COPYSTYLE">COPYSTYLE</a>
		</ul>
		
		<li><a href="#STYLE_BEFORE_START"><strong>Changing type/style parameters prior to START</strong></a>
		<ul>
			<li><a href="#TYPE_BEFORE_START">Using typesetting macros prior to START</a>
			<li><a href="#DOC_LEAD_ADJUST">Adjusting document leading to fill pages -- DOC_LEAD_ADJUST</a>
			<li><a href="#DOCHEADER">Managing the document header</a>
			<ul>
				<li><a href="#DOCHEADER">DOCHEADER -- turning docheaders off</a>
				<li><a href="#DOCHEADER_CONTROL">Docheader control</a>
			</ul>
		</ul>

		<li><a href="#COLUMNS_INTRO"><strong>Setting documents in columns</strong></a>
		<ul>
			<li><a href="#COLUMNS">COLUMNS</a>
			<li><a href="#COL_NEXT">COL_NEXT</a>
			<li><a href="#COL_BREAK">COL_BREAK</a>

		</ul>

		<li><a href="#START_MACRO"><strong>START</strong> -- the macro to initiate document processing</a>
		<ul>
			<li><a href="#START">START</a>
		</ul>
	
		<li><a href="#DOC_PARAM_MACROS"><strong>Changing document-wide typesetting parameters after START</strong></a>
		<ul>
			<li><a href="#DOC_LEFT_MARGIN">DOC_LEFT_MARGIN</a>
			<li><a href="#DOC_RIGHT_MARGIN">DOC_RIGHT_MARGIN</a>
			<li><a href="#DOC_LINE_LENGTH">DOC_LINE_LENGTH</a>
			<li><a href="#DOC_FAMILY">DOC_FAMILY</a>
			<li><a href="#DOC_PT_SIZE">DOC_PT_SIZE</a>
			<li><a href="#DOC_LEAD">DOC_LEAD</a>
			<li><a href="#DOC_LEAD_ADJUST">DOC_LEAD_ADJUST</a>
			<li><a href="#DOC_QUAD">DOC_QUAD</a>
		</ul>
		<br>
		<li><strong>THE DOCUMENT ELEMENT MACROS (TAGS)</strong>
		<ul>
			<li><a href="docelement.html#DOCELEMENT_INTRO">Introduction to the document element tags</a>
			<ul>
				<li><a href="docelement.html#DOCELEMENT_CONTROL">Document element (tag) control macros</a>
			</ul>
			<li><a href="docelement.html#EPIGRAPH_INTRO"><strong>Epigraphs</strong></a>
			<ul>
				<li><a href="docelement.html#EPIGRAPH">EPIGRAPH</a>
				<li><a href="docelement.html#EPIGRAPH_CONTROL">Epigrah control</a>
			</ul>
			<li><a href="docelement.html#PP_INTRO"><strong>Paragraphs</strong></a>
			<ul>
				<li><a href="docelement.html#PP">PP</a>
				<li><a href="docelement.html#PP_CONTROL">Paragraph control</a>
			</ul>
			<li><a href="docelement.html#HEAD_INTRO"><strong>Main heads</strong></a>
			<ul>
				<li><a href="docelement.html#HEAD">HEAD</a>
				<li><a href="docelement.html#HEAD_CONTROL">Head control</a>
			</ul>
			<li><a href="docelement.html#SUBHEAD_INTRO"><strong>Subheads</strong></a>
			<ul>
				<li><a href="docelement.html#SUBHEAD">SUBHEAD</a>
				<li><a href="docelement.html#SUBHEAD_CONTROL">Subhead control</a>
			</ul>
			<li><a href="docelement.html#PARAHEAD_INTRO"><strong>Paragraph heads</strong></a>
			<ul>
				<li><a href="docelement.html#PARAHEAD">PARAHEAD</a>
				<li><a href="docelement.html#PARAHEAD_CONTROL">Parahead control</a>
			</ul>
			<li><a href="docelement.html#LINEBREAK_INTRO"><strong>Linebreaks (author linebreaks)</strong></a>
			<ul>
				<li><a href="docelement.html#LINEBREAK">LINEBREAK</a>
				<li><a href="docelement.html#LINEBREAK_CONTROL">Linebreak control</a>
			</ul>
			<li><a href="docelement.html#QUOTE_INTRO"><strong>Quotes (line for line poetic quotes)</strong></a>
			<ul>
				<li><a href="docelement.html#QUOTE">QUOTE</a>
				<li><a href="docelement.html#QUOTE_CONTROL">Quote control</a>
			</ul>
			<li><a href="docelement.html#BLOCKQUOTE_INTRO"><strong>Blockquotes (cited material)</strong></a>
			<ul>
				<li><a href="docelement.html#BLOCKQUOTE">BLOCKQUOTE</a>
				<li><a href="docelement.html#BLOCKQUOTE_CONTROL">Blockquote control</a>
			</ul>
			<li><a href="docelement.html#FOOTNOTE_INTRO"><strong>Footnotes</strong></a>
			<ul>
				<li><a href="docelement.html#FOOTNOTE">FOOTNOTE</a>
				<li><a href="docelement.html#FOOTNOTE_CONTROL">Footnote control</a>
			</ul>
			<li><a href="docelement.html#FINIS_INTRO"><strong>Document termination</strong></a>
			<ul>
				<li><a href="docelement.html#FINIS">FINIS</a>
				<li><a href="docelement.html#FINIS_CONTROL">Finis control</a>
			</ul>
		</ul>
		
		<li><a href="headfootpage.html#HEADFOOTPAGE"><strong>HEADERS and FOOTERS</strong></a>
		<br>
		<ul>
			<li><a href="headfootpage.html#HEADFOOTPAGE_INTRO">Introduction to headers/footers</a>
			<li><a href="headfootpage.html#HEADFOOT_MANAGEMENT">Managing headers/footers</a>
			<ul>
				<li><a href="headfootpage.html#HEADERS">HEADERS</a> -- on or off
				<li><a href="headfootpage.html#FOOTERS">FOOTERS</a> -- on or off
				<li><a href="headfootpage.html#FOOTER_ON_FIRST_PAGE">FOOTER_ON_FIRST_PAGE</a>
			</ul>
			<li><a href="headfootpage.html#HEADFOOT_CONTROL">Header/footer control</a>
			<ul>
				<li><a href="headfootpage.html#HDRFTR_STRINGS">Header/footer strings</a>
				<li><a href="headfootpage.html#HDRFTR_STYLE">Header/footer style</a> -- global and part-by-part
				<li><a href="headfootpage.html#HDRFTR_VERTICAL">Header/footer placement and spacing</a>
				<li><a href="headfootpage.html#HDRFTR_SEPARATOR">The header/footer separator rule</a>
			</ul>
		</ul>
		<li><a href="headfootpage.html#PAGINATION"><strong>PAGINATION</strong></a>
		<br>
		<ul>
			<li><a href="headfootpage.html#PAGINATE">PAGINATE -- on or off</a>
			<li><a href="headfootpage.html#PAGENUMBER">PAGENUMBER -- user supplied page number</a>
			<li><a href="headfootpage.html#PAGENUM_STYLE">PAGENUM_STYLE -- digits, roman numerals, etc.</a>
			<li><a href="headfootpage.html#PAGINATION_CONTROL">Pagination control</a>
		</ul>
		<br>
		<li><a href="rectoverso.html#RECTOVERSO"><strong>RECTO_VERSO PRINTING and COLLATING</strong></a>
		<br>
		<ul>
			<li><a href="rectoverso.html#RECTOVERSO_INTRO">Introduction to recto/verso</a>
			<ul>
				<li><a href="rectoverso.html#RECTO_VERSO">RECTO_VERSO</a>
				<li><a href="rectoverso.html#SWITCH_HDRFTR">SWITCH_HEADERS</a> (also FOOTERS)
			</ul>
			<li><a href="rectoverso.html#COLLATE_INTRO">Introduction to collating</a>
			<ul>
				<li><a href="rectoverso.html#COLLATE">COLLATE</a>
			</ul>
		</ul>
	
		<li><a href="cover.html#COVER"><strong>CREATING A COVER PAGE</strong></a>
		<br>
		<li><a href="letters.html#LETTERS"><strong>WRITING LETTERS</strong></a>
		<ul>
			<li><a href="letters.html#LETTERS_INTRO">Introduction to writing letters</a>
			<li><a href="letters.html#TUTORIAL">Tutorial on writing letters</a>
			<li><a href="letters.html#LETTERS_DEFAULTS">Default style for letters</a>
			<li><a href="letters.html#LETTERS_MACROS">The letter macros</a>



		</ul>
	</ul>
</ul>
<br>
<hr>

<h2><a name="INTRO_MACROS_DOCPROCESSING"><u>Introduction to document processing</u></a></h2>
<p>
As explained in
<a href="intro.html#INTRO_DOCPROCESSING">Document processing with mom</a>,
document processing uses markup tags to identify document elements
like heads, paragraphs, and so on.  The tags are, of course, macros,
but with sensible, readable names that make them easy to grasp and
easy to remember.  (And don't forget: if you don't like the
&quot;official&quot; name of a tag -- too long, cumbersome
to type in, not &quot;intuitive&quot; enough -- you can change it
with the
<a href="goodies.html#ALIAS">ALIAS</a>
macro.)
<p>
In addition to the tags themselves, <strong>mom</strong> has an
extensive array of macros that control how they look and behave.
<p>
Setting up a <strong>mom</strong> doc is a simple, four-part procedure.
You begin by entering information about the document itself (title,
subtitle, author, etc.).  Next, you tell <strong>mom</strong> what
kind of document you're creating (e.g. chapter, letter, abstract,
etc...) and what kind of output you want (typeset, typewrittten,
draft-style, etc).  Thirdly, you make as many or as few changes to
<strong>mom</strong>'s default behaviour as you wish.  Lastly, you
invoke the
<a href="#START">START</a>
macro.  Voilà!  You're ready to write.
<br>
<hr>


<h2><a name="DEFAULTS"><u>Some document defaults</u></a></h2>

As is to be expected, <strong>mom</strong> has defaults for everything.
If you want to know a particular default, read about it in the
description of the pertinent tag.
<p>
I fear the following may not be adequately covered in the
documentation.  Just in case, here they are.
<p>
<ul>
	<li>the paper size is 8.5x11 inches
	<li>the left and right margins are 1-inch
	<li>the top and bottom margins for document text are plus/minus
		visually 1-inch
	<li>pages are numbered; the number appears centered, at the
		bottom, surrounded by hyphens ( e.g. -6- )
	<li>the first page of a document begins with a
		<a href="definitions.html#TERMS_DOCHEADER">document header</a>
	<li>subsequent pages have
		<a href="definitions.html#TERMS_HEADER">page headers</a>
		with a rule underneath
</ul>
<p>
Another way to check up on document processing defaults is to have
a look at the macro file (om.tmac).  Each macro is preceded by a
description that (generally) says what its default is (if it has
one).
<br>
<hr>

<a name="LEADING_NOTE">
	<h2><u>IMPORTANT NOTE on leading/spacing and  bottom margins</u></h2>
</a>

<strong>Mom</strong> takes evenly-aligned  bottom margins in
<a href="definitions.html#TERMS_RUNNING">running text</a>
very seriously.  Only under a very few (exceptional) circumstances
will she allow a bottom margin to &quot;hang&quot; (i.e. to fall
short).
<p>
In order to ensure even bottom margins, <strong>mom</strong>
uses the &quot;base&quot; document
<a href="definitions.html#TERMS_LEADING">leading</a>
in effect <em>at the start of each page</em> (i.e. the leading used
in paragraphs) to calculate the spacing of every document element.
Prior to invoking
<a href="#START">START</a>,
this is done with the
<a href="typesetting.html#MACROS_TYPESETTING">typesetting macro</a>
<a href="typesetting.html#LEADING">LS</a>,
afterwards with the document
<a href="definitions.html#TERMS_CONTROLMACRO">control macro</a>
<a href="#DOC_LEAD">DOC_LEAD</a>.
<p>
Because <strong>mom</strong> relies so heavily on the base document
leading, any change to the leading or spacing on a page will almost
certainly have undesirable consequences on that page's bottom margin
unless the change is fully compensated for elsewhere on the page.
<p>
In other words, if you add a few points of space somewhere on a page,
you must subtract the same number of points somewhere else on that
same page, and vice versa.
<p>
If it's a question of adding or subtracting full line spaces between
or within document elements, you can do so by using the &quot;v&quot;
<a href="definitions.html#TERMS_UNITOFMEASURE">unit of measure</a>
with whatever spacing macro you choose --
<a href="typesetting.html#ALD">ALD</a>,
<a href="typesetting.html#RLD">RLD</a>,
<a href="typesetting.html#SPACE">SPACE</a>
-- and <strong>mom</strong> won't object.  &quot;v&quot; means
&quot;the current leading&quot;, so she isn't confused by it.  And
since &quot;v&quot; accepts decimal fractions, you can add/subtract
half linespaces and quarter linespaces with &quot;v&quot; as well,
<em>provided you compensate for the fractional linespace somewhere
else on the page</em>.
<br>
<hr>

<a name="SETUP"><h2><u>Document setup</u></h2></a>

<a name="DOCPROCESSING_TUT">
	<h3><u>Tutorial -- Setting up a mom document</u></h3>
</a>
<p>
There are four &quot;parts&quot; to setting up a <strong>mom</strong>
doc (three, actually, with one optional).  Before we proceed, though,
be reassured that something as simple as
<p>
<pre>
	.TITLE     "By the Shores of Lake Attica"
	.AUTHOR    "Rosemary Winspeare"
	.PRINTSTYLE TYPESET
	.START
</pre>

produces a beautifully typeset 8.5x11 document, with a
<a href="definitions.html#TERMS_DOCHEADER">docheader</a>
at the top of page 1,
<a href="definitions.html#TERMS_HEADER">page headers</a>
with the title and author on subsequent
pages, and page numbers at the bottom of each page.  In the course
of the document, heads, subheads, citations, quotes, epigraphs,
and so on, all come out looking neat, trim, and professional.
<p>
For the purposes of this tutorial, we're going to set up a short
story -- <em>My Pulitzer Winner</em> by Joe Blow.  Thankfully,
we don't have to look at story itself, just the setup.
Joe wants the document
<p>
<ul>
	<li>to be draft 7, revision 39;
	<li>to use the &quot;default&quot; style of document formatting:
	<li>to print as draft-style output (instead of &quot;final&quot; copy output);
	<li>to be typeset, in Helvetica, 12 on 14,
		<a href="definitions.html#TERMS_RAG">rag-right</a>;
	<li>to have <a href="definitions.html#TERMS_FOOTER">footers</a>
		instead of
		<a href="definitions.html#TERMS_HEADER">headers</a>;
	<li>to use a single asterisk for
		<a href="definitions.html#TERMS_LINEBREAK">author linebreaks</a>.
</ul>
<p>
Joe Blow has no taste in typography.  His draft won't look pretty,
but this is, after all, a tutorial; we're after examples, not beauty.
<h3><u>Step 1</u></h3>

The first step in setting up any document is giving <strong>mom</strong>
some reference information.  The reference macros are:
<p>
<ul>
	<li>TITLE
	<li>SUBTITLE
	<li>AUTHOR
	<li>CHAPTER -- the chapter number
	<li>DRAFT -- the draft number
	<li>REVISION -- the revision number
</ul>
<p>
You can use as many or as few as you wish, although at a minimum,
you'll probably fill in <strong>TITLE</strong> (unless the document's
a letter) and <strong>AUTHOR</strong>.  Order doesn't matter.
You can separate the
<a href="definitions.html#TERMS_ARGUMENTS">arguments</a>
from the macros by any number of spaces.  The following are
what you'd need to start Joe Blow's story.
<p>
<pre>
	.TITLE    "My Pulitzer Winner"
	.AUTHOR   "Joe Blow"
	.DRAFT     7
	.REVISION  39
</pre>

<h3><u>Step 2</u></h3>

Once you've given <strong>mom</strong> the reference information she
needs, you tell her how you want your document formatted.  What kind
of document is it?  Should it be typeset or typewritten?  Is this
a &quot;final&quot; copy (for the world to see) or just a draft?
<strong>Mom</strong> calls the macros that answer these questions
&quot;the docstyle macros.&quot;  They are:
<p>
<ul>
	<li>DOCTYPE -- the type of document (default, chapter, user-defined, letter)
	<li>PRINTSTYLE -- typeset or typewritten
	<li>COPYSTYLE  -- draft or final copy
</ul>
<p>
<strong>Mom</strong> has defaults for <strong>DOCTYPE</strong>
and <strong>COPYSTYLE</strong>; if they're what you want, you
don't need to include them here.  However, <strong>PRINTSTYLE</strong>
has no default and MUST be present in every formatted document.
If you omit it, <strong>mom</strong> won't process the document AND
she'll complain (both to stderr and as a single printed sheet with
a warning).  Moms -- they can be so annoying sometimes. &lt;sigh&gt;
<p>
Adding to what we already have, the next bit of setup for Joe
Blow's story looks like this:
<p>
<pre>
	.TITLE    "My Pulitzer Winner"
	.AUTHOR   "Joe Blow"
	.DRAFT     7
	.REVISION  39
	\#
	.DOCTYPE     DEFAULT \"Superfluous; mom uses DOCTYPE DEFAULT by default
	.PRINTSTYLE  TYPESET
	.COPYSTYLE   DRAFT
</pre>

Notice the use of the
<a href="definitions.html#TERMS_COMMENTLINES">comment line</a>
( \# ), a handy way to keep groups of macros visually separated
for easy reading in a text editor.

<h3><u>Step 3</u></h3>

This step -- completely optional -- is where you, the user, take
charge.  <strong>Mom</strong> has defaults for <em>everything</em>,
but who's ever satisfied with defaults?  Use any of the <a
href="typesetting.html#MACROS_TYPESETTING">typesetting macros</a>
here to change <strong>mom</strong>'s document defaults (paper
size, margins, family, point size, line space, rag, etc), or
any of the document processing macros that set/change/control
the appearance of document elements.  Think of this as the
&quot;style-sheet &quot; section of a document.
<p>
Joe Blow wants his story printed in Helvetica, 12 on 14, rag
right, with
<a href="definitions.html#TERMS_FOOTER">page footers</a>
instead of
<a href="definitions.html#TERMS_HEADER">page headers</a>
and a single asterisk for the
<a href="definitions.html#TERMS_LINEBREAK">linebreak</a>
character.  None of these requirements conforms
to <strong>mom</strong>'s defaults for the chosen
<strong>PRINTSTYLE</strong> (TYPESET), so we change them here.
The setup for Joe Blow's story now looks like this:
<p>
<pre>
	.TITLE    "My Pulitzer Winner"
	.AUTHOR   "Joe Blow"
	.DRAFT     7
	.REVISION  39
	\#
	.DOCTYPE     DEFAULT
	.PRINTSTYLE  TYPESET
	.COPYSTYLE   DRAFT
	\#
	.FAMILY  H
	.PS      12
	.LS      14
	.QUAD    LEFT    \"ie. rag right
	.FOOTERS
	.LINEBREAK_CHAR *
</pre>

<h3><u>Step 4</u></h3>
The final step in setting up a document is telling <strong>mom</strong>
to start document processing.  It's a no-brainer, just the single macro
<strong>START</strong>.  Other than <strong>PRINTSTYLE</strong>, it's
the only macro required for document processing (although
I can't guarantee you'll like the results of using just the two).
<p>
Here's the complete setup for <em>My Pulitzer Winner</em>:
<p>
<pre>
	.TITLE    "My Pulitzer Winner"
	.AUTHOR   "Joe Blow"
	.DRAFT     7
	.REVISION  39
	\#
	.DOCTYPE     DEFAULT
	.PRINTSTYLE  TYPESET
	.COPYSTYLE   DRAFT
	\#
	.FAMILY   H
	.PS       12
	.LS       14
	.QUAD     LEFT    \"ie. rag right
	.FOOTERS
	.LINEBREAK_CHAR *
	\#
	.START
</pre>

As pointed out earlier, Joe Blow is no typographer.  Given that all he
needs is a printed draft of his work, a simpler setup would have been:
<p>
<pre>
	.TITLE    "My Pulitzer Winner"
	.AUTHOR   "Joe Blow"
	.DRAFT     7
	.REVISION  39
	\#
	.PRINTSTYLE  TYPEWRITE
	.COPYSTYLE   DRAFT
	\#
	.START
</pre>

<kbd>.PRINTSTYLE TYPEWRITE</kbd>, above, means that Joe's work
will come out &quot;typewritten, double-spaced&quot;, making the
blue-pencilling he (or someone else) is sure to do much
easier (which is why many publishers and agents still insist on
typewritten, double-spaced copy).
<p>
When J. Blow stops re-writing and decides to print off a final,
typeset copy of his work for the world to see, he need only
make two changes to the (simplified) setup:
<p>
<pre>
	.TITLE    "My Pulitzer Winner"
	.AUTHOR   "Joe Blow"
	.DRAFT     7
	.REVISION  39
	\#
	.PRINTSTYLE  TYPESET  \"first change
	.COPYSTYLE   FINAL    \"second change
	\#
	.START
</pre>

In the above, <kbd>.DRAFT 7, .REVISION 39,</kbd> and <kbd>.COPYSTYLE
FINAL</kbd> are actually superfluous.  The draft and revision numbers
aren't used when <strong>COPYSTYLE</strong> is <strong>FINAL</strong>,
and <strong>COPYSTYLE FINAL</strong> is <strong>mom</strong>'s
default unless you tell her otherwise.  BUT... to judge from the
number of drafts already, J. Blow may very well decide his
&quot;final&quot; version still isn't up to snuff.  Hence, he might
as well leave in the superfluous macros.  That way, when draft 7,
rev. 62 becomes draft 8, rev. 1, he'll be ready to tackle his Pulitzer
winner again.
<br>
<hr>

<!========================================================================>

<a name="REFERENCE_MACROS">
	<h2><u>The Reference Macros</u></h2>
</a>

The reference macros give <strong>mom</strong> the information
she needs to generate
<a href="definitions.html#TERMS_DOCHEADER">docheaders</a>
and
<a href="definitions.html#TERMS_HEADER">page headers</a>.  They
must go at the top of any file that uses <strong>mom</strong>'s
document processing macros.

<a name="INDEX_REFERENCE">
	<h3><u>Reference macros list</u></h3>
</a>

<ul>
	<li><a href="#TITLE">TITLE</a>
	<li><a href="#SUBTITLE">SUBTITLE</a>
	<li><a href="#AUTHOR">AUTHOR</a>
	<li><a href="#CHAPTER">CHAPTER</a>
	<li><a href="#DRAFT">DRAFT</a>
	<li><a href="#REVISION">REVISION</a>
</ul>

<!---TITLE--->

<hr width="66%" align="left">
<p>
<a name="TITLE"></a>
Macro: <strong>TITLE</strong> <var>&quot;&lt;title&gt;&quot;</var>
<br>
<em>*Argument must be enclosed in double-quotes</em>

<p>
The title string can be caps or caps/lower-case; it's up to you.
In
<a href="#PRINTSTYLE">PRINTSTYLE TYPESET</a>,
the title will appear in the
<a href="definitions.html#TERMS_DOCHEADER">docheader</a>
exactly as you typed it.  However, <strong>mom</strong> converts
the title to all caps in
<a href="definitions.html#TERMS_HEADER">page headers</a>
unless you turn that feature off (see
<a href="headfootpage.html#_CAPS">HEADER_&lt;POSITION&gt;_CAPS</a>). In
<a href="#PRINTSTYLE">PRINTSTYLE TYPEWRITE</a>,
the title always gets converted to caps.
<p>
<strong>NOTE:</strong> If your
<a href="#DOCTYPE">DOCTYPE</a>
is <strong>CHAPTER</strong>, <strong>TITLE</strong> should be the
title of the opus, not &quot;CHAPTER whatever&quot;.
<br>

<!---SUBTITLE--->

<hr width="66%" align="left">
<p>
<a name="SUBTITLE"></a>
Macro: <strong>SUBTITLE</strong> <var>&quot;&lt;subtitle&gt;&quot;</var>
<br>
<em>*Argument must be enclosed in double-quotes</em>

<p>
The subtitle string can be caps or caps/lower-case.  Since a
document's subtitle appears only in the
<a href="definitions.html#TERMS_DOCHEADER">docheader</a>,
and the title is most likely in caps, I recommend caps/lower case.
<br>

<!---AUTHOR--->

<hr width="66%" align="left">
<p>
<a name="AUTHOR"></a>
Macro: <strong>AUTHOR</strong> <var>&quot;&lt;author string&gt;&quot; [ &quot;&lt;author2 string&gt;&quot; &quot;&lt;author3 string&gt;&quot; ... ]</var>
<br>
<em>*Multiple arguments must be enclosed in double-quotes</em>

<p>
Each author string can hold as many names as you like, e.g.
<p>
<pre>
	.AUTHOR "Joe Blow"
	    or
	.AUTHOR "Joe Blow, Jane Doe" "John Hancock"
</pre>

<strong>Mom</strong> prints each string that's enclosed in
double-quotes on a separate line in the
<a href="definitions.html#TERMS_DOCHEADER">docheader</a>,
however only the first string appears in
<a href="definitions.html#TERMS_HEADER">page headers</a>.
If you want <strong>mom</strong> to put something else in the author
part of page headers (say, just the last names of a document's two
authors), redefine the appropriate part of the header (see
<a href="headfootpage.html#HEADER_CONTROL">header/footer control</a>).
<p>
The strings can be caps or caps/lower-case.  I recommend caps/lower
case.
<br>

<!---CHAPTER--->

<hr width="66%" align="left">
<p>
<a name="CHAPTER"></a>
Macro: <strong>CHAPTER</strong> <var>&lt;chapter number&gt;</var>

<p>
The chapter number can be in any form you like -- a digit, a roman
numeral, a word.  If you choose
<a href="#DOCTYPE">DOCTYPE CHAPTER</a>,
<strong>mom</strong> prints whatever argument you pass
<strong>CHAPTER</strong> beside the word &quot;Chapter&quot; as a
single line
<a href="definitions.html#TERMS_DOCHEADER">docheader</a>.
She also puts the same thing in the middle of
<a href="definitions.html#TERMS_HEADER">page headers</a>.
<p>
If you're not using <strong>DOCTYPE CHAPTER</strong>, the macro serves
no purpose and <strong>mom</strong> ignores it.
<a name="CHAPTER_STRING"></a>
<p>
If you're not writing in English, you can ask <strong>mom</strong>
to use the word for chapter in your own language by telling
her what it is with the <strong>CHAPTER_STRING</strong> macro,
like this:
<p>
<pre>
	.CHAPTER_STRING "Chapître"
</pre>

You can also use <strong>CHAPTER_STRING</strong> if you want
&quot;CHAPTER&quot; instead of &quot;Chapter&quot; in the doc- and
page-headers.  (See also the
<a href="#CHAPTER_NOTE">Special Note on CHAPTER</a>.)
<br>

<!---DRAFT--->

<hr width="66%" align="left">
<p>
<a name="DRAFT"></a>
Macro: <strong>DRAFT</strong> <var>&lt;draft #&gt;</var>

<p>
<strong>DRAFT</strong> only gets used with
<a href="#COPYSTYLE">COPYSTYLE DRAFT</a>.
If the <strong>COPYSTYLE</strong> is <strong>FINAL</strong> (the
default), <strong>mom</strong> ignores <strong>DRAFT</strong>.
<strong>DRAFT</strong> only accepts a
<a href="definitions.html#TERMS_NUMERICARGUMENT">numeric argument</a>.
<p>
<strong>Mom</strong> prints the draft number beside the word
&quot;Draft&quot; in the middle part of
<a href="definitions.html#TERMS_HEADER">page headers</a>.
If you're not writing in English, you can ask <strong>mom</strong>
to use the word for draft in your own language by telling
her what it is with the <strong>DRAFT_STRING</strong> macro,
like this:
<p>
<pre>
	.DRAFT_STRING "Ébauche"
</pre>

<!---REVISION--->

<hr width="66%" align="left">
<p>
<a name="REVISION"></a>
Macro: <strong>REVISION</strong> <var>&lt;revision #&gt;</var>

<p>
<strong>REVISION</strong> only gets used with
<a href="#COPYSTYLE">COPYSTYLE DRAFT</a>.
If the <strong>COPYSTYLE</strong> is <strong>FINAL</strong>
(the default), <strong>mom</strong> ignores the
<strong>REVISION</strong> macro.  <strong>REVISION</strong> only
accepts a
<a href="definitions.html#TERMS_NUMERICARGUMENT">numeric argument</a>.
<p>
<strong>Mom</strong> prints the revision number beside the shortform
&quot;Rev.&quot; in the middle part of
<a href="definitions.html#TERMS_HEADER">page headers</a>.
If you're not writing in English, you can ask <strong>mom</strong>
to use the word for revision, or a shortform therof in your own language
by telling her what it is with the <strong>REVISION_STRING</strong>
macro, like this:
<p>
<pre>
	.REVISION_STRING "Rév."
</pre>
<hr>

<!========================================================================>

<a name="DOCSTYLE_MACROS">
	<h2><u>The Docstyle Macros</u></h2>
</a>

The docstyle macros tell <strong>mom</strong> what type of document you're
writing, whether you want the output typeset or
&quot;typewritten&quot;, and whether you want a draft copy (with
draft and revision information in the headers) or a final copy.

<a name="INDEX_DOCSTYLE">
	<h3><u>Docstyle macros list</u></h3>
</a>

<ul>
	<li><a href="#DOCTYPE">DOCTYPE</a>
	<li><a href="#PRINTSTYLE">PRINTSTYLE</a>
	<ul>
		<li><a href="#TYPESET_DEFAULTS">Defaults for PRINTSTYLE TYPESET</a>
		<li><a href="#TYPEWRITE_DEFAULTS">Defaults for PRINTSTYLE TYPEWRITE</a>
		<ul>
			<li><a href="#TYPEWRITE_CONTROL">TYPEWRITE control macros</a>
		</ul>
	</ul>
	<li><a href="#COPYSTYLE">COPYSTYLE</a>
</ul>

<!---DOCTYPE--->

<hr width="66%" align="left">
<p>
<a name="DOCTYPE"></a>
Macro: <strong>DOCTYPE</strong> <var>DEFAULT | CHAPTER | NAMED &quot;&lt;name&gt;&quot; | LETTER</var>
<p>
The arguments <strong>DEFAULT, CHAPTER</strong> and
<strong>NAMED</strong> tell <strong>mom</strong> what to put
in the
<a href="definitions.html#TERMS_DOCHEADER">docheader</a>
and
<a href="definitions.html#TERMS_HEADER">page headers</a>.
<strong>LETTER</strong> tells her that you want to write a
lettter.
<p>
<strong>Mom</strong>'s default <strong>DOCTYPE</strong> is
<strong>DEFAULT</strong>.  If that's what you want, you don't
have to give a <strong>DOCTYPE</strong> command.
<p>
<strong>DEFAULT</strong> prints a
<a href="definitions.html#TERMS_DOCHEADER">docheader</a>
containing the title, subtitle and author information given to the
<a href="#REFERENCE_MACROS">reference macros</a>,
and page headers with the author and title.
(See
<a href="headfootpage.html#HEADER_STYLE">Default specs for headers</a>
for how <strong>mom</strong>'s outputs each part of the page header.)
<p>
<strong>CHAPTER</strong> prints &quot;Chapter #&quot; in place of a
<a href="definitions.html#TERMS_DOCHEADER">docheader</a>
(# is what you gave to
<a href="#CHAPTER">CHAPTER</a>).
Page headers contain the author, the title of the book (which
you gave with
<a href="#TITLE">TITLE</a>),
and &quot;Chapter #&quot;.  (See
<a href="headfootpage.html#HEADER_STYLE">Default Specs for Headers</a>
for <strong>mom</strong>'s default type parameters for each part of
the page header.)
<p>
<em>*See the
<a href="#CHAPTER_NOTE">Special Note on CHAPTER</a>
below for how you can make CHAPTER print something
other than &quot;Chapter #&quot; as its docheader.</em>
<p>
<strong>NAMED</strong> takes an additional argument: a name
for this particular kind of document  (e.g. outline, synopsis,
abstract, memorandum), enclosed in double-quotes.
<strong>NAMED</strong> is identical to <strong>DEFAULT</strong>
except that <strong>mom</strong> prints the argument to
<strong>NAMED</strong> beneath the
<a href="definitions.html#TERMS_DOCHEADER">docheader</a>,
as well as in page headers.
(See
<a href="headfootpage.html#HEADER_STYLE">Default specs for headers</a>
for how <strong>mom</strong>'s outputs each part of the page header.)
<p>
<strong>LETTER</strong> tells mom you're writing a letter.  See
the section
<a href="letters.html#INTRO">Writing Letters</a>
for instructions on using <strong>mom</strong> to format letters.

<a name="CHAPTER_NOTE"><h3><u>Special Note on CHAPTER</u></h3></a>
In novels, new chapters are generally (but not always)
introduced by &quot;Chapter #&quot;.  Other types of documents
(reports and so on) often require specific titles for chapters.
If your document is of this latter type, use <strong>DOCTYPE
CHAPTER</strong> in the following way:
<p>
<ol>
	<li>Omit the
		<a href="#REFERENCE_MACROS">reference macro</a>
		<a href="#CHAPTER">CHAPTER</a>
	<li>Invoke
		<a href="#CHAPTER_STRING"><code>.CHAPTER_STRING</code></a>
		with the title you'd like the chapter to have (enclosed
		in double-quotes, of course).
	<li>Optionally, if you'd like the chapter title to appear
		in the the center part of
		<a href="definitions.html#TERMS_HEADER">page headers</a>
		(its default location), invoke
		<a href="headfootpage.html#HDRFTR_CENTER"><code>.HEADER_CENTER</code></a>
		with the same title you gave to <strong>CHAPTER_STRING</strong>.

</ol>
<br>

<!---PRINTSTYLE--->

<hr width="66%" align="left">
<p>
<a name="PRINTSTYLE"></a>
Macro: <strong>PRINTSTYLE</strong> <var>TYPESET | TYPEWRITE [ SINGLESPACE ]</var>
<br>
<em>*Required for document processing.</em>

<p>
<strong>PRINTSTYLE</strong> tells <strong>mom</strong> whether to typeset
a document, or to print it out &quot;typewritten, doubled-spaced&quot;.
<p>
<strong>THIS MACRO MAY NOT BE OMITTED.</strong>  In order for
document processing to take place, <strong>mom</strong> requires
a <strong>PRINTSTYLE</strong>.  If you don't give one,
<strong>mom</strong> will warn you on stderr and print a single
page with a nasty message.
<p>
<strong>TYPESET</strong>, as the argument implies, typesets documents
(by default in Times Roman; see
<a href="#TYPESET_DEFAULTS">TYPESET defaults</a>).
You have full access to all the
<a href="typesetting.html#MACROS_TYPESETTING">typesetting macros</a>
as well as the
<a href="definitions.html#STYLE_CONTROL">style control macros</a>
of document processing.
<p>
With <strong>TYPEWRITE</strong>, <strong>mom</strong> does her best
to reproduce the look and feel of typewritten, double-spaced copy (see
<a href="#TYPEWRITE_DEFAULTS">TYPEWRITE defaults</a>).
<a href="docelement.html#DOCELEMENT_CONTROL">Control macros</a>
and
<a href="typesetting.html#INTRO_MACROS_TYPESETTING">typesetting macros</a>
that alter family, font, point size, and
<a href="definitions.html#TERMS_LEADING">leading</a>
are (mostly) ignored.  An important exception is
<a href="headfootpage.html#HDRFTR_GLOBAL_SIZE">HEADER_SIZE</a>
(and, by extension, <strong>FOOTER_SIZE</strong>), which allows
you to reduce the point size of headers/footers should they become
too crowded.  Most of <strong>mom</strong>'s inlines affecting the
appearance of type are also ignored (<strong>\*S</strong> is an
exception; there may be a few others).
<p>
In short, <strong>TYPEWRITE</strong> never produces effects other than
those available on a typewriter.  Don't be fooled by how brainless
this sounds; <strong>mom</strong> is remarkably sophisticated when
it comes to conveying the typographic sense of a document within the
confines of <strong>TYPEWRITE</strong>.
<p>
The primary uses of <strong>TYPEWRITE</strong> are: outputting hard
copy drafts of your work (for editing), and producing documents
for submission to publishers and agents who (wisely) insist on
typewritten, double-spaced copy. To get a nicely typeset version of
work that's in the submission phase of its life (say, to show fellow
writers for critiquing), simply change <strong>TYPEWRITE</strong>
to <strong>TYPESET</strong> and print out a copy.
<p>
If, for some reason, you would prefer the output of
<strong>TYPEWRITE</strong> single-spaced, pass <strong>PRINTSTYLE
TYPEWRITE</strong> the optional argument, <strong>SINGLESPACE</strong>.
<p>
If you absolutely must have a leading other than typewriter double-
or singlespaced, the only way to get it is with the
<a href="#DOC_LEAD">DOC_LEAD</a>
macro, and then ONLY if <strong>DOC_LEAD</strong> is set
<strong>before</strong> you invoke the <strong>START</strong>
macro.

<a name="TYPESET_DEFAULTS"><h3><u>TYPESET defaults</u></h3></a>
<pre>
	Family            = Times Roman
	Point size        = 12.5
	Paragraph leading = 16 points, adjusted
	Fill mode         = justified
	Hyphenation       = enabled
	                    max. lines = 2
	                    margin = 36 points
	                    interword adjustment = 1 point
	Kerning           = enabled
	Ligatures         = enabled
	Smartquotes       = enabled
	Word space        = groff default
	Sentence space    = 0
</pre>

<a name="TYPEWRITE_DEFAULTS"><h3><u>TYPEWRITE defaults</u></h3></a>
<pre>
	Family            = Courier
	Italics           = underlined
	Point size        = 12
	Paragraph leading = 24 points, adjusted; 12 points for SINGLESPACE
	Fill mode         = left
	Hyphenation       = disabled
	Kerning           = disabled
	Ligatures         = disabled
	Smartquotes       = disabled
	Word space        = groff default
	Sentence space    = groff default
	Columns           = ignored
</pre>

<a name="TYPEWRITE_CONTROL"><h3><u>PRINTSTYLE TYPEWRITE control macros</u></h3></a>
<p>
In <strong>PRINTSTYLE TYPEWRITE</strong>, <strong>mom</strong>,
by default, underlines anything that looks like italics.  This
includes the
<a href="typesetting.html#SLANT_INLINE">\*[SLANT]</a>
<a href="definitions.html#TERMS_INLINES">inline escape</a>
for pseudo-italics.
<p>
If you'd prefer that <strong>mom</strong> were
less bloody-minded about pretending to be a typewriter (i.e.
you'd like italics and pseudo-italics to come out as italics),
use the control macros <strong>.ITALIC_MEANS_ITALIC</strong> and
<strong>.SLANT_MEANS_SLANT</strong>.  Neither requires an
argument.
<p>
Although it's unlikely, should you wish to reverse the sense of
these macros in the midst of a document,
<strong>.UNDERLINE_ITALIC</strong> and
<strong>.UNDERLINE_SLANT</strong> restore underlining of
italics and pseudo-italics.
<p>
Additionally, by default, <strong>mom</strong> underlines
<a href="definitions.html#TERMS_QUOTES">quotes</a>
(but not
<a href="definitions.html#TERMS_BLOCKQUOTES">blockquotes</a>)
in <strong>PRINTSTYLE TYPEWRITE</strong>.
If you don't like this behaviour, turn it off with
<p>
<pre>
	.UNDERLINE_QUOTES OFF
</pre>

To turn underlining of quotes back on, use
<strong>UNDERLINE_QUOTES</strong> without an argument.
<p>
While most of the
<a href="docelement.html#DOCELEMENT_CONTROL">control macros</a>
have no effect on <strong>PRINTSTYLE TYPEWRITE</strong>, there
is an important exception:
<a href="headfootpage.html#HDRFTR_GLOBAL_SIZE">HEADER_SIZE</a>
(and by extension, <strong>FOOTER_SIZE</strong>).  This is
particularly useful for reducing the point size of
headers/footers should they become crowded (quite likely to
happen if the title of your document is long and your
<a href="#COPYSTYLE">COPYSTYLE</a>
is <strong>DRAFT</strong>).
<br>

<!---COPYSTYLE--->

<hr width="66%" align="left">
<p>
<a name="COPYSTYLE"></a>
Macro: <strong>COPYSTYLE</strong> <var>DRAFT | FINAL</var>

<p>
<strong>Mom</strong>'s default <strong>COPYSTYLE</strong> is
<strong>FINAL</strong>, so you don't have to use this macro unless
you want to.
<p>
<strong>DRAFT</strong> starts your document on page 1, regardless
of whether you've requested a different starting page number
with
<a href="headfootpage.html#PAGENUMBER">PAGENUMBER</a>.
Page numbers are set in lower case roman numerals.
<strong>Mom</strong> puts a draft and revision number (from the
<a href="#DRAFT">DRAFT</a>
and
<a href="#REVISION">REVISION</a>
<a href="#REFERENCE_MACROS">Reference Macros</a>)
in
<a href="definitions.html#TERMS_HEADER">page headers</a>
along with all other information that normally appears there.
<p>
<strong>FINAL</strong> respects the starting page number you give
your document.  Page numbers are set in normal (arabic) digits, and
no draft or revision number appears in the page headers.
<br>
<hr>

<!========================================================================>

<a name="STYLE_BEFORE_START"><h2><u>Changing type/style parameters prior to START</u></h2></a>

In the third (optional) part of setting up a document (see
<a href="#DOCPROCESSING_TUT">Tutorial -- setting up a mom document</a>),
you can use the
<a href="typsetting.html">typesetting macros</a>
to change <strong>mom</strong>'s document-wide defaults for margins,
line length, family, base point size,
<a href="definitions.html#TERMS_LEADING">leading</a>,
and justification style.
<p>
Two additional style concerns have to be addressed here (i.e. in
macros before
<a href="#START">START</a>):
changes to the
<a href="definitions.html#TERMS_DOCHEADER">docheader</a>,
and whether you want you want the document's nominal leading
adjusted to fill pages fully to the bottom margin.
<p>
<ul>
	<li><a href="#TYPE_BEFORE_START">Using typesetting macros prior to START</a>
	<p>
	<li><a href="#DOC_LEAD_ADJUST">DOC_LEAD_ADJUST</a>
		-- adjusting linespacing for equal, accurate bottom margins
	<li><a href="#DOCHEADER">DOCHEADER</a>
		-- turning the docheader off
	<ul>
		<li><a href="#DOCHEADER_CONTROL">Docheader control</a>
	</ul>
</ul>

<hr width="66%" align="left">
<a name="TYPE_BEFORE_START"><h2><u>Using typesetting macros prior to START</u></h2></a>

When used before the
<a href="#START">START</a>
macro, the following
<a href="typesetting.html#MACROS_TYPESETTING">typesetting macros</a>
have these meanings:
<p>
<pre>
	L_MARGIN         Left margin of pages, including headers/footers
	R_MARGIN         Right margin of pages, including headers/footers
	T_MARGIN         The point at which running text (i.e. not
	                 headers/footers or page numbers) starts on each page
	B_MARGIN         The point at which running text (i.e. not
	                 headers/footers or page numbers) ends on each page

	(PAGE            If you use PAGE, its first four arguments have the
	                 same meaning as L_ R_ T_ and B_MARGIN above.)

	LL               The line length for everything on the page;
	                 equivalent to setting the right margin with R_MARGIN
	FAMILY           The family of all type in the document
	PS               The point size of type in paragraphs; mom uses this
	                 calculate automatic point size changes (eg. for heads,
	                 footnotes, quotes, headers, etc)
	*LS or AUTOLEAD  The leading used in paragraphs; all leading and spacing
	                 of running text is calculated from this
	QUAD             Affects paragraphs only

------
*See <a href="#DOC_LEAD_ADJUST">DOC_LEAD_ADJUST</a>
</pre>

Other macros that deal with type style, or refinements thereof
(<strong>KERN, LIGATURES, HY, WS, SS,</strong> etc.), behave normally.
It is not recommended that you set up tabs or indents prior to
<strong>START</strong>.
<p>
If you want to change any of the basic parameters above
<em>after</em> <strong>START</strong> and have them affect a
document globally (as if you'd entered them <em>before</em>
<strong>START</strong>), you must use the macros listed in
<a href="#DOC_PARAM_MACROS">Changing document-wide style parameters after START</a>.
<br>

<!---DOC_LEAD_ADJUST--->

<hr width="66%" align="left">
<a name="DOC_LEAD_ADJUST"><h3><u>Adjusting document leading to fill pages</u></h3></a>
<br>
Macro: <strong>DOC_LEAD_ADJUST</strong> <var>toggle</var>
<br>
<em>*Must come after LS or AUTOLEAD and before START</em>

<p>
<strong>DOC_LEAD_ADJUST</strong> is a special macro to adjust
document
<a href="definitions.html#TERMS_LEADING">leading</a>
so that bottom margins fall precisely where you expect.
<p>
If you invoke <strong>DOC_LEAD_ADJUST</strong>, <strong>mom</strong>
takes the number of lines that fit on the page at your requested
leading, then incrementally adds
<a href="definitions.html#TERMS_UNITS">machine units</a>
to the leading until the maximum number of lines at the new leading
matches the bottom margin.  In most instances, the difference
between the requested lead and the adjusted lead is
unnoticeable.
<p>
<strong>Mom</strong> uses <strong>DOC_LEAD_ADJUST</strong> with
her default document settings, but if you invoke
<a href="typesetting.html#LS">LS</a>
or
<a href="typesetting.html#AUTOLEAD">AUTOLEAD</a>
prior to
<a href="#START">START</a>,
you have to do
<p>
<pre>
	.DOC_LEAD_ADJUST
</pre>
in order to enable it.
<p>
If you don't like the idea of <strong>mom</strong> playing around
with the leading by default, you can turn adjusting off with
<p>
<pre>
	.DOC_LEAD_ADJUST OFF
</pre>

In this scenario, the maximum number of lines that fit on a page at
the current document leading determine where <strong>mom</strong> ends
a page.  The effect will be that last lines usually fall (slightly)
short of your expected bottom margin.
<p>
<strong>NOTE:</strong> <strong>DOC_LEAD_ADJUST</strong>, if
used, must be invoked after
<a href="typesetting.html#LS">LS</a>
or
<a href="typesetting.html#AUTOLEAD">AUTOLEAD</a>
and before
<a href="#START">START</a>
<br>

<!---DOCHEADER--->

<hr width="66%" align="left">
<a name="DOCHEADER"><h3><u>Managing the docheader</u></h3></a>
<br>
Macro: <strong>DOCHEADER</strong> <var>&lt;toggle&gt; [ distance to advance from top of page ]</var>
<br>
<em>*Must come before START; distance requires a <a href="#TERMS_UNITOFMEASURE">unit of measure</a></em>

<p>
By default, <strong>mom</strong> prints a
<a href="definitions.html#TERMS_DOCHEADER">docheader</a>
on the first page of any document (see
<a href="#DOCHEADER_DESC">below</a>
for a description of the docheader).  If you don't want a docheader,
turn it off with
<p>
<pre>
	.DOCHEADER OFF
</pre> 

<strong>DOCHEADER</strong> is a toggle macro, so the argument doesn't
have to be <strong>OFF</strong>; it can be anything you like.
<p>
If you turn the docheader off, <strong>mom</strong>, by default, starts
your document in the same place she would if the docheader were there.
If you'd like her to start at a different vertical position, give
her the distance you'd like as a second argument.
<p>
<pre>
	.DOCHEADER OFF 1.5i
</pre>

This starts the document 1.5 inches from the top of the page.
The distance you give is measured from the top edge of the paper
to the
<a href="definitions.html#TERMS_BASELINE">baseline</a>
of the first line of type.
<p>
<strong>TIP:</strong> Since no document processing happens until
you invoke
<a href="#START">START</a>
-- including anything to do with docheaders -- you can typeset
your own docheader prior to <strong>START</strong> (if you don't
like the way <strong>mom</strong> does things) and use
<strong>DOCHEADER OFF</strong> with its optional distance argument
to ensure that the body of your document starts where you want.
You can even insert a PostScript file (with <strong>.PSPIC</strong>;
see the <strong>grops</strong> man page for usage).

<a name="DOCHEADER_CONTROL"><h3><u>How to change the look of docheaders: docheader control macros</u></h3></a>

<p>
With
<a href="#PRINTSTYLE">PRINTSTYLE TYPEWRITE</a>,
the look of docheaders is carved in stone.
In
<a href="#PRINTSTYLE">PRINTSTYLE TYPESET</a>,
however, you can make a lot of changes.  Macros that alter docheaders
MUST come before
<a href="#START">START</a>.
<a name="DOCHEADER_DESC"></a>
<p>
A typeset docheader has the following characteristics.  Note that
title, subtitle, author, and document type are what you supply
with the
<a href="#REFERENCE_MACROS">reference macros</a>.
Any you leave out will not appear; <strong>mom</strong> will
compensate:
<p>
<pre>
	    TITLE         bold, 3.5 points larger than running text (not necessarily caps)
	   Subtitle       medium, same size as running text
	      by          medium italic, same size as running text
	   Author(s)      medium italic, same size as running text

	(Document type)   bold italic, underscored, 3 points larger than running text
</pre>

The
<a href="definitions.html#TERMS_FAMILY">family</a>
is the prevailing family of the whole document.

<h3><u>The docheader macros to:</u></h3>
<ol>
	<li><a href="#CHANGE_START">Change the starting position</a>
	<li><a href="#ADJUST_LEADING">Adjust the leading</a>
	<li><a href="#CHANGE_FAMILY">Change the family of docheader elements</a>
	<li><a href="#CHANGE_FONT">Change the font of docheader elements</a>
	<li><a href="#CHANGE_SIZE">Adjust the size of docheader elements</a>
	<li><a href="#CHANGE_ATTRIBUTE">Change the attribution string (&quot;by&quot;)</a>
</ol>
<p>
<a name="CHANGE_START"><h3><u>1. Change the starting position</u></h3></a>
By default, a docheader starts on the same
<a href="definitions.html#TERMS_BASELINE">baseline</a>
as
<a href="definitions.html#TERMS_RUNNING">running text</a>.
If you'd like it to start somewhere else, use the macro
<kbd>.DOCHEADER_ADVANCE</kbd> and give it the distance you want
(measured from the top edge of the paper to the first baseline
of the docheader), like this:
<p>
<pre>
	.DOCHEADER_ADVANCE 4P
</pre>

A
<a href="definitions.html#TERMS_UNITOFMEASURE">unit of measure</a>
is required.
<p>
<strong>NOTE:</strong> If
<a href="headfootpage.html#HEADERS">HEADERS</a>
are <strong>OFF</strong>, <strong>mom</strong>'s normal top
margin for
<a href="definitions.html#TERMS_RUNNING">running text</a>
(7.5
<a href="definitions.html#TERMS_PICASPOINTS">picas</a>)
changes to 6 picas (visually approx. 1 inch).  Since the
first baseline of the docheader falls on the same baseline
as the first line of running text (on pages after page 1),
you might find the docheaders a bit high when headers are off.
Use
<a href="#CHANGE_START">DOCHEADER_ADVANCE</a>
to place them where you want.


<a name="ADJUST_LEADING"><h3><u>2. Adjust the leading</u></h3></a>
The
<a href="definitions.html#TERMS_LEADING">leading</a> of
docheaders is the same as running text.  If you'd like a
different leading, say, 2 points more than the lead of running
text, use:
<p>
<pre>
	.DOCHEADER_LEAD +2p
</pre>

Since the leading of docheaders is calculated from the lead of running
text, a + or - sign is required before the argument (how much to add
or subtract from the lead of running text).  The
<a href="definitions.html#TERMS_UNITOFMEASURE">unit of measure</a>
is also required.

<a name="CHANGE_FAMILY"><h3><u>3. Change the family of docheader elements</u></h3></a>
The following macros let you change the
<a href="definitions.html#TERMS_FAMILY">family</a>
of each docheader element separately:
<p>
<ul>
<li><strong>TITLE_FAMILY</strong> <var>&lt;family&gt;</var>
<li><strong>SUBTITLE_FAMILY</strong> <var>&lt;family&gt;</var>
<li><strong>AUTHOR_FAMILY</strong> <var>&lt;family&gt;</var>
<li><strong>DOCTYPE_FAMILY</strong> <var>&lt;family&gt;</var> (if
<a href="#DOCTYPE">DOCTYPE</a> is NAMED)
</ul>
<p>
Simply pass the appropriate macro the family you want.

<a name="CHANGE_FONT"><h3><u>4. Change the font of docheader elements</u></h3></a>
The following macros let you change the
<a href="definitions.html#TERMS_FONT">font</a>
of each docheader element separately:
<p>
<ul>
<li><strong>TITLE_FONT</strong> <var>R | B | I | BI</var>
<li><strong>SUBTITLE_FONT</strong> <var>R | B | I | BI</var>
<li><strong>AUTHOR_FONT</strong> <var>R | B | I | BI</var>
<li><strong>DOCTYPE_FONT</strong> <var>R | B | I | BI</var> (if
<a href="#DOCTYPE">DOCTYPE</a> is NAMED)
</ul>
<p>
Simply pass the appropriate macro the font you want.  <strong>R,
B, I</strong> and <strong>BI</strong> have the same meaning as
they do for
<a href="typesetting.html#FONT">FT</a>.


<a name="CHANGE_SIZE"><h3><u>5. Adjust the size of docheader elements</u></h3></a>
The following macros let you adjust the point size of each docheader
element separately.
<p>
<strong>Mom</strong> calculates the point size
of docheader elements from the point size of paragraphs, so you
must prepend a + or - sign to the argument.  Points is
assumed as the
<a href="definitions.html#TERMS_UNITOFMEASURE">unit of measure</a>,
so there's no need to append a unit to the argument.  Fractional point
sizes are allowed.
<p>
<ul>
<li><strong>TITLE_SIZE</strong> <var>&lt;+/-points&gt;</var>
<br>
default = +3.5 (+4 if docheader title is &quot;Chapter #&quot;)
<li><strong>SUBTITLE_SIZE</strong> <var>&lt;+/-points&gt;</var>
<br>
default = +0
<li><strong>AUTHOR_SIZE</strong> <var>&lt;+/-points&gt;</var>
<br>
default = +0
<li><strong>DOCTYPE_SIZE</strong> <var>&lt;+/-points&gt;</var> (if
<a href="#DOCTYPE">DOCTYPE</a> is NAMED)
<br>
default = +3
</ul>
<p>
Simply pass the appropriate macro the size adjustment you want.

<a name="CHANGE_ATTRIBUTE"><h3><u>6. Change the attribution string (&quot;by&quot;)</u></h3></a>
If you're not writing in English, you can change what
<strong>mom</strong> prints where &quot;by&quot; appears in
docheaders.  For example,
<p>
<pre>
	.ATTRIBUTE_STRING "par"
</pre>

changes &quot;by&quot; to &quot;par&quot;.  If you
don't want an attribution string at all, simply pass
<strong>ATTRIBUTE_STRING</strong> an empty argument, like this:
<p>
<pre>
	.ATTRIBUTE_STRING ""
</pre>

<strong>Mom</strong> will deposit a blank line where the
attribution string normally appears.
<p>
<strong>NOTE:</strong> The type specs for the attribution line
in docheaders are the same as for the author line.  Although
it's highly unlikely you'll want the attribution line in a
different family, font, or point size, you can do so by using
<a href="definitions.html#TERMS_INLINES">inline escapes</a>
in the argument to <strong>ATTRIBUTE_STRING</strong>.  For
example,
<p>
<pre>
	.ATTRIBUTE_STRING "\f[HBI]\*S[-2p] by \*S[+2p]\*[PREV]"
</pre>

would set &quot;by&quot; in Helvetica bold italic, 2 points
smaller than normal.
<br>
<hr>

<!---COLUMNS_INTRO--->

<a name="COLUMNS_INTRO"><h2><u>Setting documents in columns</u></h2></a>

<p>
Setting documents in columns is easy with <strong>mom</strong>.  (Of
course she'd say that, but it's true!)  All you have to do is is
say how many columns you want and how much space you want
between them (the
<a href="definitions.html#TERMS_GUTTER">gutters</a>).
That's it. <strong>Mom</strong> takes care of everything else, from
soup to nuts.
<p>
<strong>SOME WORDS OF ADVICE:</strong>
<p>
If you want your type to achieve a pleasing
<a href="definitions.html#TERMS_JUST">justification</a>
or
<a href="definitions.html#TERMS_RAG">rag</a>
in columns, reduce the point size of type (and probably the
<a href="definitions.html#TERMS_LEADING">leading</a>
as well).  <strong>Mom</strong>'s default document point
size is 12.5, which works well across her default 39
<a href="definitions.html#TERMS_PICASPOINTS">pica</a>
full page line length, but with even just two columns on a page,
the default point size is awkward to work with.
<p>
Furthermore, you'll absolutely need to reduce the indents for
<a href="docelement.html#EPIGRAPH_CONTROL">epigraphs</a>,
<a href="docelement.html#QUOTE_GENERAL">quotes</a>,
and
<a href="docelement.html#BLOCKQUOTE_GENERAL">blockquotes</a>
(and probably the
<a href="docelement.html#PARA_INDENT">paragraph first-line indent</a>
as well).
<br>

<!---COLUMNS--->

<hr width="66%" align="left">
<a name="COLUMNS"><h3><u>COLUMNS</u></h3></a>
<br>
Macro: <strong>COLUMNS</strong> <var>&lt;number of columns&gt; &lt;width of gutters&gt;</var>
<br>
<em>*Should be the last macro before START
<br>
The second argument requires a <a href="#TERMS_UNITOFMEASURE">unit of measure</a></em>

<p>
<strong>COLUMNS</strong> takes two arguments: the number of
columns you want on document pages, and the width of the
<a href="definitions.html#TERMS_GUTTER">gutter</a>
between them.  For example, to set up a page with two columns
separated by an 18 point gutter, you'd do
<p>
<pre>
	.COLUMNS 2 18p
</pre>

Nothing to it, really.  However, as noted above,
<strong>COLUMNS</strong> should always be the last document
setup macro prior to
<a href="#START">START</a>.
<p>
<strong>NOTE:</strong> <strong>Mom</strong> ignores columns completely
when the
<a href="#PRINTSTYLE">PRINTSTYLE</a>
is <strong>TYPEWRITE</strong>.	The notion of typewriter-style
output in columns is just too ghastly for her to bear.

<h3><u>Breaking columns manually</u></h3>
<p>
<strong>Mom</strong> takes care of breaking columns when they reach
the bottom margin of a page.  However, there may be times you want to
break the columns yourself.  There are two macros for breaking columns
manually: <strong>COL_NEXT</strong> and <strong>COL_BREAK</strong>.

<a name="COL_NEXT"></a>
<p>
<kbd>.COL_NEXT</kbd> breaks the line just before it,
<a href="definitions.html#TERMS_QUAD">quads</a>
it left (assuming the type is justified or quad left), and moves over
to the top of the next column.  If the column happens to be the last
(rightmost) one on the page, <strong>mom</strong> starts a new page
at the &quot;column 1&quot; position.  This is the macro to use when
you want to start a new column after the end of a paragraph.

<a name="COL_BREAK"></a>
<p>
<kbd>.COL_BREAK</kbd> is almost the same, except that
instead of breaking and quadding the line preceding it,
she breaks and spreads it (see
<a href="typesetting.html#SPREAD">SPREAD</a>).
Use this macro whenever you need to start a new column in the middle
of a paragraph.
<p>
If you need <strong>COL_BREAK</strong> in the middle of a blockquote
or (god help us) an epigraph, you must do the following in order for
<strong>COL_BREAK</strong> to work:
<p>
<pre>
	.SPREAD
	\!.COL_BREAK
</pre>
<hr>

<!========================================================================>

<a name="START_MACRO">
<h2><u>Initiate document processing</u></h2>
</a>

In order to use <strong>mom</strong>'s document element macros
(tags), you have to tell her you want them.  The macro to do this
is <strong>START</strong>.
<p>
<strong>START</strong> collects the information you gave
<strong>mom</strong> in the setup section at the top of your file (see
<a href="#DOCPROCESSING_TUT">Tutorial -- setting up a mom document</a>),
merges it with her defaults, sets up headers and page numbering,
and prepares <strong>mom</strong> to process your document using
the document element tags.  No document processing takes place until
you invoke <strong>START</strong>.
<br>

<!---START--->

<hr width="66%" align="left">
<p>
<a name="START"></a>
Macro: <strong>START</strong>
<br>
<em>*Required for document processing.</em>

<p>
<strong>START</strong> takes no arguments.  It simply instructs
<strong>mom</strong> to begin document processing.  If you don't
want document processing (i.e. you only want the
<a href="typesetting.html#MACROS_TYPESETTING">typesetting macros</a>),
don't use <strong>START</strong>.
<p>
At a barest minimum before <strong>START</strong>, you must enter a
<a href="#PRINTSTYLE">PRINTSTYLE</a>
command.
<br>
<hr>

<!========================================================================>

<a name="DOC_PARAM_MACROS">
<h2><u>Changing document-wide style parameters after START</u></h2>
</a>

In the normal course of things, you change the basic type
parameters of a document <em>before</em>
<a href="#START">START</a>,
using
<a href="typesetting.html#MACROS_TYPESETTING">typesetting macros</a>
(<strong>L_MARGIN, FAMILY, PS, LS,</strong> etc).  After
<strong>START</strong>, you must use the following macros to make
global changes to the basic type parameters of a document.
<br>

<a name="INDEX_DOC_PARAM">
	<h3><u>Macro list</u></h3>
</a>
<ul>
	<li><a href="#DOC_LEFT_MARGIN">DOC_LEFT_MARGIN</a>
	<li><a href="#DOC_RIGHT_MARGIN">DOC_RIGHT_MARGIN</a>
	<li><a href="#DOC_LINE_LENGTH">DOC_LINE_LENGTH</a>
	<li><a href="#DOC_FAMILY">DOC_FAMILY</a>
	<li><a href="#DOC_PT_SIZE">DOC_PT_SIZE</a>
	<li><a href="#DOC_LEAD">DOC_LEAD</a>
	<li><a href="#DOC_LEAD_ADJUST">DOC_LEAD_ADJUST</a>
	<li><a href="#DOC_QUAD">DOC_QUAD</a>
</ul>

<hr width="66%" align="left">
<p>
<a name="DOC_LEFT_MARGIN">
	Macro: <strong>DOC_LEFT_MARGIN</strong> <var>&lt;left margin&gt;</var>
</a>
<br>
<em>*Requires a <a href="definitions.html#TERMS_UNITOFMEASURE">unit of measure</a></em>
<p>
<ul>
	<li>the argument is the same as for
		<a href="typesetting.html#L_MARGIN">L_MARGIN</a>
	<li>changes all left margins to the new value
	<li>the line length remains the same (i.e. the right margin
		shifts when you change the left margin)
</ul>

<br>

<hr width="66%" align="left">
<p>
<a name="DOC_RIGHT_MARGIN">
	Macro: <strong>DOC_RIGHT_MARGIN</strong> <var>&lt;right margin&gt;</var>
</a>
<br>
<em>*Requires a <a href="definitions.html#TERMS_UNITOFMEASURE">unit of measure</a></em>
<p>
<ul>
	<li>the argument is the same as for
		<a href="typesetting.html#R_MARGIN">R_MARGIN</a>
	<li>changes all right margins to the new value
	<li>all mom commands that include a right indent calculate
		the indent from the new value
</ul>
<br>

<hr width="66%" align="left">
<p>
<a name="DOC_LINE_LENGTH">
	Macro: <strong>DOC_LINE_LENGTH</strong> <var>&lt;length&gt;</var>
</a>
<br>
<em>*Requires a <a href="definitions.html#TERMS_UNITOFMEASURE">unit of measure</a></em>
<p>
<ul>
	<li>the argument is the same as for
		<a href="typesetting.html#LL">LL</a>
	<li>equivalent to changing the right margin with DOC_RIGHT_MARGIN
</ul>
<br>

<hr width="66%" align="left">
<p>
<a name="DOC_FAMILY">
	Macro: <strong>DOC_FAMILY</strong> <var>&lt;family&gt;</var>
</a>
<p>
<ul>
	<li>the argument is the same as for
		<a href="typesetting.html#FAMILY">FAMILY</a>
	<li>globally changes the type family
	<li>if you wish the
		<a href="definitions.html#TERMS_HEADER">header</a>
		and/or page number families to remain at their old values,
		you must reset them with
		<a href="headfootpage.html#HEADER_FAMILY">HEADER_FAMILY</a>
		and
		<a href="headfootpage.html#PAGENUM_FAMILY">PAGENUM_FAMILY</a>
</ul>
<br>

<hr width="66%" align="left">
<p>
<a name="DOC_PT_SIZE">
	Macro: <strong>DOC_PT_SIZE</strong> <var>&lt;point size&gt;</var>
</a>
<br>
<em>*Does not require a <a href="definitions.html#TERMS_UNITOFMEASURE">unit of measure</a>; points is assumed</em>
<p>
<ul>
	<li>the argument is the same as for
		<a href="typesetting.html#PS">PS</a>,
		and refers to the point size of type in paragraphs
	<li>all automatic point size changes (heads, quotes,
		footnotes, headers, etc.) are affected by the new size;
		anything you do not want affected must be reset to
		its former value (see the Control Macros section of
		the pertinent document element for instructions on
		how to do this)
</ul>
<br>

<hr width="66%" align="left">
<p>
<a name="DOC_LEAD">
	Macro: <strong>DOC_LEAD</strong> <var>&lt;points&gt; [ ADJUST ]</var>
</a>
<br>
<em>*Does not require a <a href="definitions.html#TERMS_UNITOFMEASURE">unit of measure</a>; points is assumed</em>
<p>
<ul>
	<li>the argument is the same as for
		<a href="typesetting.html#LS">LS</a>,
		and refers to the
		<a href="definitions.html#TERMS_LEAD">leading</a>
		of paragraphs
	<li>because paragraphs will have a new leading, the leading and
		spacing of most running text is influenced by the new value
	<li>epigraphs and footnotes remain unaffected;
		if you wish to change their leading, use
		<a href="docelement.html#EPIGRAPH_AUTOLEAD">EPIGRAPH_AUTOLEAD</a>
		and
		<a href="docelement.html#FOOTNOTE_AUTOLEAD">FOOTNOTE_AUTOLEAD</a>.
	<li>the optional argument <strong>ADJUST</strong> performs
		leading adjustment as explained in
		<a href="#DOC_LEAD_ADJUST">DOC_LEAD_ADJUST</a>
</ul>
<p>
<strong>IMPORTANT:</strong> Do not use <strong>DOC_LEAD</strong>
in the middle of a page!  Always precede it with a manual break
to a new page, like this:
<p>
<pre>
	.NEWPAGE
	.DOC_LEAD &lt;new value&gt;
</pre>

<hr width="66%" align="left">
<p>
<a name="DOC_QUAD">
	Macro: <strong>DOC_QUAD</strong> <var>L | R | C | J</var>
</a>
<p>
<ul>
	<li>the arguments are the same as for
		<a href="typesetting.html#QUAD">QUAD</a>
	<li>affects paragraphs, epigraphs and footnotes; does not
		affect blockquotes
</ul>

<p>
<hr>
<a href="docelement.html#TOP">Next</a>&nbsp;&nbsp;
<a href="inlines.html#TOP">Prev</a>&nbsp;&nbsp;
<a href="#TOP">Top</a>&nbsp;&nbsp;
<a href="toc.html">Back to Table of Contents</a>
</body>
</html>