HomeSort by relevance Sort by last modified time
    Searched defs:gpos (Results 1 - 4 of 4) sorted by null

  /external/freetype/src/otvalid/
otvmod.c 79 FT_Byte* volatile gpos; local
89 base = gdef = gpos = gsub = jstf = math = NULL;
122 error = otv_load_table( face, TTAG_GPOS, &gpos, &len_gpos );
160 if ( gpos )
162 ft_validator_init( &valid, gpos, gpos + len_gpos, FT_VALIDATE_DEFAULT );
164 otv_GPOS_validate( gpos, num_glyphs, &valid );
184 otv_GDEF_validate( gdef, gsub, gpos, num_glyphs, &valid );
194 otv_JSTF_validate( jstf, gsub, gpos, num_glyphs, &valid );
212 *ot_gpos = (FT_Bytes)gpos;
    [all...]
  /external/freetype/src/autofit/
afshaper.c 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 t
552 hb_glyph_position_t* gpos; local
    [all...]
  /external/harfbuzz_ng/src/
hb-ot-layout.cc 41 #include "hb-ot-layout-gpos-table.hh"
125 face->table.GPOS->table.get_length ())
287 * GSUB/GPOS
296 * GSUB/GPOS tables. Some have GSUB with zero scripts, those are ignored by
316 OT::GPOS::is_blacklisted (hb_blob_t *blob HB_UNUSED,
328 case HB_OT_TAG_GPOS: return *face->table.GPOS->table;
899 const OT::PosLookup& l = face->table.GPOS->table->get_lookup (lookup_index);
1134 const OT::GPOS &gpos = *face->table.GPOS->table; local
    [all...]
  /external/wpa_supplicant_8/src/drivers/
driver_wext.c 1334 char *genie, *gpos, *gend; local
    [all...]

Completed in 286 milliseconds