Known limitations and minor bugs.

Table of contents

For other information, see the Development Projects list .

There are many areas that might make Ghostscript more useful or minor bugs that we would like to investigate and possibly fix, but for which we don't have enough resources. These may or may not be addressed in future releases.

If you would like to take responsibility for any of these issues, please contact us.

Additional comments on implementation approaches or project goals are in italic type like this.

Known Limitations.

bbox device doesn't allow min coords < 0.

Adobe eps specification doesn't say that bbox values must be positive, and, for example Adobe Illustrator, can create EPS files with negative bboxes. In such case, Ghostscipt returns zero instead of proper negative number.

Bug #202735, March 09, 2000.

This might be able to be fixed by applying a large positive translation to the bbox CTM which would be subtracted from coordinates passed to the target device as well as from the results the bbox device reports.

If coordinates for the ImagingBBox[0] and [1] values, then negative values are handled, but this is not reliable since there are places in the graphics library that depend on first quadrant coordinates.

Error messages are too low level and confusing.

Although technically correct many error messages are confusing for end users. Some commonly reported examples are listed below.

When pdfwrite device cannot open the output file it fails with:

**** Unable to open the initial device, quitting.
When CIDFont-CMap pair required by PDF file is not available GS fails with:
/undefinedresource in --findresource--

epswrite device generates low level PostScript.

epswrite devices reduce everything to path, fill, stroke, clip image, and imagemask operations. Although the resulting file prints OK it produces unsatisfactory results when scaled, distilled or imported into graphic editors. The file can easily exceed 4GB and hit file size limits in some applications or operation systems. Handling of big files is slow.

Bug #615165, September 26, 2002.

NB. The epswrite device is deprecated as of the 9.12 release, the eps2write device should be used instead which does not suffer these limitations.

Minor Bugs.

Bad JPEG stream in PDF generated when source ends prematurely

When GS converts the source image to JPEG stream in PDF file and the source data end prematurely, it generates bad JPEG stream. tiff2ps from libtiff distribution often generates such files.

One potential workaround is to use -dAutoFilterColorImages=false and -dColorImageFilter=/FlateEncode.

Bug #228808, Jan 15, 2000.

JPEG stream writes image dimensions in JPEG header when the stream is created. When the source data end the dimensions are not updated. There may be other problems too.

Some attributes of Catalog object are lost during PDF to PDF conversion

Dests, OpenAction, URI, PageMode, ViewerPreferences are lost during PDF to PDF conversion. Other attributes have not been checked.

The loss happens diring PDF interpretation. GS can generate these attributes from pdfmark's.

March 25, 2001.

GS doesn't handle names of separations with HalftoneType 5.

PLRM3 says, that HalftoneType 5 may use user defined names of separations. Neither zht2.c nor cmd_put_drawing_color in gxclpath.c can handle this. GS chooses default halftone component for any non-standard separation name.

Bug #406643, March 7, 2001.

PDF 1.4 images don't deallocate all memory

The pdf14_begin_typed_image() function in the PDF 1.4 device creates a marking device, but this is not freed on end_image. The garbage collector will free it, so it's not a real memory leak, but it would still be nicer to free it explicitly.

Truetype fonts are written with incorrect table checksums

psf_write_truetype_data() writes truetype fonts with incorrect checksums on most tables. Most truetype interpreters ignore these so in practice the issue hasn't been a problem. Nevertheless, Ghostscript is embedding off-spec fonts in pdf documents.

A complete fix should generate font data in 2 passes: the first pass computes the checksums, the second one really writes data. Fonts can be very large, so buffering the entire font is not a good solution. The checksums can't be modified after the data is written because the output stream may not be positionable (likely it's a FlateEncode filter).

Igor suggests implementing a special encoding filter for checksums, and executing the body of psf_write_truetype_data twice: first with the checksum filter, second with the real output stream. After a TT table is completed, its checksum to be taken from the filter and to be put into the 'tables' array.

Bug #615620, September 27, 2002.

Driver Issues.

[ ] Missing text in landscape mode.

Using GSWIN32C.EXE with djet500 to print a file in landscape mode on a HP 2000C, the first 3 characters on the left margin are missing.
When the postscript file is editted to use a larger offset (1st moveto parameter), the text appears ok.
When the postscript file is sent to a printer with a builtin postscript interpreter, it prints ok.

Bug #206652

A possible work around is to send the following postscript file to the printer prior to printing the problem file. This works but it leaves a .5" margin at the top and left which is may be ok for some uses.

% Reset the offset and margins.
    /PageOffset [-12 -18]
    /Margins [0 0]
    /.HWMargins [0 0 0 0]
This is an instance of the endless struggle with printer margins, especially for HP printers. The HP drivers are inconsistent as to whether the user space (0,0) should be the physical corner of the page (as it is in PostScript) or the corner of the printable area, and if the latterm whether the page should be clipped or scaled.


Incremental loading for CIDFontType 2 and TrueType fonts.

