Differences between revisions 1 and 20 (spanning 19 versions)
Revision 1 as of 2005-08-25 16:02:16
Size: 1914
Editor: OwenTaylor
Comment:
Revision 20 as of 2021-02-05 13:42:53
Size: 2070
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
Pango is a library for layout and rendering of text, with an emphasis
on internationalization. Pango can be used anywhere that text layout
is needed, though most of the work on Pango so far has been done in
the context of the GTK+ widget toolkit. Pango forms the core of text
and font handling for GTK+-2.x.
Pango is a library for laying out and rendering of text, with an emphasis on internationalization. Pango can be used anywhere that text layout is needed, though most of the work on Pango so far has been done in the context of the [[https://www.gtk.org|GTK]] widget toolkit. Pango forms the core of text and font handling for GTK
Line 12: Line 8:
Pango is designed to be modular; the core Pango layout engine can
be used with different font backends. There are two basic backends,
with multiple options for rendering with each.
Pango is designed to be modular; the core Pango layout engine can be used with different font backends. There are three basic backends, with multiple options for rendering with each.
Line 16: Line 10:
 * 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. (Optionally using Uniscribe for complex-text handling). Rendering can be done via Cairo or directly using the native Win32 API.
 * Client side fonts using the Free``Type and fontconfig libraries, using HarfBuzz for complex-text handling. 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 for complex-text handling. Rendering can be done via Cairo or directly using the native Win32 API.
 * Native fonts on MacOS X using CoreText for complex-text handling, rendering via Cairo.
Line 19: Line 14:
The integration of Pango with Cairo (http://cairographics.org)
provides a complete solution with high quality text handling
and graphics rendering.
The integration of Pango with [[https://cairographics.org/|Cairo]] provides a complete solution with high quality text handling and graphics rendering.
Line 23: Line 16:
Dynamically loaded modules then handle text layout for particular
combinations of script and font backend. Pango-1.10 ships with a wide
selection of modules, including modules for Hebrew, Arabic, Hangul,
Thai, and a number of Indic scripts. Virtually all of the world's major
scripts are supported.
Dynamically loaded modules then handle text layout for particular combinations of script and font backend. Pango ships with a wide selection of modules, including modules for Hebrew, Arabic, Hangul, Thai, and a number of Indic scripts. Virtually all of the world's major scripts are supported.
Line 29: Line 18:
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.
As well as the low level layout rendering routines, Pango includes Pango``Layout, a high level driver for laying out entire blocks of text, and routines to assist in editing internationalized text.
Line 33: Line 20:
More information about Pango is available from http://www.pango.org/. Pango depends on 2.x series of the GLib library; more information about GLib can be found at: https://www.gtk.org/
Line 35: Line 22:
Pango depends on version 2.6.0 or newer of the GLib library; more
information about GLib can be found at http://www.gtk.org/.
If this information is insufficient, please see also: https://developer.gnome.org/pango/
----
CategoryHomepage

Pango is a library for laying out and rendering of text, with an emphasis on internationalization. Pango can be used anywhere that text layout is needed, though most of the work on Pango so far has been done in the context of the GTK widget toolkit. Pango forms the core of text and font handling for GTK

Pango is designed to be modular; the core Pango layout engine can be used with different font backends. There are three basic backends, with multiple options for rendering with each.

  • Client side fonts using the FreeType and fontconfig libraries, using HarfBuzz for complex-text handling. 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 for complex-text handling. Rendering can be done via Cairo or directly using the native Win32 API.
  • Native fonts on MacOS X using CoreText for complex-text handling, rendering via Cairo.

The integration of Pango with Cairo 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. Pango ships with a wide selection of modules, including modules for Hebrew, Arabic, Hangul, Thai, and a number of Indic scripts. Virtually all of the world's major scripts are supported.

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.

Pango depends on 2.x series of the GLib library; more information about GLib can be found at: https://www.gtk.org/

If this information is insufficient, please see also: https://developer.gnome.org/pango/


CategoryHomepage

Introduction (last edited 2023-08-29 09:34:25 by EmmanueleBassi)