Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!husc6!unix!unix.sri.com!felix From: felix@ai.sri.com (Francois Felix INGRAND) Newsgroups: comp.lang.postscript Subject: Re: even and odd page separator. Message-ID: Date: 7 Aug 90 17:25:19 GMT References: <14709@unix.SRI.COM> <1990Aug5.231903.6165@watdragon.waterloo.edu> Sender: news@unix.SRI.COM Organization: SRI International, Menlo Park, CA Lines: 35 In-reply-to: cjroehrig@poppy.uwaterloo.ca's message of 5 Aug 90 23:19:03 GMT In article <1990Aug5.231903.6165@watdragon.waterloo.edu> cjroehrig@poppy.uwaterloo.ca (Chris J. Roehrig) writes: > In article <14709@unix.SRI.COM> felix@AI.SRI.COM (Francois Felix INGRAND) writes: > >I am looking for a tool to separate odd and even page from a PS file. > >At the end I want to be able to print double sided. > > > There is a shell script to do this in the NeXT ftp site at > sonata.cc.purdue.edu under /pub/next/source called pstools. > It creates two .ps files, one containing odd pages and one > containing even pages. However, I have had problems getting > it to work on complicated documents. (When most of the BuzzNUG > files (NeXT newsletters produced by FrameMaker) are run through > it, the resulting two files end up generating syntax errors.) > It may work ok for simple things, though. I think I have tried this program. It makes a fairly strong assumption that the %%Page: or %%Pages: field is correct, and check the last digit to see if it is an even or odd number. Unfortunately, the ps file I want to parse do not have these fields set up right. > If anyone knows of a better program, I'd like to hear about it, too. Me too of course. > Chris Roehrig (croehrig@audiolab.UWaterloo.ca) > Audio Research Group > University of Waterloo, Canada -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Francois Felix INGRAND SRI International, AIC felix@AI.SRI.COM 333, Ravenswood Avenue felix%AI.SRI.COM@UUNET.UU.NET MENLO PARK, CA 94025, USA "Pourquoi tant de haine..." (Edika) "Read my Lisp... No new syntax" (nil)