Showcase and discover digital art at yex

Follow Design Stacks

Subscribe to our free newsletter to get all our latest tutorials and articles delivered directly to your inbox!

PostScript Methodologies

How to test an Adobe PostScript print file.

A minimal, useful, but inadequate test is:

  1. Print it on a PostScript language level 2 (a.k.a. Red and White Book) interpreter such as a QMS 1700 or HP 4si or 5si.
  2. Ghostview. Check for the following:
    • Eyeball hangs do not occur (i.e., that the cursor changes to a cross).
    • All EPS images show up and are properly sized, located and oriented.
    • The file shows all pages in the proper order with no extra pages.
    • The page number bar appears in the Ghostview frame.

The print file should be submitted to each of the following and the outputs checked for proper behavior:

  1. A PostScript language level 1 (a.k.a. Red Book) interpreter such as an Apple LaserWriter.
  2. A PostScript language level 2 (a.k.a. Red and White Book) interpreter such as an QMS 1700 or a HP 4si or 5si.
  3. Ghostview. Check for the following:
    • Eyeball hangs (the cursor does not change to a cross) do not occur.
    • All EPS images show up and are properly sized, located and oriented. If an EPS image does not have appropriate amounts of white space around it, then check the image itself separately for a proper BoundingBox DSC comment.
    • The file shows all pages in the proper order with no extra pages.
    • The page number bar appears in the Ghostview frame.
    • Skipping around in the file works between arbitary pages.
  4. Ghostscript itself (somestimes the program name is gs). Check for the following:
    • All EPS images show up and are properly sized, located and oriented. If an EPS image does not have appropriate amounts of white space around it, then check the image itself separately for a proper BoundingBox DSC comment.
    • The file shows all pages in the proper order with no extra pages.

How to test an Adobe EPS file.

Note that an EPS file may itself contain other EPS files.

A minimal, useful, but inadequate test is:

  1. After being encapsulated in a test harness, the resultant test file should be submitted to a PostScript language level 2 Red and White Book) interpreter such as an QMS 1700 or a HP 4si or 5si.
  2. After being encapsulated in a test harness, the resultant test file should be submitted to Ghostview. Check for the following:
    • Eyeball hangs (the cursor does not change to a cross) do not occur.
    • All EPS images show up and are properly sized, located and oriented. If an EPS image does not have appropriate amounts of white space around it, then check the image itself separately for a proper BoundingBox DSC comment.
    • The page number bar appears in the Ghostview frame.
  3. Give the EPS file by itself to Ghostview. Check for the following:
    • Eyeball hangs (the cursor does not change to a cross) do not occur.
    • All EPS images show up and are properly sized, located and oriented. If an EPS image does not have appropriate amounts of white space around it, then check it for a proper BoundingBox DSC comment.

The EPS file should be submitted to each of the following tests and the outputs checked for proper behavior:

  1. After being encapsulated in a test harness, the resultant test file should be submitted to a PostScript language level 1 (a.k.a. Red Book) interpreter such as an Apple LaserWriter.
  2. After being encapsulated in a test harness, the resultant test file should be submitted to a PostScript language level 2 Red and White Book) interpreter such as an QMS 1700 or a HP 4si or 5si.
  3. After being encapsulated in a test harness, the resultant test file should be submitted to Ghostview. Check for the following:
    • Eyeball hangs (the cursor does not change to a cross) do not occur.
    • All EPS images show up and are properly sized, located and oriented. If an EPS image does not have appropriate amounts of white space around it, then check the image itself separately for a proper BoundingBox DSC comment.
    • The file shows all pages in the proper order with no extra pages.
    • The page number bar appears in the Ghostview frame.
    • Skipping around in the file works between arbitary pages.
  4. After being encapsulated in a test harness, the resultant test file should be submitted to ghostscript itself (somestimes the program name is gs). Check for the following:
    • All EPS images show up and are properly sized, located and oriented. If an EPS image does not have appropriate amounts of white space around it, then check the image itself separately for a proper BoundingBox DSC comment.
    • The file shows all pages in the proper order with no extra pages.
  5. The EPS file by itself to Ghostview. Check for the following:
    • Eyeball hangs (the cursor does not change to a cross) do not occur.
    • All EPS images show up and are properly sized, located and oriented. If an EPS image does not have appropriate amounts of white space around it, then check it for a proper BoundingBox DSC comment.
  6. The EPS file by itself ghostscript itself (somestimes the program name is gs). Check for the following:
    • The EPS image shows up and is properly sized, located and oriented. If an EPS image does not have appropriate amounts of white space around it, then check for a proper BoundingBox DSC comment. pages.

Comments