summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKhaled Hosny <khaledhosny@eglug.org>2018-12-10 01:42:25 +0200
committerKhaled Hosny <khaledhosny@eglug.org>2018-12-10 01:42:25 +0200
commitc8793f5df3b63f76c37b04384eabd8c10e44cedc (patch)
tree0d27c2a3d9edff1e0b36ca28b20aac74bfad0fc2
parenta8e5b31a3bf02776e62465852ade45f131eda175 (diff)
downloadpango-c8793f5df3b63f76c37b04384eabd8c10e44cedc.tar.gz
Edit the README.md markdown a bit
-rw-r--r--README.md45
1 files changed, 21 insertions, 24 deletions
diff --git a/README.md b/README.md
index fedd147c..4ed638df 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,6 @@
+Pango
+=====
+
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; however, most of the work on Pango so far has been done using
@@ -8,18 +11,16 @@ Pango is designed to be modular; the core Pango layout 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.
- 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
- script handling. Rendering can be done via Cairo or directly
- using the native Win32 API.
+- 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 for complex
+ script handling. Rendering can be done via Cairo or directly
+ using the native Win32 API.
+- Native fonts on MacOS X with the CoreText framework, rendering via
+ Cairo.
- - Native fonts on MacOS X with the CoreText framework, rendering via
- Cairo.
-
-The integration of Pango with Cairo (http://cairographics.org)
+The integration of Pango with [Cairo](https://cairographics.org)
provides a complete solution with high quality text handling
and graphics rendering.
@@ -29,24 +30,21 @@ and routines to assist in editing internationalized text.
For more information about Pango, see:
- http://www.pango.org/
+ https://www.pango.org/
Dependencies
-============
-
+------------
Pango depends on the GLib library; more information about GLib can
-be found at http://www.gtk.org/.
+be found at https://www.gtk.org/.
To use the Free Software stack backend, Pango depends on the following
libraries:
- * FontConfig for font discovery (http://www.fontconfig.org),
+- [FontConfig](https://www.fontconfig.org) for font discovery,
+- [FreeType](https://www.freetype.org) for font access,
+- [HarfBuzz](http://www.harfbuzz.org) for complex text shaping
- * FreeType for font access (http://www.freetype.org),
-
- * HarfBuzz for complex text shaping (http://www.harfbuzz.org/)
-
-Cairo support depends on the Cairo library (http://cairographics.org).
+Cairo support depends on the [Cairo](https://cairographics.org) library.
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.
@@ -54,14 +52,13 @@ 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
+Xft is available from https://xlibs.freedesktop.org/release/. You'll
need the libXft package, and possibly the libXrender and renderext
packages as well. You'll also need FontConfig.
Installation of Pango on Win32 is possible, see README.win32.
License
-=======
-
+-------
Most of the code of Pango is licensed under the terms of the
GNU Lesser Public License (LGPL) - see the file COPYING for details.