Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!unicorn!ogicse!plains!dall
From: dall@plains.UUCP (Brian Dall)
Newsgroups: comp.lang.postscript
Subject: Re: Reg marks, crop marks, gry
Keywords: use actual width you want, please
Message-ID: <5503@plains.UUCP>
Date: 14 Aug 90 03:44:40 GMT
References: <134400015@cdp>
Followup-To: comp.lang.postscript
Distribution: usa
Organization: North Dakota State University, Fargo
Lines: 27

In article <134400015@cdp> jwhiting@cdp.UUCP writes:
>... creates registration marks.
> [ much deleted]
>0 setlinewidth stroke

This works fine at 300dpi, but you should request the actual 
line width you want.  At 2400dpi, you need a microscope to
see the lines.  If you want 1/300th of an inch think lines, ask
for them with code like "0.24 setlinewidth stroke" instead of 
assuming the smallest line a device can print will work ok.

See the "Orange" Book (Roth) section on device independent coding.

As far as a wish list, Quark XPress will do the color bars, and
most programs have options for crop marks and registration marks.
Usually the items that need to be added by hand are things like
fold marks.

Other usefull information I like to see on the output is the name
of the file and the list of fonts that are required, so I know
which suitcases to open if I go back to it later (obviously from
a Mac environment).

Take Care,

-Brian Dall
dall@plains.NoDak.edu