![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to VERSION CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Research Unix] / researchv10dc / cmd / postscript|
Return to VERSION CVS log | Up to [Research Unix] / researchv10dc / cmd / postscript |
1.1 root 1: ------------------------
2: Version 3.3.1 5/20/91
3: ------------------------
4:
5: 1: buildtables stuff has been cleaned up and is now a user level command.
6: Uses shell.lib files that are installed with font tables. The devpost
7: tables were built on a version 47.0 PS-810. The devLatin1 tables were
8: built on a version 51.7 PS-820.
9:
10: 2: The devLatin1 tables provide support for the ISO Latin1 alphabet on
11: PostScript printers.
12:
13: 3: All translators support different text font encoding schemes using the
14: -E option and *.enc files installed in POSTLIB. The ISO Latin 1 alphabet
15: is supported with file /usr/lib/postscript/Latin1.enc.
16:
17: 4: printfont prints a table of the available (encoded) characters in one
18: or more PostScript fonts. It also understands the -E option.
19:
20: 5: grabit and hardcopy are two new programs that may be of interest to the
21: more serious PostScript programmer. grabit resembles ==, but produces
22: output that's usally easier to read. hardcopy redirects output from
23: PostScript file output operators (or procedures) to paper. It's useful
24: if you don't have direct access to a printer.
25:
26: 6: Prologues and programs are stored together. Other common PostScript files
27: are now in the psfiles directory.
28:
29: 7: Changed $(@F) in the DWB 3.2 makefiles to `basename $@`. $(@F) didn't work
30: properly on research systems??
31:
32: ------------------------
33: Verions 3.3 4/16/90
34: ------------------------
35:
36: 1: The package is now included in DWB. Version numbers are a bit misleading.
37: The one in postscript.mk refers to the DWB package.
38:
39: 2: dpost (and troff) now read ASCII font tables. makedev and the old binary
40: format are gone.
41:
42: 3: The devpost directory came directly from the DWB package. The font tables
43: originally distributed with this package are in directory devopost. They
44: are not installed. If possible we recommend you use the devpost tables.
45: The old tables can be installed by adding devopost to the TARGETS list in
46: file postscript.mk.
47:
48: 4: dpost recognizes two new fields in font tables. Entries for the full
49: PostScript font look like,
50:
51: fontname Times-Roman
52:
53: The fontname field is helps manage host resident fonts, the DocumentFonts
54: comment, and is used to define font name abbreviations like the ones in
55: dpost.ps. A font table entry that looks like,
56:
57: named in prologue
58:
59: disables the runtime abbreviation for the font - dpost assumes it's already
60: in the prologue.
61:
62: 5: Extra font tables included in DWB 3.0's devpost font collection are in
63: directory devpost.add. They included here, but should probably not be
64: used.
65:
66: 6: Bracket building has been fixed and tested on a wide range of PostScript
67: printers. It will likely still not work on many clones. Real problem
68: appears to be with Adobe's braceleftbt character.
69:
70: 7: Most of the special tuning code for device emulation has been removed.
71: Emulation still works, but there may be cases where it's not as good as
72: earlier versions.
73:
74: 8: Several problems with color and reverse video printing have been fixed.
75:
76: 9: buildtables directory has been cleanup up. The template files in directory
77: buildtables/devpost.data were used to build the devpost tables.
78:
79: 10: postplot and download are two new programs. postplot is for the System V
80: plot package only. Both were written for the Unix 4.0 lp package.
81:
82: 11: postgif is also relatively new - it came from Chi Choy.
83:
84: 12: The translators now rotate clockwise when printing in landscape mode. If
85: you want the old behavior set ROTATION to -1 in postscript.mk.
86:
87: 13: forms.ps has been cleaned up some. Better behavior when you print 2
88: landscape pages on one sheet.
89:
90: 14: Handling of Datakit code for System V has been changed some. Makefiles
91: now expect to find libdk.a and dk.h in standard places (e.g /usr/lib and
92: /usr/include). Set DKHOST to TRUE in postscript.mk to get Datakit support
93: on System V.
94:
95: If you're stuck and need to have things behave as they did in the past
96: take a look at file postio/postio.mk. Define DKHOSTDIR and uncomment
97: three lines and the behavior should be close to what it was.
98:
99: 15: Picture inclusion and color macros are gone. They're included in the DWB
100: package, and not here.
101:
102: ------------------------
103: Version 3.2 11/27/89
104: ------------------------
105:
106: 1: Implemented height and slant requests in dpost.
107:
108: 2: Modified the behavior of all translators so save objects are no longer left
109: on the stack. The original implementation was a mistake and occasionally
110: (e.g. picture inclusion with forms.ps) resulted in invalid restores.
111:
112: 3: Fixed the mistake in the external declaration of mesg in postio/slowsend.c.
113:
114: 4: The malloc() call in postdmd (routine dimensions()) is only made if patterns
115: is positive.
116:
117: 5: Changed definition of De in draw.ps so savematrix is loaded with the CTM
118: whenever De is executed. Original implementation didn't work with forms.ps
119: because the CTM is changed with each page image. (4/29/89)
120:
121: 6: Flush stdout when postio is invoked with the -t option - just convenient
122: not necessary. (4/30/89)
123:
124: 7: Included a man page for the picture inclusion macros - file man/mpictures.5.
125: (5/6/89)
126:
127: 8: Added BoundingBox code to dpost - still needs to go in other translators.
128: Most of the work is done in common/bbox.c. (5/7/89)
129:
130: 9: Fiddled with the bracket building stuff in dpost.ps so things finally look
131: decent. Was particularly bad on the typesetter.
132:
133: 10: dpost now generates a PageBoundingBox comment and ps_include.c accepts
134: the comment. Added -B option to enable/disable the BoundingBox calculations.
135: -Bon to enable and -Boff to disable. On by default now, but that may change.
136: Add similar code to the rest of the translators (6/20/89).
137:
138: 11: Fixed ps_include.c so it properly handles %%BeginGlobal and %%EndGlobal.
139: Added braces and compare page.start to page.end instead of 0.
140:
141: 12: Added xymove(hpos, vpos) for \X'PS ...' request - near the end of devcntrl().
142: Must output position info for following PostScript.
143:
144: 13: Added a call to endtext() immediately before the oput() call for \N'...'
145: requests. Without it spacing often messed up with -e2 but not -e0.
146:
147: ------------------------
148: Version 3.1 11/15/88
149: ------------------------
150:
151: 1: postio can run as one or two processes (-R option) and can establish an
152: interactive connection with a postscript printer (-i option). Parsing of
153: status reports has been improved. The status query mechanism can be disabled
154: using the -q option. An exit status of 1 implies a system error (eg. can't
155: open the line) while 2 usually means there was an error in the PostScript
156: file. By default postio runs as a single process. The -B, -R, and -q options
157: can be used to speed things up some. A version of the program (previously
158: supplied in postio.tmp) that can help if you seem to be having flow control
159: problems can be obtained using the -S option. It's not generally recommended
160: and should only be used as a last resort!
161:
162: 2: Several widthshow encoding schemes have been added to dpost and can reduce
163: print time by 20% or more. The method used to encode lines of text can be
164: changed on the command line using the -e option. Level 0 produces output
165: essentially identical to previous versions of dpost. The default can be
166: changed by modifying the definition of ENCODING in ./Makefile. At present
167: only level 0 is thoroughly tested, although level 2 (ie. -e2) may be the
168: default and is undoubtedly worth a try.
169:
170: 3: dpost now supports color selection and reverse video. Access in troff is via
171: the stand-alone macro package ./macros/color. Examples are,
172:
173: .so /usr/lib/macros/color
174: .CL red "this prints in red"
175: .CL "white on black" "and this prints white text on a black background"
176:
177: The postscript procedures that handle color and reverse video can be found
178: in ./postscript/color.ps. Additional colors can be added to the colordict
179: dictionary defined in ./postscript/color.ps.
180:
181: 4: The dpost drawing routines have been improved and have been moved from the
182: prologue (ie. ./postscript/dpost.ps) to ./postscript/draw.ps. That file is
183: only included if needed. Drawing routines now support the ability to group
184: a series of drawing commands together as a single path. May be useful for
185: future versions of pic that wish to fill regions with colors or gray levels.
186: Access is via the new "x X BeginPath" and "x X DrawPath" device control
187: commands. In addition there's some complicated PostScript code in file
188: ./postscript/baseline.ps, that can be used to set text along an arbitrary
189: curve. It's terribly confusing and I doubt anyone will have the patience to
190: bother to figure it out.
191:
192: 5: A simple picture packing troff preprocessor (picpack) has been included and
193: the code needed to recover pictures and text has been added to dpost. The
194: program is designed to supplement to the original picture inclusion mechanism,
195: and should ONLY be used when absolutely necessary. Using dpost to pull picture
196: files into a document is strongly recommended and will always be the more
197: efficient and portable approach. picpack simply provides a way to combine
198: pictures and text in a single file before dpost is executed. It may help in
199: a distributed printing environment where the user runs everything through
200: troff while a spooling daemon (eg. lp) handles the postprocessing. There
201: are serious disadvantages to this approach, with perhaps the most important
202: being that troff output files (when picpack is used) will likely result in
203: files that can no longer be reliably passed through other important post-
204: processors like proof.
205:
206: 6: Code to handle host resident PostScript fonts in dpost has been tested and
207: finally works. The -H option points dpost to a host resident font directory,
208: which by default is NULL. Host resident font files stored in that directory
209: must be assigned a name that corresponds to the one or two character troff
210: font name. Width tables must also be built (see buildtables/README), the new
211: binary font files must be installed in /usr/lib/font/devpost, and a mapping
212: definition from troff's name to the PostScript font name must be added to
213: ./postscript/dpost.ps.
214:
215: 7: The default pattern length in postdmd has been reduced to from 10 to 6 bytes.
216: Printers with fast processors (eg. PS-810s) often benefit from a further
217: reduction, while optimal performance on slower printers (eg PS-800s) may
218: require larger pattern sizes. The pattern length can be set using the -b
219: option. Increasing the pattern size usually increases the size of the output
220: file.
221:
222: 8: Line drawing in posttek and postbgi includes code that automatically ties
223: lines to device space coordinates when you select a non-zero width. Helps
224: eliminate the variation in line thickness that many observed. The default
225: line width in posttek and postbgi is still 0 (which gets 1 pixel). If you
226: want a different default change the definition of variable linewidth in files
227: ./postscript/posttek.ps and ./postscript/postbgi.ps.
228:
229: 9: Defocused lines in posttek have been fixed.
230:
231: 10: postbgi now supports color and can be used to translate most PRISM (color
232: BGI) jobs. Special device specific tuning needed for many PRISM jobs can be
233: enabled by using the -P"/prism true" option. Missing pieces (eg. subroutines)
234: needed for translating PRISM jobs, have also been implemented.
235:
236: 11: postreverse can reverse the pages in documents that conform to Adobe's 1.0
237: or 2.0 file structuring conventions, and it works with all the translators in
238: this package. The new version is backwards compatible, but files produced by
239: the new translators should not be passed through old versions of postreverse.
240: The likely result will be no output at all. If you choose to do a partial
241: installation put the new postreverse up first!
242:
243: 12: All translators attempt to conform to Adobe's Version 2.0 file structuring
244: conventions. dpost output falls short, but only in the interest of efficiency.
245: Passing dpost output through postreverse (perhaps with the -r option) produces
246: a minimally conforming PostScript file.
247:
248: 13: All the translators now support three options that pass arbitrary PostScript
249: through to the output file. The -P and -C options add a string and the
250: contents of a file respectively immediately after the prologue. It's assumed
251: whatever is added is legitimate PostScript - there is no checking. In each
252: case the added PostScript code becomes part of the job's global environment.
253:
254: The -R option can be used to request special action (eg. manualfeed) on a
255: global or page basis. The argument should be "request", "request:page", or
256: "request:page:file". If page is given as 0 or omitted the request applies
257: globally. If file is omitted the lookup is in /usr/lib/postscript/ps.requests.
258: The collection of recognized requests can be modified or extended by changing
259: /usr/lib/postscript/ps.requests.
260:
261: 14: PostScript code (from Johnathan Shopiro) that produces bolder versions of the
262: Courier fonts has been included in file postscript/fatcourier.ps. The file
263: can be added to individual prologue files (eg. dpost.ps) or pulled in as
264: needed using the -C option.
265:
266: 15: postmd is a new program that can be used to display a large matrix as a gray
267: scale image. May help if you're looking for patterns in a large matrix. A very
268: optimistic estimate suggests you can display up to a 600x600 matrix (with five
269: different shades of gray) on 300dpi printer using 8.5x11 inch paper.
270:
271: 16: What's available in buildtables has been cleaned up and works well with the
272: new version of postio. It can be used to have PostScript printers build troff
273: width tables for both printer and host resident fonts.
274:
275: 17: The PostScript bind operator has been applied to all procedures that are
276: expected to be executed more than once. Redefined save and restore procedures
277: are no longer needed and saverestore.ps is not included in this package.
278:
279: 18: The bizarre PostScript code used to get to the upper left corner of a page
280: in old versions of dpost.ps and postprint.ps has been replaced by something
281: that's at least slightly more comprehensible. All prologues have also been
282: changed so picture inclusion (eg. including a pic picture that's been run
283: through troff and dpost) should work better than previous versions. Still
284: missing (from most translators) is the %%BoundingBox comment and even when
285: it's put out (by postdmd) only the dimensions are correct - sorry!
286:
287: 19: The careless mistake in the DKHOST section of postio that some noticed belongs
288: to me (not Allan Buckwalter) and has now been fixed.
289:
290: 20: By default all prologues still use the current clipping path to determine page
291: dimensions, but that behavior can be disabled by setting boolean useclippath
292: (in each prologue) to false. In that case the page dimensions will be taken
293: from array pagebbox, which by default is initialized to 8x11 inch paper. The
294: -P options (in each translator) can change useclippth and pagebbox.
295:
296: 21: New in the misc directory is sample lp support from Maryann Csaszar and a
297: simple program that converts host resident font files obtained from a Macintosh
298: to a format that works on Unix.
299:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.