head 1.2; access; symbols perseant-exfatfs-base-20250801:1.2 perseant-exfatfs-base-20240630:1.2 cjep_sun2x:1.2.0.14 cjep_sun2x-base:1.2 cjep_staticlib_x-base1:1.2 cjep_staticlib_x:1.2.0.12 cjep_staticlib_x-base:1.2 phil-wifi-20200421:1.2 phil-wifi-20200411:1.2 phil-wifi-20200406:1.2 pgoyette-compat-merge-20190127:1.2 pgoyette-compat-20190127:1.2 pgoyette-compat-20190118:1.2 pgoyette-compat-1226:1.2 pgoyette-compat-1126:1.2 pgoyette-compat-1020:1.2 pgoyette-compat-0930:1.2 pgoyette-compat-0906:1.2 netbsd-7-2-RELEASE:1.1.1.3 pgoyette-compat-0728:1.2 pgoyette-compat-0625:1.2 pgoyette-compat-0521:1.2 pgoyette-compat-0502:1.2 pgoyette-compat-0422:1.2 pgoyette-compat-0415:1.2 pgoyette-compat-0407:1.2 pgoyette-compat-0330:1.2 pgoyette-compat-0322:1.2 pgoyette-compat-0315:1.2 netbsd-7-1-2-RELEASE:1.1.1.3 pgoyette-compat:1.2.0.10 pgoyette-compat-base:1.2 netbsd-7-1-1-RELEASE:1.1.1.3 perseant-stdc-iso10646:1.2.0.8 perseant-stdc-iso10646-base:1.2 prg-localcount2-base3:1.2 prg-localcount2-base2:1.2 prg-localcount2-base1:1.2 prg-localcount2:1.2.0.6 prg-localcount2-base:1.2 pgoyette-localcount-20170426:1.2 bouyer-socketcan-base1:1.2 pgoyette-localcount-20170320:1.2 netbsd-7-1:1.1.1.3.0.68 netbsd-7-1-RELEASE:1.1.1.3 netbsd-7-1-RC2:1.1.1.3 netbsd-7-nhusb-base-20170116:1.1.1.3 bouyer-socketcan:1.2.0.4 bouyer-socketcan-base:1.2 pgoyette-localcount-20170107:1.2 netbsd-7-1-RC1:1.1.1.3 pgoyette-localcount-20161104:1.2 netbsd-7-0-2-RELEASE:1.1.1.3 localcount-20160914:1.2 netbsd-7-nhusb:1.1.1.3.0.66 netbsd-7-nhusb-base:1.1.1.3 pgoyette-localcount-20160806:1.2 pgoyette-localcount-20160726:1.2 pgoyette-localcount:1.2.0.2 pgoyette-localcount-base:1.2 netbsd-7-0-1-RELEASE:1.1.1.3 netbsd-7-0:1.1.1.3.0.64 netbsd-7-0-RELEASE:1.1.1.3 netbsd-7-0-RC3:1.1.1.3 netbsd-7-0-RC2:1.1.1.3 netbsd-7-0-RC1:1.1.1.3 netbsd-5-2-3-RELEASE:1.1.1.3 netbsd-5-1-5-RELEASE:1.1.1.3 netbsd-6-0-6-RELEASE:1.1.1.3 netbsd-6-1-5-RELEASE:1.1.1.3 netbsd-7:1.1.1.3.0.62 netbsd-7-base:1.1.1.3 yamt-pagecache-base9:1.1.1.3 yamt-pagecache-tag8:1.1.1.3 netbsd-6-1-4-RELEASE:1.1.1.3 netbsd-6-0-5-RELEASE:1.1.1.3 tls-earlyentropy:1.1.1.3.0.60 tls-earlyentropy-base:1.1.1.3 riastradh-xf86-video-intel-2-7-1-pre-2-21-15:1.1.1.3 riastradh-drm2-base3:1.1.1.3 netbsd-6-1-3-RELEASE:1.1.1.3 netbsd-6-0-4-RELEASE:1.1.1.3 netbsd-5-2-2-RELEASE:1.1.1.3 netbsd-5-1-4-RELEASE:1.1.1.3 netbsd-6-1-2-RELEASE:1.1.1.3 netbsd-6-0-3-RELEASE:1.1.1.3 netbsd-5-2-1-RELEASE:1.1.1.3 netbsd-5-1-3-RELEASE:1.1.1.3 netbsd-6-1-1-RELEASE:1.1.1.3 riastradh-drm2-base2:1.1.1.3 riastradh-drm2-base1:1.1.1.3 riastradh-drm2:1.1.1.3.0.54 riastradh-drm2-base:1.1.1.3 netbsd-6-1:1.1.1.3.0.58 netbsd-6-0-2-RELEASE:1.1.1.3 netbsd-6-1-RELEASE:1.1.1.3 netbsd-6-1-RC4:1.1.1.3 netbsd-6-1-RC3:1.1.1.3 agc-symver:1.1.1.3.0.56 agc-symver-base:1.1.1.3 netbsd-6-1-RC2:1.1.1.3 netbsd-6-1-RC1:1.1.1.3 yamt-pagecache-base8:1.1.1.3 netbsd-5-2:1.1.1.3.0.52 netbsd-6-0-1-RELEASE:1.1.1.3 yamt-pagecache-base7:1.1.1.3 netbsd-5-2-RELEASE:1.1.1.3 netbsd-5-2-RC1:1.1.1.3 matt-nb6-plus-nbase:1.1.1.3 yamt-pagecache-base6:1.1.1.3 netbsd-6-0:1.1.1.3.0.50 netbsd-6-0-RELEASE:1.1.1.3 netbsd-6-0-RC2:1.1.1.3 tls-maxphys:1.1.1.3.0.48 tls-maxphys-base:1.1.1.3 matt-nb6-plus:1.1.1.3.0.46 matt-nb6-plus-base:1.1.1.3 netbsd-6-0-RC1:1.1.1.3 yamt-pagecache-base5:1.1.1.3 yamt-pagecache-base4:1.1.1.3 netbsd-6:1.1.1.3.0.44 netbsd-6-base:1.1.1.3 netbsd-5-1-2-RELEASE:1.1.1.3 netbsd-5-1-1-RELEASE:1.1.1.3 yamt-pagecache-base3:1.1.1.3 yamt-pagecache-base2:1.1.1.3 yamt-pagecache:1.1.1.3.0.42 yamt-pagecache-base:1.1.1.3 cherry-xenmp:1.1.1.3.0.40 cherry-xenmp-base:1.1.1.3 bouyer-quota2-nbase:1.1.1.3 bouyer-quota2:1.1.1.3.0.38 bouyer-quota2-base:1.1.1.3 matt-mips64-premerge-20101231:1.1.1.3 matt-nb5-mips64-premerge-20101231:1.1.1.3 matt-nb5-pq3:1.1.1.3.0.36 matt-nb5-pq3-base:1.1.1.3 netbsd-5-1:1.1.1.3.0.34 netbsd-5-1-RELEASE:1.1.1.3 netbsd-5-1-RC4:1.1.1.3 matt-nb5-mips64-k15:1.1.1.3 netbsd-5-1-RC3:1.1.1.3 netbsd-5-1-RC2:1.1.1.3 netbsd-5-1-RC1:1.1.1.3 netbsd-5-0-2-RELEASE:1.1.1.3 matt-nb5-mips64-premerge-20091211:1.1.1.3 matt-premerge-20091211:1.1.1.3 matt-nb5-mips64-u2-k2-k4-k7-k8-k9:1.1.1.3 matt-nb4-mips64-k7-u2a-k9b:1.1.1.3 matt-nb5-mips64-u1-k1-k5:1.1.1.3 matt-nb5-mips64:1.1.1.3.0.32 netbsd-5-0-1-RELEASE:1.1.1.3 jym-xensuspend-nbase:1.1.1.3 netbsd-5-0:1.1.1.3.0.30 netbsd-5-0-RELEASE:1.1.1.3 netbsd-5-0-RC4:1.1.1.3 netbsd-5-0-RC3:1.1.1.3 netbsd-5-0-RC2:1.1.1.3 jym-xensuspend:1.1.1.3.0.28 jym-xensuspend-base:1.1.1.3 netbsd-5-0-RC1:1.1.1.3 netbsd-5:1.1.1.3.0.26 netbsd-5-base:1.1.1.3 matt-mips64-base2:1.1.1.3 matt-mips64:1.1.1.3.0.24 mjf-devfs2:1.1.1.3.0.22 mjf-devfs2-base:1.1.1.3 netbsd-4-0-1-RELEASE:1.1.1.3 wrstuden-revivesa-base-3:1.1.1.3 wrstuden-revivesa-base-2:1.1.1.3 wrstuden-fixsa-newbase:1.1.1.3 wrstuden-revivesa-base-1:1.1.1.3 yamt-pf42-base4:1.1.1.3 yamt-pf42-base3:1.1.1.3 hpcarm-cleanup-nbase:1.1.1.3 yamt-pf42-baseX:1.1.1.3 yamt-pf42-base2:1.1.1.3 wrstuden-revivesa:1.1.1.3.0.20 wrstuden-revivesa-base:1.1.1.3 yamt-pf42:1.1.1.3.0.18 yamt-pf42-base:1.1.1.3 keiichi-mipv6:1.1.1.3.0.16 keiichi-mipv6-base:1.1.1.3 matt-armv6-nbase:1.1.1.3 matt-armv6-prevmlocking:1.1.1.3 wrstuden-fixsa-base-1:1.1.1.3 netbsd-4-0:1.1.1.3.0.14 netbsd-4-0-RELEASE:1.1.1.3 cube-autoconf:1.1.1.3.0.12 cube-autoconf-base:1.1.1.3 netbsd-4-0-RC5:1.1.1.3 netbsd-4-0-RC4:1.1.1.3 netbsd-4-0-RC3:1.1.1.3 netbsd-4-0-RC2:1.1.1.3 netbsd-4-0-RC1:1.1.1.3 matt-armv6:1.1.1.3.0.10 matt-armv6-base:1.1.1.3 matt-mips64-base:1.1.1.3 hpcarm-cleanup:1.1.1.3.0.8 hpcarm-cleanup-base:1.1.1.3 netbsd-3-1-1-RELEASE:1.1.1.2 netbsd-3-0-3-RELEASE:1.1.1.2 wrstuden-fixsa:1.1.1.3.0.6 wrstuden-fixsa-base:1.1.1.3 abandoned-netbsd-4-base:1.1.1.3 abandoned-netbsd-4:1.1.1.3.0.2 netbsd-3-1:1.1.1.2.0.6 netbsd-3-1-RELEASE:1.1.1.2 netbsd-3-0-2-RELEASE:1.1.1.2 netbsd-3-1-RC4:1.1.1.2 netbsd-3-1-RC3:1.1.1.2 netbsd-3-1-RC2:1.1.1.2 netbsd-3-1-RC1:1.1.1.2 netbsd-4:1.1.1.3.0.4 netbsd-4-base:1.1.1.3 netbsd-3-0-1-RELEASE:1.1.1.2 groff-1-19-2:1.1.1.3 netbsd-3-0:1.1.1.2.0.4 netbsd-3-0-RELEASE:1.1.1.2 netbsd-3-0-RC6:1.1.1.2 netbsd-3-0-RC5:1.1.1.2 netbsd-3-0-RC4:1.1.1.2 netbsd-3-0-RC3:1.1.1.2 netbsd-3-0-RC2:1.1.1.2 netbsd-3-0-RC1:1.1.1.2 netbsd-2-0-3-RELEASE:1.1.1.1 netbsd-2-1:1.1.1.1.0.6 netbsd-2-1-RELEASE:1.1.1.1 netbsd-2-1-RC6:1.1.1.1 netbsd-2-1-RC5:1.1.1.1 netbsd-2-1-RC4:1.1.1.1 netbsd-2-1-RC3:1.1.1.1 netbsd-2-1-RC2:1.1.1.1 netbsd-2-1-RC1:1.1.1.1 netbsd-2-0-2-RELEASE:1.1.1.1 netbsd-3:1.1.1.2.0.2 netbsd-3-base:1.1.1.2 netbsd-2-0-1-RELEASE:1.1.1.1 netbsd-2:1.1.1.1.0.4 netbsd-2-base:1.1.1.1 netbsd-2-0-RELEASE:1.1.1.1 netbsd-2-0-RC5:1.1.1.1 netbsd-2-0-RC4:1.1.1.1 netbsd-2-0-RC3:1.1.1.1 netbsd-2-0-RC2:1.1.1.1 netbsd-2-0-RC1:1.1.1.1 groff-1-19-1:1.1.1.2 netbsd-2-0:1.1.1.1.0.2 netbsd-2-0-base:1.1.1.1 groff-1-19:1.1.1.1 FSF:1.1.1; locks; strict; comment @# @; 1.2 date 2016.01.13.19.25.00; author christos; state dead; branches; next 1.1; commitid Y4vhQ1Aj99QZ0OQy; 1.1 date 2003.06.30.17.51.46; author wiz; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2003.06.30.17.51.46; author wiz; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2004.07.30.14.44.32; author wiz; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2006.02.06.18.11.32; author wiz; state Exp; branches; next ; desc @@ 1.2 log @groff has moved to external @ text @ Mom -- Document processing, creating a cover page Next   Prev   Back to Table of Contents

