Page tree
Skip to end of metadata
Go to start of metadata

This manual describes the Jaws RIP (raster image processor) version 4001.0 from Global Graphics Software (GGS) for Macintosh, Windows and Linux. Generally speaking, the only differences between Jaws running on different platforms are issues to do with installation, file naming and so on. These differences are covered in detail in Chapter 5 to Chapter 10.

Most importantly, all device driver and device class code is portable across all platforms.

Contents of this manual

  • Chapter 1, “Jaws overview”, gives an overview of Jaws, and covers various compatibility issues, special features and the like. This includes a brief review of features that have been added to the Adobe® PostScript® language since the 2nd edition of the PostScript Language Reference Manual (PLRM) was published, plus a description of Jaws features that are not part of the Adobe PostScript language.
  • Chapter 2, “PostScript language compatibility” describes Jaws compatibility with the PostScript language.
  • Chapter 3, “PDF compatibility” describes Jaws compatibility with the PDF specification.
  • Chapter 4, “Jaws specific features” describes those language features in Jaws which are either not present in standard the PostScript language or documented as being product-dependent.
  • Chapter 5, “Jaws initialization files”, describes the various PostScript language files that Jaws reads when the interpreter first starts up.
  • Chapter 6, “Jaws sample device drivers”, covers the sample device drivers that are supplied with Jaws.
  • Chapter 7, “Jaws front-end interface”, describes the front-end interface, which you can use if you are linking Jaws into your own application. This interface lets you initialize the interpreter and pass PostScript language code to it.
  • Chapter 8, “Jaws kernel structures and routines”, describes various kernel data structures and support routines that you will need to know about if you are developing your own device drivers or device classes.
  • Chapter 9, “Writing Jaws device drivers”, provides a brief guide to the functions of the various device driver routines that you will need to provide in your driver.
  • Chapter 10, “Device classes”, describes device classes, and the routines that you can provide when you develop your own device class.
  • Chapter 11, “Miscellaneous developer notes”, contains a collection of notes, procedures and sample code that have been compiled by the Jaws team in response to common Jaws issues.


In complex installations, you may wish to send jobs between PCs, Macintosh computers, and computers running the Unix operating system.

You should be familiar with the following:

  1. Prepress terminology and common output devices.
  2. Simple PostScript language constructs.

Conventions used in this manual

All conventions are explained as they are first used. Here are some widelyused conventions.

Font conventions:

  • Italic is used for the names of files, first use of a new term or for normal emphasis in the text.
  • Courier is used in body text for the names of C routines, structures and variables. Routines are always written with parentheses after the name, for example, makestring().
  • Courier oblique is used as a placeholder in examples. For example, a routine such as dv_text() is used to refer to the device class text routine. dv_text is actually the name of the field (a function pointer) in the device class structure, and your own routine will probably be called something like foo_text().
  • Bold courier is used in code examples.
  • Routines are always written with parentheses after the name, for example makestring() and are shown in the following form:

uchar *malloczero (int bytes)

  • Sans serif Bold type is used for the names of PostScript language operators that appear in the body of the text.
  • Bold courier headings are used to introduce the description of particular routines or variables.
  • Note: Text indicated by starting with a bold word in the left margin is important and should be read carefully. A Note is often a suggestion that may save you work, improve performance, or improve the quality of output.
  • Warning: Like a Note, a Warning is important and often indicates the need for care to avoid loss of files or settings.

  • No labels