From dd5ad6b6b5aed3db62bc03b89acf90c68795edb4 Mon Sep 17 00:00:00 2001 From: Nathan Willis Date: Fri, 24 May 2019 20:30:22 +0100 Subject: [PATCH] Usermanual-buffers-chapter: trim out fallback-of-ufuncs talk and just mention that stuff exists if you care to go find it. --- ...manual-buffers-language-script-and-direction.xml | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/docs/usermanual-buffers-language-script-and-direction.xml b/docs/usermanual-buffers-language-script-and-direction.xml index 57f3920a7..e9585c467 100644 --- a/docs/usermanual-buffers-language-script-and-direction.xml +++ b/docs/usermanual-buffers-language-script-and-direction.xml @@ -300,12 +300,13 @@ decomposing code points. - At build time, HarfBuzz looks first for the GLib library. If - it is found, HarfBuzz will use GLib's Unicode functions by - default. If there is no GLib, HarfBuzz will look for the - International Components for Unicode (ICU) library. If neither - GLib nor ICU is found, HarfBuzz will fall back to its own - internal, lightweight set of Unicode functions instead. + HarfBuzz includes its own internal, lightweight set of Unicode + functions. At build time, it is also possible to compile support + for some other options, such as the Unicode functions provided + by GLib or the International Components for Unicode (ICU) + library. Generally, this option is only of interest for client + programs that have specific integration requirements or that do + a significant amount of customization. If your program has access to other Unicode functions, however,