1 02/15/80 dot_page.compin, dot_page_off.compin
2
3 Syntax: .srv add_date "publish_date"
4 .srv add_letter "what_addendum"
5 .ifi dot_page what_addendumblank_page
6 and at the top of the page where normal page counting resumes
7 .ifi dot_page_off
8 .srv add_date "" see Notes
9 .srv add_letter ""
10
11
12 Function:
13 The dot_page macro creates addendum footer lines when composed. It
14 1) turns on the date and addendum letter portion of the footers
15 2) turns on an automatic counter for 'point' pages
16 3) generates blank 'backup' pages if necessary see Notes
17
18 The dot_page_off macro restores the page counter to the counting
19 sequence in effect before the dot_page macro was called. BEWARE! These
20 macros cause page breaks.
21
22
23 Arguments:
24 'publish_date' is the month and year, in the form mm/yy e.g. 10/20,
25 that this addendum is published generally 'published' here means
26 'brought to the printer'. Leading zeros are not used, so a publish
27 date of August 1978 would be 8/78 not 08/78.
28 'what_addendum' is a single capital letter, indicating which addendum
29 this is i.e. A is the first addendm; B second; etc.. The value
30 assigned to 'add_letter' appears in the page footer and the value
31 given in the call to 'dot_page' is used for changed page selection.
32 'blank_page' may be any non-blank character to indicate that a needed
33 blank page see Notes should precede the added 'point' pages. If
34 no 'blank_page' character is given, the blank page follows the point
35 pages. This feature allows the user to avoid the facing blank
36 pages that are usually considered not good practice.
37
38
39 Notes:
40 1) In order to add addendum pages, knowledge of the current and correct
41 placement of all text on the pages involved is necessary. Also,
42 keep in mind that use of either of these macros forces a new page so
43 placement of the dot_page macro call line is crucial.
44 2) The use of the two '.srv' lines following the dot_page_off call line
45 is shown as optional. If the page following the desired 'point'
46 pages contains change bars, the '.srv' lines should not be given;
47 if it does not contain change bars, they should be given so that a
48 possible obverse unmodified page will have a proper footer.
49 3) The dot_page macro assumes that the material will be submitted for
50 printing and therefore both sides of the printed page must be
51 considered. If a blank page is required, it is labeled as such
52 "This page intentionally left blank." and the proper addendum
53 footers without a page number are generated.
54
55
56 Examples:
57 Assume compose encounters the following lines in the compin segment
58 as it is formatting the twelfth page of the section numbered either
59 12 or <section_number>-12.
60
61 .srv add_date "8/78"
62 .srv add_letter "B"
63 .ifi dot_page B
64
65 These lines add the addendum publish date in the left side of the
66 footer; add the addendum letter to the order number in the footer;
67 turn on the point page page number counter so the next page number
68 is 12.1, next is 12.2, etc. or <section_number>-12.1
69 <section_number>-12.2 etc. if you have put in a '.srv section
70 <section_number>' line earlier; and, if a blank backup page is
71 needed, put it at the end of the point pages.
72
73
74 .ifi dot_page_off
75
76 turns off the point page counter and returns to normal page numbers
77 so the next page number is 13 or <section_number>-13. Since the
78 add_date and add_letter values were not reset, the footer will
79 continue to show those value.
80
81 If the following lines are encountered in the compin segment as the
82 twelfth page is being formatted
83
84 .srv add_date "8/78"
85 .srv add_letter "B"
86 .ifi dot_page B,x
87
88 compose generates formatted pages exactly as the example above
89 except a blank page will precede the point pages.
90
91 END