From b8e6f17eed5eec3715e9d16f7f3db4c352f6d312 Mon Sep 17 00:00:00 2001 From: Khaled Hosny Date: Sun, 27 Dec 2020 15:03:57 +0200 Subject: [PATCH] [docs] Move note about harfbuzz-old to proper place Commit 443f87213272be5ae0579dce4749b2036dfe3815 seems to have moved it to the API part by mistake. --- docs/harfbuzz-docs.xml | 60 ++++++++++++++++++++---------------------- 1 file changed, 29 insertions(+), 31 deletions(-) diff --git a/docs/harfbuzz-docs.xml b/docs/harfbuzz-docs.xml index 0c1cb6cab..8cbd25cf6 100644 --- a/docs/harfbuzz-docs.xml +++ b/docs/harfbuzz-docs.xml @@ -49,37 +49,6 @@ http://[SERVER]/libharfbuzz/.--> - - - - The current HarfBuzz codebase is versioned 2.x.x and is stable - and under active maintenance. This is what is used in latest - versions of Firefox, GNOME, ChromeOS, Chrome, LibreOffice, - XeTeX, Android, and KDE, among other places. - - - Prior to 2012, the original HarfBuzz codebase (which, these - days, is referred to as harfbuzz-old) was - derived from code in FreeType, Pango, and - Qt. - It is not actively developed or - maintained, and is extremely buggy. All users of harfbuzz-old - are encouraged to switch over to the new HarfBuzz as soon as possible. - - - To make this distinction clearer in discussions, the current - HarfBuzz codebase is sometimes referred to as - harfbuzz-ng. - - - For reference purposes, the harfbuzz-old source tree is archived - here. There - are no release tarballs of harfbuzz-old whatsoever. - - Reference manual @@ -180,4 +149,33 @@ + + + + The current HarfBuzz codebase is versioned 2.x.x and is stable + and under active maintenance. This is what is used in latest + versions of Firefox, GNOME, ChromeOS, Chrome, LibreOffice, + XeTeX, Android, and KDE, among other places. + + + Prior to 2012, the original HarfBuzz codebase (which, these days, is + referred to as harfbuzz-old) was derived from code + in FreeType, + Pango, and + Qt. + It is not actively developed or maintained, and is + extremely buggy. All users of harfbuzz-old are encouraged to switch over + to the new HarfBuzz as soon as possible. + + + To make this distinction clearer in discussions, the current HarfBuzz + codebase is sometimes referred to as harfbuzz-ng. + + + For reference purposes, the harfbuzz-old source tree is archived + here. + There are no release tarballs of harfbuzz-old whatsoever. + + +