oheare@gandalf.UUCP (David O'Heare) (07/11/89)
To all the kind folks who sent mail on the red, blue, and green books -- thanks. My favourite technical bookstore had the PostScript Language Tutorial and Cookbook (the blue book) and the PostScript Language Program Design book (the green book). They've also ordered the PostScript Language Reference Manual the red book). Now there's nothing standing in the way of me becoming a PostScript wizard. This stuff is fun! -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ !gandalf!oheare or maybe oheare@gandalf.UUCP or else 1-613-723-6500 "There's plenty of room for disclaimers," said Alice, sitting down in a large chair at the head of the table.
barnett@crdgw1.crd.ge.com (Bruce Barnett) (07/20/89)
In article <2537@gandalf.UUCP>, oheare@gandalf (David O'Heare) writes: > >They've also ordered >the PostScript Language Reference Manual the red book). Now there's >nothing standing in the way of me becoming a PostScript wizard. If you want to be a REAL PostScript Wizard, You also MUST get Inside PostScript $37.50 Frank Merrit Braswell Published by System, of Merrit, Inc 2551 Old Dobbin Dr. East Mobile, AL 36695 (205) 660-1240 and by Peachpit Press, Inc 1085 Keith Ave Berkeley, CA 94708 (415) 527-8555 It describes the real workings of the pre-defined procedures like =, ==, typeprint, stack, pstack, findfont, typecheck, etc. Also documented is the server loop, idle loop, ==dict, interactive mode, error handling, printer communication, the test page, etc. In many cases the "sources" of the procedures are also included and documented. That is, when available, the author examined the pre-defined procedures in the engine and documented what he found. As Mr. Braswell says: "Also be aware of the fact that the information in this book may not be 100% accurate since I developed _Inside PostScript_ apart from any Adobe internal documentation. Only Adobe can speak with complete authority on the subjetcs presented within." Braswell worked with Adobe to evaluate the alpha and beta software for several QMS printers. As he said in the book, the output of serverdict {} forall pstack intrigued him, and prompted him to write the book. Highly Recommended !!! -- Bruce G. Barnett <barnett@crdgw1.ge.com> a.k.a. <barnett@[192.35.44.4]> uunet!crdgw1.ge.com!barnett barnett@crdgw1.UUCP
batcheldern@level.dec.com (Ned Batchelder) (07/25/89)
> If you want to be a REAL PostScript Wizard, You also MUST get > > Inside PostScript > $37.50 > Frank Merrit Braswell I have a simple question: In what way does this book help you to become a real wizard? I've seen the book, and was amazed that someone would try to publish such a book, and now I am amazed that someone would so highly recommend it. It seems to me that since all of the new information in the book may be completely different not only from printer to printer, but in the next version of the same printer, that all Inside PostScript can really do is fill your head with a lot of trivia about a particular version of a particular printer. It should be called "Inside Version <foo> of Printer <bar>" I don't mind this to be a flame; I really would like to know in what way you will use this book. Ned Batchelder, Digital Equipment Corp., BatchelderN@Hannah.DEC.com
barnett@crdgw1.crd.ge.com (Bruce Barnett) (07/26/89)
I wrote>> >> If you want to be a REAL PostScript Wizard, You also MUST get >> >> Inside PostScript In article <3717@shlump.nac.dec.com>, batcheldern@level (Ned Batchelder) writes: >I have a simple question: In what way does this book help you to become >a real wizard? I've seen the book, and was amazed that someone would >try to publish such a book, and now I am amazed that someone would so >highly recommend it. Well, I have learned a lot from it. What I have learned was not well documented in the Adobe books. I am NOT a PostScript wizard, and nowhere near your level, Ned. Still, I have been collecting everything I can get on PostScript, and I still think this book is valuable. >It seems to me that since all of the new information in the book may be >completely different not only from printer to printer, but in the next >version of the same printer, that all Inside PostScript can really do is >fill your head with a lot of trivia about a particular version of a >particular printer. True, the Author has only debugged, with Adobe, 7 different printers - all QMS. True the implementation at QMS isn't the same as other vendors. But doesn't Adobe do most of the work? Do they sell the sources of their interpreter? If not, then most implementations should be similar??? >It should be called "Inside Version <foo> of Printer <bar>" I bet they wouldn't sell as many books if they did that. >I don't mind this to be a flame; I really would like to know in what way >you will use this book. A good question, and as I find myself learning PostScript and NeWS in my spare time, my knowledge is scanty. When I read the source of the various NeWS browsers, my head hurts. Nevertheless, I found the book to be refreshing in several ways. It explains what is really going on inside the printer. For instance, take the commands '=', '==', and 'pstack'. Instead of just stating how to use these commands, the book documents what these commands do. If I want to modify these commands, or make my own variation, I now understand how to do this. Those browsers mentioned above, for instance, display the structures in windows that allow you to examine procedures and modify them. This book gives me the tools to examine ANY implementation, and learn how ANY implementation REALLY works. I think. If someone knows if I am way-off base, please respond, and deflate my hopes. Then again, I'm the type of person who wants to have a real understanding how something works. Understanding one implementation helps me understand other implementations. I like reading books that explain how operating systems work down to the source code. I think "Inside PostScript" is that sort of book. What do other people think of this book? Am I the only one who likes it? -- Bruce G. Barnett <barnett@crdgw1.ge.com> a.k.a. <barnett@[192.35.44.4]> uunet!crdgw1.ge.com!barnett barnett@crdgw1.UUCP
batcheldern@level.dec.com (Ned Batchelder) (07/27/89)
Distribution: world
Keywords: red blue green Addison-Wesley print them
Organization: DEC
In article <1360@crdgw1.crd.ge.com>, barnett@crdgw1.crd.ge.com (Bruce Barnett)
states essentially that Inside PostScript has given him greater understanding
of the inner workings of PostScript implementations, and has helped him in
writing his own code that must act in ways similar to the PostScript code found
burned into the ROMs of printers.
I think this is a reasonable way to approach this book, but please, be careful.
It can be extremely tricky to keep separate the implementation and the
language definition. Many people would do very poorly on a quiz that
asked what PostScript facilities were guaranteed by the Red Book. I have
known even Adobe people to get questions of that nature wrong.
The fact is that if you examine a reasonable number of instances of a
thing, and they all have a feature in common, then even when you are
told that other instances may not have that feature, you deep down
believe that it either does or should.
For example, I've seen programs that make use of a variable named
"=string". Is this wise? No. Will it work on all the printers made so
far? Maybe. So why not do it? Because you have no guarantee that it will
continue to work.
So, go ahead and enjoy Inside PostScript. Just don't fall into the trap
of thinking that its cover is red.
Ned Batchelder, Digital Equipment Corp., BatchelderN@Hannah.DEC.com