CREATING A COVER PAGE

At present, mom provides no mechanism for automatically generating cover pages. It's a situation not likely to change, given that what's needed on document covers changes from document to document, both in terms of style and content. And, more often than not, what goes on covers is matter of personal taste.

If you want a document to begin with a cover page, typeset the cover (using the typesetting macros). At the end, invoke NEWPAGE, then set up your document in full (see Tutorial -- Setting up a mom document), invoking START as usual once you're done. The cover page (and any typesetting commands on it) will have no effect on mom's processing of the document itself, the first page of which, moreover, will be numbered "1" unless you instruct her otherwise with PAGENUMBER.


Next   Prev   Top   Back to Table of Contents @ 1.1 log @Initial revision @ text @@ 1.1.1.1 log @Import groff-1.19. Changes since 1.16.1: too many to list here (> 1000 lines in the abridged version). Please read the included NEWS file for details. @ text @@ 1.1.1.2 log @Import groff-1.19.1. Changes since 1.19: Groff ----- o The argument of the command line option `-I' is now also passed to troff and grops, specifying a directory to search for files on the command line, files named in `so' and `psbb' requests, and files named in \X'ps: file' and \X'ps: import' escapes. o If option `-V' is used more than once, the commands will be both printed on standard error and run. Troff ----- o Two new read-only, string-valued registers `.m' and `.M' return the name of the current drawing and background color, respectively. o New read-only register `.U' which is set to 1 if in safer mode and set to 0 if in unsafe mode. o An input encoding file for latin-5 (a.k.a. ISO 8859-9) has been added. Example use: groff -Tdvi -mlatin5 my_file > my_file.dvi Note that some output devices don't support all glyphs of this encoding. o If the `return' request is called with an argument, it exits twice, namely the current macro and the macro one level higher. This is used to define a wrapper macro for `return' in trace.tmac. o For completeness, two new requests have been added: `dei1' and `ami1'. They are equivalent to `dei' and `ami', respectively, but the macros are executed with compatibility mode off (similar to `de1' and `am1'). o New command line option `-I' to specify a directory for files (both those on the command line and those named in `psbb' requests). This is also handled by the groff wrapper program. o Since version 1.19 you can say `.vs 0'. Older versions emit a warning and convert this to `.vs \n[.V]'. This hasn't been documented properly. Note that `.vs 0' isn't saved in a diversion since it doesn't result in vertical motion. Pic ___ o Dashed and dotted ellipses have been implemented. Tbl --- o New key character `x' to make tbl call a user-defined macro on a table cell. Patch by Heinz-Jürgen Oertel . Grohtml ------- o New option `-j' to emit output splitted into multiple files. Grops ----- o New command line option `-I' to specify a directory to search for files on the command line and files named in \X'ps: import' and \X'ps: file' escapes. This is also handled by the groff wrapper program. o The default value for the `broken' keyword in the DESC file is now 0. Grolj4 ------ o A new man page `lj4_font(5)' documents how fonts are accessed with grolj4. o The built-in fonts for LJ4 and newer PCL 5 devices have been completely revised, mainly to access as much glyphs as possible. The provided metric files should be compatible with recent PCL 5 printers also. Additionally, font description files have been added for the Arial and Times New Roman family, the MS symbol, and Wingdings fonts. Hpftodit -------- o Completely revised to handle HP TrueType metric files also. See the hpftodit manual page for more details. Macro Packages -------------- o www.tmac: New macro `JOBNAME' to split output into multiple files. o In mdoc, multiple calls to `.Lb' are now supported in the LIBRARY section. @ text @a12 1

