Lines Matching +full:before +full:- +full:script

2 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
3                "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
7 <chapter id="buffers-language-script-and-direction">
8   <title>Buffers, language, script and direction</title>
13     buffer. We'll also look at a piece of lower-level machinery that
14     you will need to understand before proceeding: the functions that
23   <section id="creating-and-destroying-buffers">
43       This will destroy the object and free its associated memory -
62       While we are on the subject of reference-counting buffers, it is
74   <section id="adding-text-to-the-buffer">
80       the standard Unicode character encodings (UTF-8, UTF-16, or
81       UTF-32). HarfBuzz provides convenience functions that accept
89       You can add UTF-8 text to a buffer by passing in the text array,
109       contents. Also, note that you can use <literal>-1</literal> in
111       if your text array is NULL-terminated. Similarly, you can also use
112       <literal>-1</literal> as the final argument want to add its full
118       attempt to grab the five characters <emphasis>before</emphasis>
121       before and after "context" segments, which are used internally
124       script-specific shaping operations are correct. If there are
125       fewer than five characters available for the before or after
130       tempting to only add smaller sub-segments to a buffer and
135       points before and after each character in order to correctly
143       want shaped (which must all have the same script, direction,
153       to you to do any deep-sanity checking necessary.
158   <section id="setting-buffer-properties">
162       properties set before HarfBuzz can shape their text correctly.
169       indicates that it contains un-shaped input
188       Buffers also need to carry information about the script,
195       hb_buffer_set_language(buf, hb_language_from_string("en", -1));
210       direction, script, and language properties individually.
214       <type>hb_direction_t</type>: left-to-right
215       (<literal>HB_DIRECTION_LTR</literal>), right-to-left (<literal>HB_DIRECTION_RTL</literal>),
216       top-to-bottom (<literal>HB_DIRECTION_TTB</literal>), and
217       bottom-to-top (<literal>HB_DIRECTION_BTT</literal>).  For the
218       script property, HarfBuzz uses identifiers based on the
226       the necessary script and language tag types.
247       example, when using a font that provides script-specific
273       property designates control characters and other non-printing
275       HarfBuzz replaces them in the output buffer with zero-width
286       flag tells HarfBuzz not to insert the dotted-circle glyph
294   <section id="customizing-unicode-functions">
300       <literal>Script</literal> (sc) properties) that is useful
316       might prefer to use those instead of the built-in
342       You can retrieve the Unicode-functions configuration for
368 	  the Mirroring Glyph code point (for bi-directional
375 	  Script (sc) property of a code point.