PostScript® Language Program Design [Paperback]

Adobe Systems Inc. (Author)

Book Description

ISBN-10: 0201143968 | ISBN-13: 978-0201143966 | Publication Date: January 11, 1988 | Edition: 1

Introduces the Postscript programming language, describes the imaging model, and discusses emulators, page design, program structure, scanned images, file merging, and error handling.

Product Details

• Paperback: 240 pages
• Publisher: Addison-Wesley Professional; 1 edition (January 11, 1988)
• Language: English
• ISBN-10: 0201143968
• ISBN-13: 978-0201143966
• Product Dimensions: 9.1 x 7.4 x 0.6 inches
• Shipping Weight: 13.6 ounces (View shipping rates and policies)
• Average Customer Review: 4.0 out of 5 stars  See all reviews (2 customer reviews)
• Amazon Best Sellers Rank: #1,482,630 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

14 of 14 people found the following review helpful:

4.0 out of 5 stars Caution: Not a beginner's guide to postscript!, July 17, 1997

By A Customer

This review is from: PostScript® Language Program Design (Paperback)

I consider myself a hardcore programmer, but I have not programmed with postscript before. When my job required postscript options added to the printer drivers, I started with this book. I now believe it would have been better to start with a beginner's guide and a reference manual on postscript. This book is great if you are already programming in postscript and want to better your skills with it

7 of 13 people found the following review helpful:

4.0 out of 5 stars I didn't really need to know THAT much about PostScript!, April 6, 2001

By 

kent dahlgren (Portland, Oregon United States) - See all my reviews

This review is from: PostScript® Language Program Design (Paperback)

This is a book intended for those who want to write drivers and stuff. I'm not that guy. I just want to know enough about how it works to respond to needs as they arise.

You know? Just because I want a web server on my machine doesn't mean I want to write an HTTP stack from scratch. I'll probably just find what works and adapt it to my purposes.

Here's a specific example relative to PostScript:

I needed to create an application for someone who wanted a custom driver that would print different state-related labels on their printed images.

Did I run off to the Program Design book to figure out how to write it from scratch? No way, man. My advanced status within the cigarette consumption community requires continued proficiency through hourly breaks, thus making this sort of focused activity quite impossible.

Instead I looked in other drivers that had what I wanted, then printed to file, viewed source, and then pulled the code out as I felt appropriate. Quick, relatively easy, and demonstratively slothful.

Get this book if you want to learn how to write drivers. Better, get this book and display it prominently so others think you know how to write PostScript drivers.

Just get this book. Hell, its worth the money.