d16 1 a16 1

CREATING A COVER PAGE

@ 1.1.1.3 log @Import groff 1.19.2 @ text @a0 1 d10 1 a10 1 Next   d15 3 a17 2

CREATING A COVER PAGE

a19 83

Introduction to cover pages

As of version 1.19 of mom, you can now have cover pages generated automatically.

Though identical in treatment, mom provides two kinds of cover pages: section cover pages (which I shall refer to simply as "cover pages") and document cover pages ("doc covers").

A document cover page (doc cover) is what you'd most likely use at the start of a collated document, where you might want the name of the complete document, the author(s) and the copyright line to appear. Another place you might use a doc cover is for a novel, where you want the title of the novel, not the chapter title or chapter number, as the first cover page.

A section cover page is what you'd use for cover pages that separate sections of a collated document. A section cover page (but not a doc cover page) in a collated document could, for example, simply read "PART I".

In non-collated documents (say, an essay) you can use either a section cover or a doc cover to generate a cover sheet.

In addition, nothing prevents you from generating both a doc cover page and a section cover page for every document in a collated document. Or you can selectively disable the automatic generation of either doc covers or section covers in a collated document, on-the-fly.

Important note: automatic generation of cover or doc cover pages after the first one(s) only takes place if you are working with collated documents. Mom provides no mechanism for saying "print a section cover here even though I'm still working on the same (non-collated) document."

