LibOFX is a parser and API designed to allow applications to support
OFX command responses, usually provided by financial institutions for
statement downloads. The author says, "To my knowledge, it is the first
working OpenSource implementations of the OFX (Open Financial eXchange)
specification on the client side. This project was first started as my
end of degree project, with the goal of adding OFX support to GnuCash.
It has since evolved into a generic library, so all OpenSource
Financial software can benefit from it."

libspectre is a small library for rendering Postscript documents. It
provides a convenient easy to use API for handling and rendering
Postscript documents.

XML is slow to parse and strings inside the document cannot be
memory mapped as they do not have a trailing NUL char. The libxmlb
library takes XML source, and converts it to a structured binary
representation with a deduplicated string table -- where the
strings have the NULs included.

This allows an application to mmap the binary XML file, do an XPath
query and return some strings without actually parsing the entire
document. This is all done using (almost) zero allocations and no
actual copying of the binary data.

This package contains a repository of data files describing media player
(mostly USB Mass Storage ones) capabilities. These files contain information
about the directory layout to use to add music to these devices, about the
supported file formats, ... These capabilities used to be provided by HAL
in the 10-usb-music-players.fdi file but had to be moved elsewhere as part
of the big HALectomy.

Poppler is a fork of the xpdf PDF viewer developed by Derek Noonburg of
Glyph and Cog, LLC. There are two reasons for forking xpdf. First, to
provide PDF rendering functionality as a shared library to centralize
the maintenence effort. Today a number of applications incorporate the
xpdf code base and whenever a security issue is discovered, all these
applications exchange patches and put out new releases. In turn, all
distributions must package and release new versions of these xpdf based
viewers. Due to this, there is a lot of duplicated effort. Even if
poppler in the short term introduces yet another xpdf-derived code base
to the world, hopefully, over time these applications will adopt
poppler. After all, only one application needs to use poppler to break
even.

Second, libpoppler intends to move forward in a number of areas that do
not fit within the goals of xpdf. By design, xpdf depends on very few
libraries and runs on a wide range of X-based platforms. This is a
strong feature and reasonable design goal. However, poppler intends to
replace parts of xpdf that are now available as standard components of
modern Unix desktop environments. One such example is fontconfig,
which solves the problem of matching and locating fonts on the system
in a standardized and well understood way. Another example is cairo,
which provides high quality 2D rendering. See the file TODO for a list
of planned changes.

This package consists of encoding files for use with poppler. The
encoding files are optional and poppler will automatically read them if
they are present. When installed, the encoding files enables poppler
to correctly render CJK and Cyrrilic properly. While poppler is
licensed under the GPL, these encoding files are copyright Adobe and
licensed much more strictly, and thus distributed separately.

This package is a placeholder only - there is no real data

The shared-color-profiles package contains various profiles which are
useful for programs that are color management aware.

Wayland protocols that adds functionality not
available in the Wayland core protocol. Such protocols either adds
completely new functionality, or extends the functionality of some other
protocol either in Wayland core, or some other protocol in
wayland-protocols.

This is an internal package that is used to create the patterns as part
of the installation source setup. Installation of this package does
not make sense.

This particular package contains the Xfce patterns.

Wayland protocols that adds functionality not
available in the Wayland core protocol. Such protocols either adds
completely new functionality, or extends the functionality of some other
protocol either in Wayland core, or some other protocol in
wayland-protocols.

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