/** * hb_glyph_info_t: * @codepoint: either a Unicode code point (before shaping) or a glyph index * (after shaping). * @cluster: the index of the character in the original text that corresponds * to this #hb_glyph_info_t, or whatever the client passes to * hb_buffer_add(). More than one #hb_glyph_info_t can have the same * @cluster value, if they resulted from the same character (e.g. one * to many glyph substitution), and when more than one character gets * merged in the same glyph (e.g. many to one glyph substitution) the * #hb_glyph_info_t will have the smallest cluster value of them. * By default some characters are merged into the same cluster * (e.g. combining marks have the same cluster as their bases) * even if they are separate glyphs, hb_buffer_set_cluster_level() * allow selecting more fine-grained cluster handling. * * The #hb_glyph_info_t is the structure that holds information about the * glyphs and their relation to input text.
*/ typedefstruct hb_glyph_info_t {
hb_codepoint_t codepoint; /*< private >*/
hb_mask_t mask; /*< public >*/
uint32_t cluster;
/** * hb_glyph_flags_t: * @HB_GLYPH_FLAG_UNSAFE_TO_BREAK: Indicates that if input text is broken at the * beginning of the cluster this glyph is part of, * then both sides need to be re-shaped, as the * result might be different. * On the flip side, it means that when this * flag is not present, then it is safe to break * the glyph-run at the beginning of this * cluster, and the two sides will represent the * exact same result one would get if breaking * input text at the beginning of this cluster * and shaping the two sides separately. * This can be used to optimize paragraph * layout, by avoiding re-shaping of each line * after line-breaking. * @HB_GLYPH_FLAG_UNSAFE_TO_CONCAT: Indicates that if input text is changed on one * side of the beginning of the cluster this glyph * is part of, then the shaping results for the * other side might change. * Note that the absence of this flag will NOT by * itself mean that it IS safe to concat text. * Only two pieces of text both of which clear of * this flag can be concatenated safely. * This can be used to optimize paragraph * layout, by avoiding re-shaping of each line * after line-breaking, by limiting the * reshaping to a small piece around the * breaking position only, even if the breaking * position carries the * #HB_GLYPH_FLAG_UNSAFE_TO_BREAK or when * hyphenation or other text transformation * happens at line-break position, in the following * way: * 1. Iterate back from the line-break position * until the first cluster start position that is * NOT unsafe-to-concat, 2. shape the segment from * there till the end of line, 3. check whether the * resulting glyph-run also is clear of the * unsafe-to-concat at its start-of-text position; * if it is, just splice it into place and the line * is shaped; If not, move on to a position further * back that is clear of unsafe-to-concat and retry * from there, and repeat. * At the start of next line a similar algorithm can * be implemented. That is: 1. Iterate forward from * the line-break position until the first cluster * start position that is NOT unsafe-to-concat, 2. * shape the segment from beginning of the line to * that position, 3. check whether the resulting * glyph-run also is clear of the unsafe-to-concat * at its end-of-text position; if it is, just splice * it into place and the beginning is shaped; If not, * move on to a position further forward that is clear * of unsafe-to-concat and retry up to there, and repeat. * A slight complication will arise in the * implementation of the algorithm above, * because while our buffer API has a way to * return flags for position corresponding to * start-of-text, there is currently no position * corresponding to end-of-text. This limitation * can be alleviated by shaping more text than needed * and looking for unsafe-to-concat flag within text * clusters. * The #HB_GLYPH_FLAG_UNSAFE_TO_BREAK flag will * always imply this flag. * To use this flag, you must enable the buffer flag * @HB_BUFFER_FLAG_PRODUCE_UNSAFE_TO_CONCAT during * shaping, otherwise the buffer flag will not be * reliably produced. * Since: 4.0.0 * @HB_GLYPH_FLAG_SAFE_TO_INSERT_TATWEEL: In scripts that use elongation (Arabic, Mongolian, Syriac, etc.), this flag signifies that it is safe to insert a U+0640 TATWEEL character before this cluster for elongation. This flag does not determine the script-specific elongation places, but only when it is safe to do the elongation without interrupting text shaping. Since: 5.1.0 * @HB_GLYPH_FLAG_DEFINED: All the currently defined flags. * * Flags for #hb_glyph_info_t. * * Since: 1.5.0
*/ typedefenum { /*< flags >*/
HB_GLYPH_FLAG_UNSAFE_TO_BREAK = 0x00000001,
HB_GLYPH_FLAG_UNSAFE_TO_CONCAT = 0x00000002,
HB_GLYPH_FLAG_SAFE_TO_INSERT_TATWEEL = 0x00000004,
HB_GLYPH_FLAG_DEFINED = 0x00000007 /* OR of all defined flags */
} hb_glyph_flags_t;
/** * hb_glyph_position_t: * @x_advance: how much the line advances after drawing this glyph when setting * text in horizontal direction. * @y_advance: how much the line advances after drawing this glyph when setting * text in vertical direction. * @x_offset: how much the glyph moves on the X-axis before drawing it, this * should not affect how much the line advances. * @y_offset: how much the glyph moves on the Y-axis before drawing it, this * should not affect how much the line advances. * * The #hb_glyph_position_t is the structure that holds the positions of the * glyph in both horizontal and vertical directions. All positions in * #hb_glyph_position_t are relative to the current point. *
*/ typedefstruct hb_glyph_position_t {
hb_position_t x_advance;
hb_position_t y_advance;
hb_position_t x_offset;
hb_position_t y_offset;
/** * hb_segment_properties_t: * @direction: the #hb_direction_t of the buffer, see hb_buffer_set_direction(). * @script: the #hb_script_t of the buffer, see hb_buffer_set_script(). * @language: the #hb_language_t of the buffer, see hb_buffer_set_language(). * * The structure that holds various text properties of an #hb_buffer_t. Can be * set and retrieved using hb_buffer_set_segment_properties() and * hb_buffer_get_segment_properties(), respectively.
*/ typedefstruct hb_segment_properties_t {
hb_direction_t direction;
hb_script_t script;
hb_language_t language; /*< private >*/ void *reserved1; void *reserved2;
} hb_segment_properties_t;
/** * HB_SEGMENT_PROPERTIES_DEFAULT: * * The default #hb_segment_properties_t of of freshly created #hb_buffer_t.
*/ #define HB_SEGMENT_PROPERTIES_DEFAULT {HB_DIRECTION_INVALID, \
HB_SCRIPT_INVALID, \
HB_LANGUAGE_INVALID, \
(void *) 0, \
(void *) 0}
/** * hb_buffer_t: * * The main structure holding the input text and its properties before shaping, * and output glyphs and their information after shaping.
*/
/** * hb_buffer_flags_t: * @HB_BUFFER_FLAG_DEFAULT: the default buffer flag. * @HB_BUFFER_FLAG_BOT: flag indicating that special handling of the beginning * of text paragraph can be applied to this buffer. Should usually * be set, unless you are passing to the buffer only part * of the text without the full context. * @HB_BUFFER_FLAG_EOT: flag indicating that special handling of the end of text * paragraph can be applied to this buffer, similar to * @HB_BUFFER_FLAG_BOT. * @HB_BUFFER_FLAG_PRESERVE_DEFAULT_IGNORABLES: * flag indication that character with Default_Ignorable * Unicode property should use the corresponding glyph * from the font, instead of hiding them (done by * replacing them with the space glyph and zeroing the * advance width.) This flag takes precedence over * @HB_BUFFER_FLAG_REMOVE_DEFAULT_IGNORABLES. * @HB_BUFFER_FLAG_REMOVE_DEFAULT_IGNORABLES: * flag indication that character with Default_Ignorable * Unicode property should be removed from glyph string * instead of hiding them (done by replacing them with the * space glyph and zeroing the advance width.) * @HB_BUFFER_FLAG_PRESERVE_DEFAULT_IGNORABLES takes * precedence over this flag. Since: 1.8.0 * @HB_BUFFER_FLAG_DO_NOT_INSERT_DOTTED_CIRCLE: * flag indicating that a dotted circle should * not be inserted in the rendering of incorrect * character sequences (such at <0905 093E>). Since: 2.4.0 * @HB_BUFFER_FLAG_VERIFY: * flag indicating that the hb_shape() call and its variants * should perform various verification processes on the results * of the shaping operation on the buffer. If the verification * fails, then either a buffer message is sent, if a message * handler is installed on the buffer, or a message is written * to standard error. In either case, the shaping result might * be modified to show the failed output. Since: 3.4.0 * @HB_BUFFER_FLAG_PRODUCE_UNSAFE_TO_CONCAT: * flag indicating that the @HB_GLYPH_FLAG_UNSAFE_TO_CONCAT * glyph-flag should be produced by the shaper. By default * it will not be produced since it incurs a cost. Since: 4.0.0 * @HB_BUFFER_FLAG_PRODUCE_SAFE_TO_INSERT_TATWEEL: * flag indicating that the @HB_GLYPH_FLAG_SAFE_TO_INSERT_TATWEEL * glyph-flag should be produced by the shaper. By default * it will not be produced. Since: 5.1.0 * @HB_BUFFER_FLAG_DEFINED: All currently defined flags: Since: 4.4.0 * * Flags for #hb_buffer_t. * * Since: 0.9.20
*/ typedefenum { /*< flags >*/
HB_BUFFER_FLAG_DEFAULT = 0x00000000u,
HB_BUFFER_FLAG_BOT = 0x00000001u, /* Beginning-of-text */
HB_BUFFER_FLAG_EOT = 0x00000002u, /* End-of-text */
HB_BUFFER_FLAG_PRESERVE_DEFAULT_IGNORABLES = 0x00000004u,
HB_BUFFER_FLAG_REMOVE_DEFAULT_IGNORABLES = 0x00000008u,
HB_BUFFER_FLAG_DO_NOT_INSERT_DOTTED_CIRCLE = 0x00000010u,
HB_BUFFER_FLAG_VERIFY = 0x00000020u,
HB_BUFFER_FLAG_PRODUCE_UNSAFE_TO_CONCAT = 0x00000040u,
HB_BUFFER_FLAG_PRODUCE_SAFE_TO_INSERT_TATWEEL = 0x00000080u,
/** * hb_buffer_cluster_level_t: * @HB_BUFFER_CLUSTER_LEVEL_MONOTONE_GRAPHEMES: Return cluster values grouped by graphemes into * monotone order. * @HB_BUFFER_CLUSTER_LEVEL_MONOTONE_CHARACTERS: Return cluster values grouped into monotone order. * @HB_BUFFER_CLUSTER_LEVEL_CHARACTERS: Don't group cluster values. * @HB_BUFFER_CLUSTER_LEVEL_DEFAULT: Default cluster level, * equal to @HB_BUFFER_CLUSTER_LEVEL_MONOTONE_GRAPHEMES. * * Data type for holding HarfBuzz's clustering behavior options. The cluster level * dictates one aspect of how HarfBuzz will treat non-base characters * during shaping. * * In @HB_BUFFER_CLUSTER_LEVEL_MONOTONE_GRAPHEMES, non-base * characters are merged into the cluster of the base character that precedes them. * * In @HB_BUFFER_CLUSTER_LEVEL_MONOTONE_CHARACTERS, non-base characters are initially * assigned their own cluster values, which are not merged into preceding base * clusters. This allows HarfBuzz to perform additional operations like reorder * sequences of adjacent marks. * * @HB_BUFFER_CLUSTER_LEVEL_MONOTONE_GRAPHEMES is the default, because it maintains * backward compatibility with older versions of HarfBuzz. New client programs that * do not need to maintain such backward compatibility are recommended to use * @HB_BUFFER_CLUSTER_LEVEL_MONOTONE_CHARACTERS instead of the default. * * Since: 0.9.42
*/ typedefenum {
HB_BUFFER_CLUSTER_LEVEL_MONOTONE_GRAPHEMES = 0,
HB_BUFFER_CLUSTER_LEVEL_MONOTONE_CHARACTERS = 1,
HB_BUFFER_CLUSTER_LEVEL_CHARACTERS = 2,
HB_BUFFER_CLUSTER_LEVEL_DEFAULT = HB_BUFFER_CLUSTER_LEVEL_MONOTONE_GRAPHEMES
} hb_buffer_cluster_level_t;
/** * HB_BUFFER_REPLACEMENT_CODEPOINT_DEFAULT: * * The default code point for replacing invalid characters in a given encoding. * Set to U+FFFD REPLACEMENT CHARACTER. * * Since: 0.9.31
*/ #define HB_BUFFER_REPLACEMENT_CODEPOINT_DEFAULT 0xFFFDu
/** * hb_buffer_diff_flags_t: * @HB_BUFFER_DIFF_FLAG_EQUAL: equal buffers. * @HB_BUFFER_DIFF_FLAG_CONTENT_TYPE_MISMATCH: buffers with different * #hb_buffer_content_type_t. * @HB_BUFFER_DIFF_FLAG_LENGTH_MISMATCH: buffers with differing length. * @HB_BUFFER_DIFF_FLAG_NOTDEF_PRESENT: `.notdef` glyph is present in the * reference buffer. * @HB_BUFFER_DIFF_FLAG_DOTTED_CIRCLE_PRESENT: dotted circle glyph is present * in the reference buffer. * @HB_BUFFER_DIFF_FLAG_CODEPOINT_MISMATCH: difference in #hb_glyph_info_t.codepoint * @HB_BUFFER_DIFF_FLAG_CLUSTER_MISMATCH: difference in #hb_glyph_info_t.cluster * @HB_BUFFER_DIFF_FLAG_GLYPH_FLAGS_MISMATCH: difference in #hb_glyph_flags_t. * @HB_BUFFER_DIFF_FLAG_POSITION_MISMATCH: difference in #hb_glyph_position_t. * * Flags from comparing two #hb_buffer_t's. * * Buffer with different #hb_buffer_content_type_t cannot be meaningfully * compared in any further detail. * * For buffers with differing length, the per-glyph comparison is not * attempted, though we do still scan reference buffer for dotted circle and * `.notdef` glyphs. * * If the buffers have the same length, we compare them glyph-by-glyph and * report which aspect(s) of the glyph info/position are different. * * Since: 1.5.0
*/ typedefenum { /*< flags >*/
HB_BUFFER_DIFF_FLAG_EQUAL = 0x0000,
/* Buffers with different content_type cannot be meaningfully compared
* in any further detail. */
HB_BUFFER_DIFF_FLAG_CONTENT_TYPE_MISMATCH = 0x0001,
/* For buffers with differing length, the per-glyph comparison is not * attempted, though we do still scan reference for dottedcircle / .notdef
* glyphs. */
HB_BUFFER_DIFF_FLAG_LENGTH_MISMATCH = 0x0002,
/* We want to know if dottedcircle / .notdef glyphs are present in the * reference, as we may not care so much about other differences in this
* case. */
HB_BUFFER_DIFF_FLAG_NOTDEF_PRESENT = 0x0004,
HB_BUFFER_DIFF_FLAG_DOTTED_CIRCLE_PRESENT = 0x0008,
/* If the buffers have the same length, we compare them glyph-by-glyph
* and report which aspect(s) of the glyph info/position are different. */
HB_BUFFER_DIFF_FLAG_CODEPOINT_MISMATCH = 0x0010,
HB_BUFFER_DIFF_FLAG_CLUSTER_MISMATCH = 0x0020,
HB_BUFFER_DIFF_FLAG_GLYPH_FLAGS_MISMATCH = 0x0040,
HB_BUFFER_DIFF_FLAG_POSITION_MISMATCH = 0x0080
} hb_buffer_diff_flags_t;
/* Compare the contents of two buffers, report types of differences. */
HB_EXTERN hb_buffer_diff_flags_t
hb_buffer_diff (hb_buffer_t *buffer,
hb_buffer_t *reference,
hb_codepoint_t dottedcircle_glyph, unsignedint position_fuzz);
/* * Tracing.
*/
/** * hb_buffer_message_func_t: * @buffer: An #hb_buffer_t to work upon * @font: The #hb_font_t the @buffer is shaped with * @message: `NULL`-terminated message passed to the function * @user_data: User data pointer passed by the caller * * A callback method for #hb_buffer_t. The method gets called with the * #hb_buffer_t it was set on, the #hb_font_t the buffer is shaped with and a * message describing what step of the shaping process will be performed. * Returning `false` from this method will skip this shaping step and move to * the next one. * * Return value: `true` to perform the shaping step, `false` to skip it. * * Since: 1.1.3
*/ typedef hb_bool_t (*hb_buffer_message_func_t) (hb_buffer_t *buffer,
hb_font_t *font, constchar *message, void *user_data);
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung ist noch experimentell.