Description of what mom does on cover pages

By default, mom typesets cover (and doc cover) pages identically to docheaders (see How to change the look of docheaders for a description of what a docheader looks like). The only differences are
d21 10 a30 61 You tell mom what you want to appear on the cover pages through the arguments you pass to COVER and/or DOC_COVER. Provided you have already given mom the appropriate references macro (e.g. TITLE or AUTHOR), she will output cover (and doc cover) pages identically to how she would output docheaders containing the same information.

By default, mom starts cover (and doc cover) pages one-third of the way down the page. This can be changed through the use of the control macros COVER_ADVANCE/DOC_COVER_ADVANCE.

If you request copyright information (and have already given mom the reference macro, COPYRIGHT), she sets it, by default, in a smaller point size in the bottom right hand corner of the cover (or doc cover) page. The default point size and the position can be controlled with COVER_COPYRIGHT_SIZE/DOC_COVER_COPYRIGHT_SIZE and COVER_COPYRIGHT_QUAD/DOC_COVER_COPYRIGHT_QUAD.

Similarly, if you request miscellaneous information (and have already given mom the reference macro, MISC), she sets it, by default, in a smaller point size in the bottom left hand corner of the cover (or doc cover) page. The default point size is dependent on COVER_COPYRIGHT_SIZE/DOC_COVER_COPYRIGHT_SIZE, but the position can be controlled with COVER_MISC_QUAD/DOC_COVER_MISC_QUAD.

