Merge pull request #2733 from astiob/buffer-context-doc
[docs] Describe buffer context applicability more explicitly
This commit is contained in:
commit
5091ea7e24
|
@ -136,10 +136,12 @@
|
||||||
determine which glyph to return.
|
determine which glyph to return.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
The safest approach is to add all of the text available, then
|
The safest approach is to add all of the text available (even
|
||||||
use <parameter>item_offset</parameter> and
|
if your text contains a mix of scripts, directions, languages
|
||||||
|
and fonts), then use <parameter>item_offset</parameter> and
|
||||||
<parameter>item_length</parameter> to indicate which characters you
|
<parameter>item_length</parameter> 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.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
You can also add Unicode code points directly with
|
You can also add Unicode code points directly with
|
||||||
|
|
Loading…
Reference in New Issue