Lpdfilter is a collection of scripts used for
printing various data with lpr(1) and lpd(8).
An entry for lpdfilter in /etc/printcap
is required (see printcap(5)) to enable
these scripts. This can be done by using
the lprsetup script.

Authors:
--------
Werner Fink

The LPRng software is an enhanced, extended,
and portable implementation of the Berkeley LPR
print spooler functionality. While providing
the same interface and meeting RFC1179 requirements,
the implementation is completely new and provides
support for the following features: lightweight
(no databases needed) lpr, lpc, and lprm programs;
dynamic redirection of print queues; automatic
job holding; highly verbose diagnostics; multiple
printers serving a single queue; and a greatly
improved permission and authorization mechanism.

LPRng provides emulation packages for the SVR4 lp
and lpstat programs, eliminating the need for
another print spooler package. These emulation
packages can be modified according to local
requirements to support vintage printing systems.

Attention: Interoperability with older LPD
implementations requires privileged access
to ports. Therefore all affected client-programs
ship with SUID root privileges.

Authors:
--------
Patrick Powell

A driver for Lexmark printers 7000, 7200,
and 5700. This driver translates PBM
(Portable Bitmap) into the printer protocol.

This is the Publishing project. Its main purpose is to serve as development project for packages around the topic of publishing in the openSUSE:Factory distribution. If you want to participate you can contact us individually. Please report bugs to the respective bugowners as set.

NOTE: Automatically created during Factory devel project migration by admin.

NOTE: Automatically created during Factory devel project migration by admin.

NOTE: Automatically created during Factory devel project migration by admin.

NOTE: Automatically created during Factory devel project migration by admin.

NOTE: Automatically created during Factory devel project migration by admin.

NOTE: Automatically created during Factory devel project migration by admin.

NOTE: Automatically created during Factory devel project migration by admin.

NOTE: Automatically created during Factory devel project migration by admin.

NOTE: Automatically created during Factory devel project migration by admin.

NOTE: Automatically created during Factory devel project migration by admin.

NOTE: Automatically created during Factory devel project migration by admin.

Texinfo is a documentation system that uses a single source file to
produce both online information and printed output. Using Texinfo, you
can create a printed document with the normal features of a book,
including chapters, sections, cross-references, and indices. From the
same Texinfo source file, you can create a menu-driven, online info
file with nodes, menus, cross-references, and indices using the included
makeinfo tool.

NOTE: Automatically created during Factory devel project migration by admin.

Currently do not use this tree as it has problems!

Build Environment for fetching data from TeX Live servers and creating the appropriate spec files as well as then building with those spec files the TeX Live binary rpms from scratch if possible as well as repacking the TeX Live texmf tar balls into rpms.

WARNING:

Please do not mix upstream TeX Live installation with rpm based TeX Live packages. The dependencies base on rpm data base can not be fulfilled with those of the upstream TeX Live packages.

The script environment for fetching data from the TeX Live Network and creating spec files. The perl script `generate' will read the data base `texlive.tlpdb.xz' from TeX Live and will generate the spec file to the basesystem. This spec file is used in the package `texlive' to e.g. build `texlive-filesystem', the various
collections and scheme packages as well as the binary packages. Also `generate' generates the spec files for most noarch TeX Live package found in `texlive.tlpdb.xz'. With this as a tarball `texlive-specs.tar.xz' and the spec file `texlive-specs.spec' more than 4200 packages will build.

The `generate' requires the package `avfs' from the project `Archiving' as otherwise it is not able to fix various problems like wrong script permissions or wrong she-bang lines.

After installing texlive and the package texlive-latex, find a large selection of documentation for TeX, LaTeX, and various layout styles in /usr/share/texmf/doc.

TeX (pronounced tech) is an interpreter for text formatting and was developed by Donald E. Knuth. It works with control and macro commands on a text file. Working with TeX is similar to typesetting methods. LaTeX is a complex macro package that removes the cryptical TeX interface and does most of the work for the user.

TeX uses special fonts produced by the MetaFont program. Various printer drivers and an X11 viewer are also included in this package. The teTeX package is based on the standard TeX package of Karl Berry, which makes configuration much easier. It is also possible to use PostScript fonts. A real PostScript printer is required, however. If the ghostscript (gs) package is installed, all drivers for printing and viewing can use these fonts. Note, however, that the fonts included in the ghostscript package are not identical to Adobe's PostScript fonts. The copyright prohibids us to include them on the CD.

Besides these features, the programs MakeIndex (for producing indexes) and BibTeX (for literature data processing) exist.

The texlive package includes a full texmf tree, many programs like tex, dvips, etc., shell script configuration, and a big collection of documentations. This package is easily configured by the script texconfig and has multilanguage options.

The basic file system layout for TeX Live installation.

Links to frozen TeXLive 2020