NOTE: mom does not set any headers or footers on cover pages. Neither does she set any page numbers. From the point of pagination, cover (and doc cover) pages are considered "null" pages; if you wish them to be included in the pagination scheme (even though no page numbers appear), you must set the page number of each first page following a COLLATE manually with PAGENUMBER.

Finally, if you want to design your own cover page(s), you can always typeset them (using the typesetting macros), invoke d32 1 a32 1 set up your document in full (see d34 7 a40 6 and lastly invoke START. The cover page (and any typesetting commands on it) will have no effect on mom's processing of the document itself, the first page of which, moreover, will be numbered "1" unless you instruct her otherwise with a41 329


Macro: COVER
Macro: DOC_COVER
Required argument: TITLE | DOCTITLE | COVERTITLE | CHAPTER | CHAPTER_TITLE | CHAPTER+TITLE
Optional arguments: [ SUBTITLE AUTHOR DOCTYPE COPYRIGHT MISC ]

*Note: these macros should be placed in the "style-sheet" section of your document setup (see the Tutorial -- Setting up a mom document), i.e. after PRINTSTYLE (and/or DOCTYPE and/or COPYSTYLE), but before START.

COVER and DOC_COVER behave identically. The reason mom provides two macros for automatic cover page generation is so that you can have two different kinds of covers with different information on each.

Imagine, for a moment, you've written a document comprised of three sections. When you COLLATE the document for output, you could use DOC_COVER to generate a cover page that contained the name of the entire document, your (the author's) name, and perhaps the copyright date. Subsequently, you could use COVER, after each COLLATE but before each START, to generate a cover page (or cover "sheet", if you prefer) containing just the name of the section.

The required argument

Both COVER and DOC_COVER, whenever invoked, require a first argument, as listed above. This first argument will become the first bit of information mom prints on the cover (or doc cover) page (i.e. it will be the "title").