Entire TrueType outline data in CIDFontType 2 and TrueType fonts are loaded into memory at once. Incremental loading of the outline data is indispensable for practical use of Asian fonts.

There is one other type of CID-keyed font that should also be loaded incrementally: CFF CIDFontType0, i.e., a CIDFontType 0 font represented using the compact binary CFF format. This is important because this is one of the two variants of Asian OpenType fonts (the other is essentially the same as TrueType). Ghostscript already supports both of these OpenType variants, but not with incremental loading.

Bug #223992, November 30, 2000.

We suggest that anyone who would like to work on this project start by looking at how CIDFontType 0 fonts do incremental loading (lib/ and psi/zfcid0.c). Probably much of this code can be also be used with CIDFontType 2 and TrueType fonts.

Differences from Adobe Implementation.

pdfwrite + TT font => Acrobat 3.x for Windows gives error

Running ps2pdf12 on the file produces a PDF on which Acrobat 3.x for Windows complains about not being able to find or create a particular TrueType font that is embedded in the PDF file. However, Acrobat 3.x for other platforms, and Acrobat 4.x for all platforms, accepts the file.

Bug #201955, February 14, 2000.

Since Acrobat 3 is superseded by Acrobat 4 which is available at no charge, and the file produced by Ghostscript meets published PDF specification, this will most likely be left as is.

Inconsistent handling of /Orientation.

PLRM says "The dictionary returned by currentpagedevice always contains an entry for every parameter supported by the device". GS prints both messages in the following program:
currentpagedevice /Orientation known not 
{ (This printer does _not_ support Orientation.) = 
<</Orientation 1gt;gt; setpagedevice 
currentpagedevice /Orientation known 
{ (Err... wait... it does.) = 
Bug #220967, October 31, 2000.

The handling of Orientation is a mess. The PLRM says quite explicitly that it is only supported for roll devices, where the page size alone doesn't give enough information to decide whether to rotate the page.

The reason that Ghostscript accepts it for other devices at all is twofold: displays are like roll media in that they don't have an inherent orientation, and almost none of the other Ghostscript devices actually specify their page sizes. Both of these reasons are now poorly motivated: displays should behave like portrait-orientation devices (albeit with variable page dimensions), rotating the image if the requested page width is greater than the height, and now that setpagedevice and the Resource machinery are fully implemented, all printer drivers should be updated to provide the paper size information. Once these fixes are made (which will probably have some repercussions other places in the code), Ghostscript will handle Orientation properly.

This should be addressed when the "setpagedevice in C" project is completed since part of this will require printer drivers to make page size information available to the setpagedevice logic.

Filesystem implementation differences.

Adobe implementations often treat the filesystem as flat. This means that the path separator characters are not handled as special characters in filenames. The PLRM states that file names are implementation specific (section 3.8.2) and Ghostscript currently implements filenames that conform with the underlying operating system as is stated in this section about the %os% device. This can result from behaviour that is different from Adobe printer implementations.

Current implementation is incompatible with most font installers. Installers expect that:

Cannot load Adobe's fonts.

The following program fails with Adobe fonts:
{ cvn findfont pop 
} 255 string /Font resourceforall 
Bug #226462, December 20, 2000.

The 'findfont' operator and '/Font resourceforall' are very difficult to keep consistent, because the same logic algorithms must be implemented in two different ways. The problem is likely to be in lib/, lib/, and lib/

Bug #226391, December 19, 2000.

ps2ascii can't handle incremental fonts

ps2ascii fails with rangecheck on incremental fonts. Need to recognise incremental fonts and say that incremental fonts are impossible to convert to ASCII.

Bug #441959 keeps good test data for this.

Buffering in input filters

The following program prints differently to stdout on GS and Adobe :

  { currentfile =string readline pop
    dup ==
    (%) anchorsearch { pop } if
  } bind def
  { //proc /ASCIIHexDecode filter 
    3 string readstring pop ==
  } bind def

(start) ==


(stop) ==


Adobe fills entire input buffer of ASCIIHexDecode with procedure's output, before passing data to ASCIIHexDecode, and without knowledge how much data does ASCIIHexDecode want. GS does know the size of data requested, so as the procedure is called exact number of times. Thus, GS is more conservative.

Anoter useful test to be made by repeating lines %31-%39 hundred times, without intermediate empty lines.

Improper handling of hybrid fonts.

Hybrid fonts are described in section 9.2 of the "Adobe Type 1 Font Format" book. Such fonts cannot load into global VM due to internal usage of save/restore (and should do into local VM). Hybrid fonts can be recognized by the appearance of the word 'hires' with a pre-scan over the font, the same way that .findfontvalue works now.

Copyright © 2000-2018 Artifex Software, Inc. All rights reserved.

This software is provided AS-IS with no warranty, either express or implied. This software is distributed under license and may not be copied, modified or distributed except as expressly authorized under the terms of that license. Refer to licensing information at or contact Artifex Software, Inc., 1305 Grant Avenue - Suite 200, Novato, CA 94945, U.S.A., +1(415)492-9861, for further information.

Ghostscript version 9.23, 21 March 2018