EPS Graphics Support in Word for Windows

ID: Q71682


The information in this article applies to:
  • Microsoft Word for Windows, versions 1.0, 1.1, 1.1a, 2.0, 2.0a, 2.0a-CD, 2.0b, 2.0c


SUMMARY

The Word for Windows Encapsulated PostScript (EPS) graphics filter EPSIMP.FLT supports the Adobe Systems Encapsulated PostScript Specification versions 2.0 and earlier.

For an EPS image to be recognized, all of its structure elements must be in accordance with the Adobe specification.

According to Adobe, an EPS file is a standard PostScript language file with a bitmap screen preview included optionally in the format. The purpose of an EPS file is to be included into other document make-up systems, such as Word for Windows. The Word for Windows version 1.1a EPS filter supports EPS images with Tagged Image File Format (TIFF) 5.0, or Windows metafile (WMF) embedded display images. The following is information on content requirements, how EPS graphics are displayed, and how they are printed.


MORE INFORMATION

Required EPS Comments

  • The first line in the EPS header (the first line in the EPS file) must be the version comment:
    %!PS-Adobe-x.x EPSF-x.x
    This line indicates that the PostScript language file conforms to the Adobe standard. The version number following the word "Adobe-" indicates the level of adherence to Adobe's standard PostScript document structuring conventions and can have a value between 1.0 and 2.0. The version number following the word "EPSF" indicates the level of adherence to the EPS specification, and can have a value between 1.0 and 2.0.

    Note: If this line is incorrect, or missing, Word for Windows may display the error message
    Cannot read of display file when importing EPS
    when importing the file.


  • The following comment must also be present in the EPS header:
    %%BoundingBox: LLx LLy URx URy
    The LL variables represent the border lengths of an EPS graphic.


Displaying EPS Graphics

  • If an EPS file contains an embedded TIFF or WMF display image, a representation of the image is displayed in Word for Windows. The quality of the display image depends on the resolution of the TIFF or WMF embedded in the EPS file. Because such display images are intended primarily as positioning aids in page composition, resolution is often low.


  • If an embedded TIFF or WMF display image is not included or the image is determined by the converter to be invalid, a graphics bounding box displays instead of a display image. Additionally, the bounding box may contain text descriptions of the creator application, creation date, and file title. Because including such information in an EPS file is optional, a blank bounding box may display in some cases.


Printing Documents Containing EPS Graphics

  • When printing to a PostScript printer, whether or not a TIFF or WMF display image is embedded in the EPS file, the PostScript commands from the PostScript section of the file are sent to the printer. In this scenario, the on-screen resolution of the display image has no impact on the printing quality of the file.


  • When printing to a non-PostScript printer, if a TIFF or WMF display image is embedded in the EPS file, the TIFF or WMF image prints as indicated above, but such images are normally of low resolution (for example, 128-by-128 bits). As a result, if you print a document containing an embedded EPS image to a non-PostScript printer, the resolution of the printed image is relatively low.


  • When printing to a non-PostScript printer, if a TIFF or WMF display image is not embedded in the EPS file or the display image is determined by the filter to be invalid, only the bounding box, creator application, date, and title text (if available) are printed.


In versions 1.0 and 1.1 of Word for Windows, an EPS macro is used to import EPS image files, but this macro limits sizing and positioning of imported pictures. To use the new EPS graphics filter, EPSIMP.FLT, the old EPS macro must be removed. For instructions on removing the EPS macro, see the file README.DOC located in the \WINWORD directory.

If there are documents that include EPS pictures imported with the old EPS macro, it is possible to retain the EPS macro in a special purpose template other than NORMAL.DOT. For more information on how to do this, query on the following words in the Microsoft Knowledge Base:
removing and EPS and macro
Some applications can generate printer-specific EPS files by intercepting PostScript output to a file. Unfortunately, not all applications strictly follow the standard format as set forth by Adobe. Consequently, a PostScript print file generated by a printer driver for one PostScript printer may not print correctly to another brand of PostScript device.

The Word for Windows EPS graphics filter is not designed to reinterpret an EPS file's PostScript code to overcome such non-standard contents. As a result, if an EPS file does not properly follow the Adobe specification, the best result Word for Windows can provide is a display of the bounding box for the image on screen. If you attempt to print, Word sends the original PostScript code to the current PostScript printer.

If the PostScript code was not originally generated for the current PostScript printer, the PostScript image, or the entire document, may not print. This is not a problem with the Word for Windows EPS graphics filter, but rather with the EPS output from the original source application.

Note: The Word 1.1a for Windows EPS graphics filter is not supported under the Windows versions 2.x environment. If you are running under Windows 2.x, you must use the EPS Insert Picture macro instead.

For more information on the Encapsulated PostScript Specification, contact the PostScript Developer Support Group at:
Adobe Systems Incorporated
1585 Charleston Road PO Box 7900
Mountain View, CA 94039-7900
(415) 961-4111
Reference(s):

"Encapsulated PostScript Files Specification Version 2.0"

Additional query words: 1.0 1.1 1.10a 2.00a grphflt

Keywords :
Version : WINDOWS:1.0,1.1,1.1a,2.0,2.0a,2.0a-CD,2.0b,2.0c
Platform : WINDOWS
Issue type :


Last Reviewed: December 10, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.