In order for the information to appear, you must, of course, first have given mom the appropriate reference macro. A list of arguments with their equivalent reference macros follows.

TITLE
-means the argument you gave to TITLE
DOCTITLE
-means the argument you gave to DOCTITLE
COVERTITLE
-means the argument you gave to COVERTITLE or DOC_COVERTITLE
CHAPTER, CHAPTER_TITLE, CHAPTER+TITLE
-see below (How the CHAPTER argument and friends work)

How the CHAPTER argument and friends work

CHAPTER, by itself, will print the CHAPTER_STRING as well as the chapter number that you gave to CHAPTER. For example, assuming a vanilla setup for your chapter

	\# Reference macros
	.CHAPTER 1
	.CHAPTER_TITLE "The Bonny Blue Yonder"
	<other stuff>
	.COVER CHAPTER \" (or .DOC_COVER CHAPTER)
	.START
will simply print

	Chapter 1
CHAPTER_TITLE will print the chapter title you gave to CHAPTER_TITLE. For example, assuming a vanilla setup for your chapter

	\# Reference macros
	.CHAPTER 1
	.CHAPTER_TITLE "The Bonny Blue Yonder"
	<other stuff>
	.COVER CHAPTER_TITLE \" (or .DOC_COVER CHAPTER_TITLE)
	.START
will simply print

	The Bonny Blue Yonder

CHAPTER+TITLE will print both the chapter string + number AND the chapter title. For example, assuming a vanilla setup for your chapter

	\# Reference macros
	.CHAPTER 1
	.CHAPTER_TITLE "The Bonny Blue Yonder"
	<other stuff>
	.COVER CHAPTER+TITLE \" (or .DOC_COVER CHAPTER+TITLE)
	.START
will print

	      Chapter 1
	The Bonny Blue Yonder

The optional arguments

The remainder of the arguments to COVER and DOC_COVER are optional. They refer specifically to the information you gave the reference macros bearing the same name as the arguments.

You may enter as many or as few as you would like to see on your cover (or doc cover) page. The only hitch is--PAY ATTENTION, CLASS!--they must be entered in the order given above. For example, if you want TITLE, AUTHOR, COPYRIGHT and MISC

	.COVER TITLE AUTHOR COPYRIGHT MISC
is correct, while

	.COVER TITLE AUTHOR MISC COPYRIGHT
is not.

What the DOCTYPE argument means

When you pass COVER or DOC_COVER the argument, DOCTYPE, it refers to the argument you gave to DOCTYPE NAMED. For example, if, in your docstyle macros you gave a

	.DOCTYPE NAMED "Abstract"
the argument, DOCTYPE, in the COVER or DOC_COVER macros, would mean that you wanted the word, Abstract, to appear on the cover (or doc cover), just as it would in the docheader.

Macro: COVERS <toggle>
Macro: DOC_COVERS <toggle>

By default, if you give mom a COVER or DOC_COVER macro, she will print it. In a document that contains sections, articles or chapters formerly treated as "one-off's" but now being collated, such behaviour may not be desirable.

Mom lets you selectively enable or disable the generation of covers and/or doc covers with the toggle macros COVERS and DOC_COVERS. Because they're toggle macros, simply invoking them by themselves enables automatic cover (or doc cover) generation, while invoking them with any argument at all (OFF, QUIT, X, etc) disables cover (or doc cover) generation.

NOTE: You must place these macros prior to any instance of START. Since they're "on" by default, there's no need to use them if you want covers. However, if you don't, especially in the kind of scenario described above, the best place to put them (most likely with an OFF, NO, X, etc. argument), is immediately after the first invocation of START. By doing so, you ensure they precede all subsequent instances of START.


Control macros--changing the defaults for covers and document covers

The default typographic appearance of the items on a cover (or doc cover) page is identical to that of the items in a docheader. (See How to change the look of docheaders for a description of the defaults.)

COPYRIGHT and MISC, which do not appear in docheaders, have the following default characteristics:

  1. The copyright line is set in the bottom right hand corner of the page, 2 point sizes smaller than the size of running text
  2. The "misc" line is set in the bottom left hand corner of the page, in the same family, font and point size as the copyright line.

With the exception of the copyright and "misc" lines, the defaults for the entirety of cover (and doc cover) pages, and all the elements thereon, can be changed with control macros whose behaviour and arguments are identical to the control macros used for docheaders. The only difference is the name by which you invoke the control macro(s).

