From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] Re: psutils et al From: nemo@gsyc.escet.urjc.es MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-xdsrpwjilgemryselosjgylsek" Message-Id: <20010215113020.58ECF199D5@mail.cse.psu.edu> Date: Thu, 15 Feb 2001 12:44:04 -0500 Topicbox-Message-UUID: 66039a8e-eac9-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-xdsrpwjilgemryselosjgylsek Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit : PostScript comments, by the way; a common misbelief. It's : not really the psutils author's fault that the psutils would : require to use a PostScript program analyser to detect bad input, : and even more effort to process non-conforming PostScript correctly. : He had the option of doing nothing, or making the best of a bad : job and writing something that worked most of the time. I'm sorry. I didn't want to say that the author did a bad job, I was only trying to say that it was mpage the one who did the job for me. --upas-xdsrpwjilgemryselosjgylsek Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <9fans-admin@cse.psu.edu> Received: from mail.cse.psu.edu (postfix@psuvax1.cse.psu.edu [130.203.4.6]) by gsyc.escet.urjc.es (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id KAA23296; Thu, 15 Feb 2001 10:44:31 +0100 X-Authentication-Warning: gsyc.escet.urjc.es: Host postfix@psuvax1.cse.psu.edu [130.203.4.6] claimed to be mail.cse.psu.edu Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.8.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 13FF3199F6; Thu, 15 Feb 2001 04:44:10 -0500 (EST) Received: from minster.cs.york.ac.uk (minster.cs.york.ac.uk [144.32.40.2]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id EC24A199D5 for <9fans@cse.psu.edu>; Thu, 15 Feb 2001 04:43:53 -0500 (EST) Received: from john by minster.cs.york.ac.uk with local-rmail (Exim 3.16 #1) id 14TKx9-0002eE-00; Thu, 15 Feb 2001 09:43:55 +0000 To: 9fans@cse.psu.edu, john@cs.york.ac.uk From: "John A. Murdie" Message-Id: Subject: [9fans] Re: psutils et al Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Thu, 15 Feb 2001 09:43:35 +0000 nemo@gsyc.escet.urjc.es wrote: >Yep. I knew them, but almost all of them I tried in Linux either >did not work as they said, or broke the postscript. Nevertheless, >mpage -1 -l worked fine in linux. Perhaps it's time to consider a >port of mpage to Plan9, since my problem was that I was >unable to do this under plan9. > >I read the gs documentation and seems that viewers that >do the rotate thing are using postscript routines to change >the page orientation, so I think that unless page could go the >same way, there is no simple gs option to rotate the ps. >In any case, I'd say that's the job of a filter and not of >page. > >hth to others with the same problem. The psutils are fine; it's usually bad PostScript that causes them to go wrong. Their manual pages emphasise that they will only cope with Document Structure Convention -conforming PostScript (see Appendix G of the second edition of the PostScript LRM; this appendix has been taken out of the current third edition). This means much more than their having all the correct DSC pseudo PostScript comments, by the way; a common misbelief. It's not really the psutils author's fault that the psutils would require to use a PostScript program analyser to detect bad input, and even more effort to process non-conforming PostScript correctly. He had the option of doing nothing, or making the best of a bad job and writing something that worked most of the time. The major offender providing bad PostScript is, in my experience, - yes, you've guessed it - Microsoft. I spend many minutes a week dealing with badly generated PostScript from various sources. If anyone wants me to explain how to fix Microsoft PostScript to be DSC compatible, ask. At various times I've attempted to write an rc/awk script to do the job automatically, but it's just too messy. I'm sad to see these consequences of bad design decisions attempting to invade Plan 9. (I hope and believe the Plan 9 devotees won't let it happen.) PostScript is too low a level to be carrying out *everyday* page transformations; it's just too flexible a language. I think that such page transformations should be done at a higher level of document description. On Unix and Plan 9, I'd say that was probably at the ditroff output level. ditnup, ditselect, dittodit etc, anyone? In one way, Microsoft had the right idea (if not the right implementation) with their device-independent DGI page description interface, though the recent GDI Plus has made this more complex. John A. Murdie Department of Computer Science University of York England --upas-xdsrpwjilgemryselosjgylsek--