From 07961daed06d181615d8087b25122985c83760cc Mon Sep 17 00:00:00 2001 From: Oleg Oshmyan Date: Sat, 24 Oct 2020 21:58:02 +0300 Subject: [PATCH] [docs] Describe buffer context applicability more explicitly Make it abundantly clear that the context's script etc. don't matter. Fixes https://github.com/harfbuzz/harfbuzz/issues/2730 --- docs/usermanual-buffers-language-script-and-direction.xml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/usermanual-buffers-language-script-and-direction.xml b/docs/usermanual-buffers-language-script-and-direction.xml index d98c79b7f..0235d2d39 100644 --- a/docs/usermanual-buffers-language-script-and-direction.xml +++ b/docs/usermanual-buffers-language-script-and-direction.xml @@ -136,10 +136,12 @@ determine which glyph to return. - The safest approach is to add all of the text available, then - use item_offset and + The safest approach is to add all of the text available (even + if your text contains a mix of scripts, directions, languages + and fonts), then use item_offset and item_length to indicate which characters you - want shaped, so that HarfBuzz has access to any context. + want shaped (which must all have the same script, direction, + language and font), so that HarfBuzz has access to any context. You can also add Unicode code points directly with