Licensing Information

Open Source Used In Cisco FXOS 1.1(4) 922
- Client side fonts using the FreeType and fontconfig libraries.
Rendering can be with with Cairo or Xft libraries, or directly
to an in-memory buffer with no additional libraries.
- Native fonts on Microsoft Windows using Uniscribe if available for
complex script handling. Rendering can be done via Cairo or
directly using the native Win32 API.
- Native fonts on MacOS X, rendering via Cairo.
The integration of Pango with Cairo (http://cairographics.org)
provides a complete solution with high quality text handling
and graphics rendering.
Dynamically loaded modules then handle text layout for particular
combinations of script and font backend.
As well as the low level layout rendering routines, Pango includes
PangoLayout, a high level driver for laying out entire blocks of text,
and routines to assist in editing internationalized text.
For more information about Pango, see:
http://www.pango.org/
Dependencies
============
Pango depends on the GLib library; more information about GLib can
be found at http://www.gtk.org/.
When using client side fonts, the fontconfig library
(http://www.fontconfig.org) to look up fonts. At least version 2.0.9
of the FreeType font handling library (http://www.freetype.org) is
also required.
Cairo support depends on the Cairo library (http://cairographics.org).
The Cairo backend is the preferred backend to use Pango with and is
subject of most of the development in the future. It has the
advantage that the same code can be used for display and printing.
We suggest using Pango with Cairo as described above, but you can also
do X-specific rendering using the Xft library. The Xft backend uses
version 2 of the Xft library to manage client side fonts. Version 2 of
Xft is available from http://xlibs.freedesktop.org/release/. You'll
need the libXft package, and possibly the libXrender and renderext
packages as well. You'll also need fontconfig (see below.)