NEWS
****

The currently released version of the Display Ghostscript System is
`0.5.8'.

Changes since version `0.5.7'
=============================

   DGS can run on a machine with a different byte order from the one it
receives client data from.

   Multiple contexts and context switching has been implemented.

   DGS also launches a server faster (after the first one), by forking
a new server for the new process.

   Features:

  1. You can change mode of debug via arguments passed to dpsnx.agent.

     dpsnx.agent debug=n  # (n=unsigned int).  if n is zero, debug
     printing is disable (default).

  2. You can specify the port number when you call dpsnx.agent directly.

     dpsnx.agent tcp/N N means the port number.


Changes since version `0.5.6'
=============================

   The dgs server accept TCP connection and UNIX connection at a time
if the client runs on the same host of the server or the architecture
of the host where the client runs has same byteorder of the
architecture of the host where the server.

Changes since version `0.5.0'
=============================

   DGS has been updated to include all the work the L. Peter Deutsch did
to upgrade Ghostscript for DPS compatibility (e.g. the 5.50 dgs release,
which is different from our DGS release). This does not have all the
functionality for a full DPS system, but it comes close.

   The current implementaion uses a *fork*-based server. After the
first time the dgs system is started using dpsnx.agent, subsequent calls
to start a DGS context cause the current context to fork a new process.
This is not the best solution, but it is faster than previous methods.

Noteworthy changes in version `0.5.0'
=====================================

   The rather large change in the version number is not due to a
significant change in functionality; instead it was changed to correlate
with the GNUstep 0.5.0 release.

   * Changes have been made so that DGS can be installed in the GNUstep
     directory structure as defined by the GNUstep Makefile Package;
     however, DGS can still be installed like normal Autoconf packages.
     `INSTALL' contains more information.

Noteworthy changes in version `0.2.1'
=====================================

   * Add some additional code so that clients retry and wait longer
     before giving up on the connection with the DGS agent.
     Applications will need to be relinked with the Client library.

   * Previous versions of DGS could not display beyond the standard
     paper size, generally 8.5 inches by 11 inches; so increase the
     size to 22 by 22 inches which should be sufficient for those
     high-res monitors.

Noteworthy changes in version `0.2.0'
=====================================

   * Upgraded the Ghostscript source code to version 4.03.  This also
     includes new fonts.

   * Upgraded jpeg library to version 6a.

   * Now configures, compiles, and installs the jpeg, png, and zlib
     libraries and programs.

   * Slight restructuring of where DGS related libraries files are
     installed; instead of create a subdirectory of DGS within the
     library install directory, ie `/usr/local/lib', the DGS
     subdirectory is placed under the gnustep library directory, ie
     `/usr/local/lib/gnustep'.  This helps keep all of the GNUstep
     related resources together.

Noteworthy changes in version `0.1.1'
=====================================

   * Brought together the Adobe DPSclient library, Aladdin Ghostscript,
     the Aladdin Ghostscript fonts, the PNG library, the JPEG library,
     and the ZLIB library into a single configuration.  All of the
     separate packages are segregated so that it will be relatively
     easy to incorporate newer versions of the individual sources.

   * Incorporated Randy Chapman's patches to the Adobe DPSclient library
     and Aladdin Ghostscript so that they will work together as a
     Display Ghostscript System.

   * Modifications so that the Display Ghostscript System can be
     installed and uninstalled without conflicting with any Ghostscript
     executables and/or library files that exist on the user's system.

   Also see the `ChangeLog' file for more detail.

