Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!sdcsvax!nosc!humu!uhccux!lee
From: lee@uhccux.UUCP (Greg Lee)
Newsgroups: comp.graphics,comp.windows.misc
Subject: Re: PostScript standard?
Message-ID: <958@uhccux.UUCP>
Date: Thu, 15-Oct-87 07:55:35 EDT
Article-I.D.: uhccux.958
Posted: Thu Oct 15 07:55:35 1987
Date-Received: Sat, 17-Oct-87 07:19:58 EDT
References: <535@micas.UUCP> <15085@topaz.rutgers.edu> <532@gssc.UUCP> <482@tnosel.UUCP>
Reply-To: lee@uhccux.uhcc.hawaii.edu (Greg Lee)
Followup-To: <482@tnosel.UUCP>
Organization: U. of Hawaii, Manoa (Honolulu)
Lines: 17
Summary: sometimes you write a page-description program
Xref: mnetor comp.graphics:1265 comp.windows.misc:83

hvt@tnosel.UUCP (henq) writes:
>In article 'Re: PostScript standard?' John D. Miller writes:
>
>>  how many times do you sit down at the terminal and write a
>>  program that describes the page you want printed?  
> 
>if you program on a Mac, *all* you do is making programs
>that describe pages to be printed (WYISWYG, remember ?)
> ...

Well, I suppose writing the program directly is what was meant.
Then the answer is: rarely.  But somewhat more often the need
to examine or edit such a program arises.  For instance when
implementing a postscript driver.  Or making some small change
in the appearance of the output, or incorporating a figure, when
the high-level software doesn't do quite the right thing for you.
Then it's nice to have an editable interpretable program available.