Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!giza.cis.ohio-state.edu!jgreely From: jgreely@giza.cis.ohio-state.edu (J Greely) Newsgroups: comp.sources.d Subject: Re: Creating a monster (was Re: Production perl...) Message-ID: Date: 24 Oct 89 20:12:02 GMT References: <6277@jpl-devvax.JPL.NASA.GOV> <1764@sauron.Columbia.NCR.COM> Sender: news@tut.cis.ohio-state.edu Reply-To: J Greely Organization: Ohio State University Computer and Information Science Lines: 46 In-reply-to: jgreely@oz.cis.ohio-state.edu's message of 22 Oct 89 07:46:34 GMT (this thread is my thread, this thread ain't your thread...) In article jgreely@oz.cis.ohio-state.edu (J Greely) writes: > The two-up (actually, n-up) code is already there, and will soon be >posted in slightly revised form to wherever seems most appropriate. >The signature-ordering code will be added to it as soon as I clean it >up a bit and add a manual page. The whole package has been sent off to comp.sources.misc, and will appear whenever. This is what you get: up - print conforming PS n-up parr - rearrange conforming PS into signature order (or any order, for that matter) makeup - produce numbered test pages up.1, parr.1, makeup.1, uprc.5 - manual pages for above ...plus a README, a Makefile, and a how-to guide for those who hate my code. Order now, and you'll also get this handy closet maximizer, a $10 value, absolutely free! (too much late-night cable tv?) For those who hate waiting, it's currently available for anoymous ftp from tut.cis.ohio-state.edu as pub/perl/scripts/up.shar, and for anonymous uucp from osu-cis as ~/perl/scripts/up.shar (and yes, the names are right this time). For anyone who picked this stuff up previously, this is a new version, with lots of changes. > Now all I need to do is find a dvi-to-PostScript converter that >obeys the Adobe structuring conventions the way I do, and I'm set. I'm close on this one. dvips 4.2 (ftp'able from labrea.stanford.edu) is the best bet, and only requires one minor hack to work (moving the Setup code to PageSetup). "But *sniff*, you will come back to play with us again, won't you?" "Of *course* I will! On the second Tuesday of next week." "Hooway! Hooway!" "Wait! The *second* Tuesday?" -- J Greely (jgreely@cis.ohio-state.edu; osu-cis!jgreely)