Two sets of free fonts are supplied
by Ghostscript:

ghostscript-fonts-std

Several Type 1 basic PostScript fonts.
Times, Helvetica, Courier, Symbol, etc.
Contributed by URW++ Design and Development
Incorporated, of Hamburg, Germany.

ghostscript-fonts-other

A miscellaneous set including Cyrillic,
kana, and fonts derived from the free
Hershey fonts, with improvements (such as
adding accented characters) by Thomas Wolff.
The Hershey-based fonts are quite different
from traditional printer or display fonts;
you can read about them in more detail in
the documentation on Hershey fonts.

The "ghostscript" package might be incompatible
with the official openSUSE "ghostscript-library"
package.

See "Package clean-up and upgrade to latest
stable release" at

https://bugzilla.novell.com/show_bug.cgi?id=735824

You need the packages ghostscript and
ghostscript-x11 which replace the official
packages ghostscript-library and
ghostscript-x11 (provided you have already
the package ghostscript-x11 installed).

Do not remove installed ghostscript-fonts-*
packages.

To replace the official packages, you must
install ghostscript and ghostscript-x11
in one run, e.g.:

# rpm -Uhv ghostscript-*.rpm ghostscript-x11-*.rpm

To go back to the official packages, you must
first remove the ghostscript and ghostscript-x11
package and ignore RPM package dependencies, e.g.:

# rpm -e --nodeps ghostscript ghostscript-x11

Then you can re-install the official packages,
e.g.:

# rpm -Uhv ghostscript-library-*.rpm ghostscript-x11-*.rpm

Be careful that you specify during installation
the exact right ghostscript-x11-*.rpm package
(with exact matching version-release) - otherwise
you get RPM conflicts.

In general please read

https://build.opensuse.org/project/show?project=Printing

The grep command searches one or more input files
for lines containing a match to a specified pattern.
By default, grep prints the matching lines.

The Gutenprint (formerly Gimp-Print) printer drivers for CUPS.
See the user's manual at /usr/share/gutenprint/doc/gutenprint-users-manual.pdf

The Hewlett-Packard Linux Imaging and Printing project (HPLIP) provides
a unified single and multifunction connectivity solution for HP
printers and scanners (in particular, HP all-in-one devices).

HPLIP provides unified connectivity for printing, scanning, sending
faxes, photo card access, and device management and is designed to work
with CUPS.

It includes the Ghostscript printer driver HPIJS for HP printers and a
special "hp" CUPS back-end that provides bidirectional communication
with the device (required for HP printer device management).

It also includes the SANE scanner driver "hpaio" for HP all-in-one
devices. Basic PC send fax functionality is supported on a number of
devices.

The special "hpfax" CUPS back-end is required to send faxes. Direct
uploading (i.e. without print and scan) of received faxes from the
device to the PC is not supported.

The "hp-toolbox" program is provided for device management.

The "hp-sendfax" program must be used to send faxes.

The "hp-setup" program can be used to set up HP all-in-one devices.

The HPLIP project is open source software and uses GPL-compatible
licenses. For more information, see:

http://hplipopensource.com

/usr/share/doc/packages/hplip/index.html

This library is intended to be used by applications that need to
communicate with (or at least identify) devices that are attached via a
parallel port.

For Linux, there are some wrinkles in communicating with devices on
parallel ports (see /usr/share/doc/packages/libieee1284/README). The
aim of this library is to take all the worry about these wrinkles from
the application. It figures out which method is appropriate for the
currently running kernel. For instance, if the application wants to
know the device ID of a device on a particular port, it asks the
library for the the device ID. The library then figures out if it is
available via /proc (in any of the possible locations) and, if not,
tries asking the device itself. If /dev/parport0 is not available for
use, it tries ioperm; if that fails, it tries /dev/port. The
application does not have to care.

This is an open source Linux printer driver for the Konica Minolta
magicolor 2300W and 2400W color laser printers. It requires Ghostscript
and foomatic-filters. It is recommended to use this driver with CUPS.

The current version 0.51 was released 2005-10-16 and
the m2300w driver is no longer actively maintained
which means that help, a workaround, or a bugfix
is rather unlikely if there are issues with this driver.

PPD files from printer manufacturers that are under a free license.

For example, the original MIT license, shown for example under
http://www.opensource.org/licenses/mit-license.php, is okay but not an
often used modified MIT license, which does not allow redistribution if
the file was altered in any way from its original form.

If you have a PostScript printer and there is no PPD file included in
this package, ask your printer manufacturer for a PPD file or visit
http://www.linuxprinting.org/ppd-doc.html.

To set up a printer configuration a printer description file
(PPD file) is required.

A printer description file is not a driver.

For non-PostScript printers a driver is needed
together with a PPD file which matches exactly
to the particular driver.

