Lines Matching refs:gpos
109 hb_set_t* gpos_lookups = NULL; /* GPOS lookups for a given script */
110 hb_set_t* gpos_glyphs = NULL; /* glyphs covered by GPOS lookups */
209 FT_TRACE4(( "GPOS lookups (style `%s'):\n"
233 /* get input coverage of GPOS feature */
310 * GPOS tables). The code for blue zones computation actually uses a
316 * feature covers the glyph in both the GSUB and the GPOS tables. This
324 * (b) a feature's GPOS data really moves the glyph vertically.
333 * directly get the necessary information from the GPOS table. A
334 * possible solution might be to directly parse the GPOS table to find
339 * Complex scripts like Devanagari have mandatory GPOS features to
349 FT_TRACE4(( " glyphs without GPOS data (`*' means already assigned)" ));
366 /* internal to GSUB or GPOS, which is fully valid */
552 hb_glyph_position_t* gpos;
559 gpos = hb_buffer_get_glyph_positions( buf, &gcount );
565 *advance = gpos[idx].x_advance;
567 *y_offset = gpos[idx].y_offset;