The complete list of cover (and doc cover) page control macros follows; please refer to the docheader control macros index in order to understand how to use them.

Index of cover and doc cover control macros

.COVER_ADVANCE  .DOC_COVER_ADVANCE -+
.COVER_FAMILY   .DOC_COVER_FAMILY   | like DOCHEADER_
.COVER_LEAD     .DOC_COVER_LEAD    -+

.COVER_TITLE_FAMILY  .DOC_COVER_TITLE_FAMILY -+
.COVER_TITLE_FONT    .DOC_COVER_TITLE_FONT    | like
.COVER_TITLE_COLOR   .DOC_COVER_TITLE_COLOR   | TITLE_
.COVER_TITLE_SIZE    .DOC_COVER_TITLE_SIZE   -+

.COVER_CHAPTER_TITLE_FAMILY  .DOC_COVER_CHAPTER_TITLE_FAMILY -+
.COVER_CHAPTER_TITLE_FONT    .DOC_COVER_CHAPTER_TITLE_FONT    | like
.COVER_CHAPTER_TITLE_COLOR   .DOC_COVER_CHAPTER_TITLE_COLOR   | CHAPTER_TITLE_
.COVER_CHAPTER_TITLE_SIZE    .DOC_COVER_CHAPTER_TITLE_SIZE   -+

.COVER_SUBTITLE_FAMILY  .DOC_COVER_SUBTITLE_FAMILY -+
.COVER_SUBTITLE_FONT    .DOC_COVER_SUBTITLE_FONT    | like
.COVER_SUBTITLE_COLOR   .DOC_COVER_SUBTITLE_COLOR   | SUBTITLE_
.COVER_SUBTITLE_SIZE    .DOC_COVER_AUTHOR_SIZE     -+

.COVER_ATTRIBUTE_COLOR  .DOC_COVER_ATTRIBUTE_COLOR - like ATTRIBUTE_COLOR
 - the macro, .ATTRIBUTE_STRING, controls the attribution string
   for both docheaders and cover pages; cover pages have no
   separate ATTRIBUTE_STRING macro

.COVER_AUTHOR_FAMILY  .DOC_COVER_AUTHOR_FAMILY -+
.COVER_AUTHOR_FONT    .DOC_COVER_AUTHOR_FONT    | like
.COVER_AUTHOR_COLOR   .DOC_COVER_AUTHOR_COLOR   | AUTHOR_
.COVER_AUTHOR_SIZE    .DOC_COVER_AUTHOR_SIZE   -+

.COVER_DOCTYPE_FAMILY  .DOC_COVER_DOCTYPE_FAMILY -+
.COVER_DOCTYPE_FONT    .DOC_COVER_DOCTYPE_FONT    | like
.COVER_DOCTYPE_COLOR   .DOC_COVER_DOCTYPE_COLOR   | DOCTYPE_
.COVER_DOCTYPE_SIZE    .DOC_COVER_DOCTYPE_SIZE   -+

.COVER_COPYRIGHT_FAMILY  .DOC_COVER_COPYRIGHT_FAMILY -+
.COVER_COPYRIGHT_FONT    .DOC_COVER_COPYRIGHT_FONT    | like any
.COVER_COPYRIGHT_COLOR   .DOC_COVER_COPYRIGHT_COLOR   | of the above
.COVER_COPYRIGHT_SIZE    .DOC_COVER_COPYRIGHT_SIZE   -+
.COVER_COPYRIGHT_QUAD    .DOC_COVER_COPYRIGHT_QUAD
 - the copyright quad can be either L (left) or R (right); default is left

.COVER_MISC_COLOR  .DOC_COVER_MISC_COLOR - like any of the above _COLOR
.COVER_MISC_QUAD   .DOC_COVER_MISC_QUAD
 - the misc quad can be either L (left) or R (right); default is right
Note: COVER_MISC and DOC_COVER_MISC have only two control macros, _COLOR and _QUAD. The family, font and size of the MISC argument to COVER or DOC_COVER are always the same as for COPYRIGHT. Should you wish the family, font or size to be different from COPYRIGHT, I suggest setting the type specs for COPYRIGHT to the ones you want for MISC, then altering them for COPYRIGHT using inline escapes in the string argument you pass to the macro, COPYRIGHT. (Of course, you could always do the reverse, but if you pass several arguments to MISC, it's more likely you want to get MISC right first.) d45 1 a45 1 Next   @