Copyright (C) 1990, 1995, 1996, 1997 Aladdin Enterprises.  All rights reserved.
  
  This file is part of GNU Ghostscript.
  
  GNU Ghostscript is distributed in the hope that it will be useful, but
  WITHOUT ANY WARRANTY.  No author or distributor accepts responsibility to
  anyone for the consequences of using it or for whether it serves any
  particular purpose or works at all, unless he says so in writing.  Refer to
  the GNU General Public License for full details.
  
  Everyone is granted permission to copy, modify and redistribute GNU
  Ghostscript, but only under the conditions described in the GNU General
  Public License.  A copy of this license is supposed to have been given to
  you along with GNU Ghostscript so you can know your rights and
  responsibilities.  It should be in a file named COPYING.  Among other
  things, the copyright notice and this notice must be preserved on all
  copies.
  
  Aladdin Enterprises is not affiliated with the Free Software Foundation or
  the GNU Project.  GNU Ghostscript, as distributed by Aladdin Enterprises,
  does not depend on any other GNU software.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

This file, current.txt, describes problems and new features in the current
release of Ghostscript.  This file describes version 5.10 of Ghostscript.

For an overview of Ghostscript and a list of the documentation files, see
README.

New features (since release 5.03)
============

(This is not a complete list of new features: see NEWS for details.)

ps2pdf (and the pdfwrite device) now produces much more compact output.  By
default, the output is compatible only with Acrobat 3.x; for Acrobat
2.x-compatible output, use
	ps2pdf -dCompatibilityLevel=1.1 ...

ps2pdf now has more flexibility about the handling of unencoded glyphs.  See
gdevpdft.c for details.

ps2pdf now recognizes the CompressPages, CompatibilityLevel, and
UseFlateCompression device (distiller) parameters.

The PDF interpreter now handles Lab and Separation color spaces, images with
color space resources, embedded font subsets, undefined operators with
BX/EX, and Functions.

Changes
=======

The RGB<->CMYK conversion rules have been changed back to Adobe's documented
rules.

Known problems
==============

(This is not a complete list of known problems: see NEWS for details.)

Usage
-----

On a MS-DOS system, interrupting the interpreter by typing ^C doesn't
restore the display mode.

Limitations
-----------

serialnumber returns the same value in all copies.

Some floating point exceptions terminate the interpreter, rather than
producing a limitcheck error.

The DCTEncode filter disregards the Blend parameter, and uses different
QuantTables and HuffTables from Adobe's.

The DCT filters do not support nonintegral sample ratios.  Also, DCTEncode
will not create files with Sum(HS*VS)>10 (regardless of the value of the
Relax parameter) because they violate the JPEG standard; but DCTDecode will
read such files.

The size of the execution stack cannot be changed dynamically.  (However,
the sizes of the operand and dictionary stacks can be changed.)

Separation color spaces are implemented, but devices that actually produce
color separations are not supported.  The special color separations All and
None, and the primary separations (Red, Green, etc.), are not supported.

execform and ucache are implemented, but they do not actually do any
caching; setucacheparams and ucachestatus are dummies.  (This only impacts
performance, not functionality.)

The image operator only honors the Interpolate flag in the image dictionary
if the combined transformation (ImageMatrix + CTM) doesn't involve rotation,
skewing, or X-reflection; imagemask doesn't honor Interpolate at all.

Some path building operations that would generate a device coordinate larger
than +/-2^19 will cause a limitcheck.  However, the common ones ([r]moveto,
[r]lineto, [r]curveto, closepath) will not.

Graphics bugs
-------------

Opening more than one window device at the same time doesn't work.
This is the case for both X Windows and Microsoft Windows.

cshow doesn't work with composite fonts.

Non-graphics bugs
-----------------

The %statementedit pseudo-file is equivalent to %lineedit.  As a
consequence, the interactive interpreter requires that every statement fit
on a line, i.e., you can't have an unpaired (, {, or <.

The following operators that expect arrays won't accept packed arrays:
	definefont (Subrs (type 1 fonts))

Syntax errors occurring within a binary token do not produce the error
message specified by the Adobe documentation.

save doesn't save, and restore doesn't restore, the user parameters.