For PostScript printers, a PPD file alone is sufficient
(except for older PostScript level 1 printer models).

The PPD files are provided in the following sub-packages
depending on which kind of driver software is needed:

OpenPrintingPPDs-ghostscript provides PPDs
which use Ghostscript built-in drivers.

OpenPrintingPPDs-hpijs provides PPDs
which use the hpijs driver from HPLIP.

OpenPrintingPPDs-postscript provides PPDs
which need no driver.

Python Bindings for CUPS, the Common Unix Printing System

The software consists of SANE scanner drivers, "scanimage," and the
"saned" daemon.

A SANE scanner driver is used via a SANE front-end. This package
contains the command line front-end "scanimage". There are various
graphical front-ends like "xscanimage" (package sane-frontends), XSane
(package xsane), and the KDE front-end Kooka (package
kdegraphics3-scan).

The "saned" daemon provides the service "sane-port" to access scanners
that are connected to a server via network from client hosts that run
the "net" meta driver.

This package contains the YaST2 component for printer configuration.

This package provides support for the configuration of USB scanners,
SCSI scanners, scanners in HP all-in-one devices, and scanning via
network (i.e. use a remote scanner via another host in the network).

Parallel port scanners and network scanners (i.e. a scanner which is
directly accessible in the network) cannot be configured with this
tool, except for such scanners in HP all-in-one devices. Usually those
devices must be configured manually. For more information see
http://www.sane-project.org/ and the documentation in the package
"sane-backends".

The "Printing" project is the development project
for packages which provide the base functionality
of the printing system.

The main intent of the "Printing" project is
to provide the newest kind of base printing software for
upcoming openSUSE and SUSE Linux Enterprise versions
and at the same time with same priority to provide the
same newest base printing software also for as many
released openSUSE and SUSE Linux Enterprise versions
as far as possible with reasonable effort.

Base printing software packages are in particular
print spooler software like CUPS,
printing filters like cups-filters,
printer drivers like HPLIP or Gutenprint,
printer driver related software like Ghostscript,
plain PPD files packages like OpenPrintingPPDs,
and other software which directly
belongs to the base printing system
like special backends for CUPS.

In contrast software which does not directly
belong to the base printing system like
user frontends (e.g. printer setup tools,
printing dialog GUIs, or other printing
related GUIs) or applications with a major
focus on printing (e.g. LaTeX or Scribus)
do usually not belong to the "Printing" project.

Of course only really free software can be
accepted in the "Printing" project.

In particular printer driver software which
is not 100% free software cannot be accepted
regardless how nice it would be when this
or that awkward printer model would work.

We will not risk any legal issue for openSUSE
and SUSE Linux Enterprise and our users and
contributors when software where the legal state
is not clear would be accepted.

An obvious precondition for any software is
that it is by default reasonably secure.
In particular for software that is run as root
(e.g. a setup tool or a special CUPS backend)
a security audit is usually required.

The "Printing" development project may contain
new software or work-in-progress changes of
existing software that might neither be in
a stable state nor fit well into currently
installed systems.

Have this in mind if you think about to install
packages from the "Printing" project into your
currently running system.

Do not use "Factory" if your system is not "Factory".
Use the matching packages for your particular system.

The packages in the "Printing" project are without
any guarantee or warranty and without any support.

As an extreme example, this means if your
complete computer center crashes because
of those packages, it is only your problem.

On the other hand this does not mean that those
packages are known to be terrible broken but
they are not thoroughly tested so that any
unexpected issue can happen.

In the end all software in the "Printing" project
are only applications which means that your system
should not "explode" when you upgrade with packages
from the "Printing" project (provided you use the
matching packages for your particular system).

If a new version does not work it should usually
help to downgrade (and to reconfigure as needed)
to get it working again.

When there are issues with the packages in the
"Printing" project we appreciate issue reports.

Regarding how to report a printing issue see
https://en.opensuse.org/SDB:How_to_Report_a_Printing_Issue

For developers:

In general see
https://en.opensuse.org/Portal:Factory_contribution
and
https://en.opensuse.org/openSUSE:How_to_contribute_to_Factory

In particular regarding how to contribute
to the "Printing" project see
https://en.opensuse.org/openSUSE:How_to_contribute_to_the_Printing_project

If you like to contribute major changes
for a package in the "Printing" project
first and foremost get in contact with the
maintainers of the particular package or
the maintainers of the "Printing" project.

This avoids that you do major work on your own
which might not be accepted by the package
maintainers.

The openSUSE Build Service (OBS) web pages
show maintainers of a particular package and
the maintainers of the "Printing" project.

The RPM changelog shows e-mail addresses of
those who had worked on an installed package:
"rpm -q --changelog package_name"