Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!1.eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Mark Carroll Newsgroups: comp.lang.postscript Subject: Re: setstrokeadjust: what's the disadvantage? Date: Tue, 28 Apr 2015 10:43:39 +0100 Organization: none Lines: 18 Message-ID: <87k2wwio50.fsf@ixod.org> References: <0951df15-771a-4953-9561-2eff99e5a323@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="1b3e5cba9e4d07a53741e6f3d1717925"; logging-data="19232"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/x7Wo8AV7ATiRR7nKODzcK" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) Cancel-Lock: sha1:wvRctK47z8SUzxS8MGPPW434+bA= sha1:pwKwzfneXKNQmdFYrvID+12HvTI= Xref: csiph.com comp.lang.postscript:2234 ken writes: (snip) > Higher resolution (and printers do keep increasing resolution, albeit > slowly) means more time taken to do scan conversion. If you add stroke > adjustment, that takes still more time, and for less and less benefit as > the resolution increases. (snip) That's interesting, I hadn't realized. > Unless you are drawing with something like 0 setlinewidth > the differing stroke widths will be hard to see. (snip) I've usually used 0 setlinewidth to mark the lines I am to cut along after printing. (-: -- Mark