|
|
1.1 root 1: .bp
2: .sh 1 "Invoking the Programs"
3: .lp
4: All of the programs provided with this toolkit have associated ``man''
5: pages for easy reference. A short overview of each is also provided below:
6: .sh 2 "maha"
7: .lp
8: This program treats the laser printer as a line-printer.
9: Normally, it uses a fixed-width font so that columns will line up.
10: Options are provided to change the font, provide two-column output
11: and print landscape (rotated) output.
12: .sh 2 "charset"
13: .lp
14: This program prints a character set of a specific font in a given point
15: size. Since the Xerox Character Encoding Standard has a very sparse
16: space of characters, it's handy to know exactly which characters your
17: printer can print.
18: .sh 2 "iptotext and texttoip"
19: .lp
20: \*(IP files are binary encoded files and thus are somewhat inconvient to
21: examine. There is a parallel representation to \*(IP called Intertext which is
22: a textual representation. Since the mapping is one-to-one, \*(IP files
23: can be converted to Intertext files and back again without loss of information.
24: The actual syntax of Intertext is documented in Section 5 of this document.
25: .lp
26: The programs iptotext and texttoip convert between these two representations
27: in the obvious way. Converting to Intertext is a handy way to debug
28: \*(IP files that are constructed using the C language interface described
29: in Section 4. Intertext also provides a way for knowledgable people
30: to edit \*(IP files. For example, it was used to debug \*(TR changes intended
31: to remove the cut-marks inserted by the standard 4.2BSD macros.
32: .sh 2 "iptroff and dipress"
33: .lp
34: The shell script ``iptroff\|'' is simply a front-end for TI-\*(TR and dipress.
35: Only under special circumstances will one need to invoke dipress directly.
36: In general, one invokes iptroff just as regular \*(TR would be used.
37: For example:
38: .(l
39: iptroff \-me foo.me
40: .)l
41: .lp
42: Remember, that many pre-processors such as eqn and pic
43: need to know which output device you intend to use. When using iptroff,
44: specifiy the ``\-Tip'' switch.
45: .sh 2 "restotext and stackres"
46: .lp
47: RES is Xerox's Raster Encoding Standard. It is used as a way of transmitting
48: and exchanging image data. The program ``restotext'' converts an RES file
49: to a textual represtation and a manner similar to iptotext. Stackres
50: executes the RES file (an RES file is similar to an \*(IP file) and
51: prints out what is left on the stack.
52: .sh 2 "ipmetrics"
53: .lp
54: The \*(IP standard specifies that fonts metrics (like widths of characters)
55: are distributed in the form of an \*(IP file which when executed leaves various
56: vectors on the stack. These vectors are property lists which contain
57: various pieces of information about the fonts. The program ``ipmetrics''
58: will execute an \*(IP master and with the aid of various description
59: files, produce metrics for \*(TR.
60: .sh 3 "Fonts"
61: .lp
62: In order to be compatible with the C/A/T phototypsetter, there are the
63: standard four fonts: R, B, I and S. The fonts provided with
64: this distribution have all the characters that the C/A/T had as well as
65: many new special characters. These are documented in Appendix \f(RN2\fR.
66: Because \*(TR has a restriction of only 221 special character names,
67: it was not possible to give all the special characters unique names.
68: The overflow characters were placed in three (3) pseudo-fonts as follows:\(dg
69: .(f
70: .ti -\n(fiu
71: \(dgThey are pseudo-fonts in the sense that although \*(TR thinks
72: they are separate fonts, they are actually mapped to the same Interpress font.
73: .)f
74: .RS
75: .ip "RN"
76: This is the roman numeral font. It has the digits one through nine
77: mapped to the matching roman numeral. The digit zero is mapped to roman
78: numeral 10.
79: .ip "CN"
80: This is the circled (arabic) numeral font. The digits are mapped
81: in the same way.
82: .ip "XX"
83: The remaining miscellaneous characters which are mapped to normal
84: ASCII characters.
85: .RE
86: .sh 3 "Hints and Warnings"
87: .lp
88: This section discusses unexpected behavior that users of iptroff might
89: encounter and how to deal with it.
90: .lp
91: On page three (3) of
92: .i "Typesetting Mathematics - User's Guide"
93: it is implied that typing a ``{'' to eqn will produce a roman ``{'' in the
94: output. Unfortuately, eqn doesn't produce any code to guarantee this behavior.
95: Instead it relies on the fact that the C/A/T would always print ``{'' as
96: a roman character. Since the \*(IP fonts include bold and italic curly
97: brackets, eqn output will produce italic curly brackets by default.
98: .lp
99: The \-me macros have a bug where some footnotes are broken across pages when
100: they shouldn't be. This may be because our higher device resolution
101: alters the fudge factor that is used
102: to compute the amount of space to reserve for a footnote.
103: .lp
104: The 4.2 BSD macros have been modified to produce cut-marks for roll paper
105: devices such as Versatec plotters. These cut marks will cause appearance
106: errors to appear on the banner page produced by the 8044 printer.
107: In \-me they can be removed by placing the following
108: two lines at the front of your file:
109: .(l
110: .rm @m
111: .)l
112: In \-ms they can be removed by using the following lines:
113: .(l
114: .rm CM
115: .)l
116: .lp
117: The default physical offset for \*(TR is often too small. Most users
118: will preface their files with a
119: .(l
120: .po 1i
121: .)l
122: .lp
123: to produce the correct page centering.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.