HarfBuzz-0.0 ▶ HarfBuzz ▶ buffer_serialize_glyphsSince 0.9.7

Serializes buffer into a textual representation of its glyph content, useful for showing the contents of the buffer, for example during debugging. There are currently two supported serialization formats:

text

A human-readable, plain text format. The serialized glyphs will look something like:

[uni0651=0@518,0+0|uni0628=0+1897]
Copy

• The serialized glyphs are delimited with [ and ].
• Glyphs are separated with |
• Each glyph starts with glyph name, or glyph index if #HB_BUFFER_SERIALIZE_FLAG_NO_GLYPH_NAMES flag is set. Then,
  • If #HB_BUFFER_SERIALIZE_FLAG_NO_CLUSTERS is not set, = then HarfBuzz.glyph_info_t.cluster.
  • If #HB_BUFFER_SERIALIZE_FLAG_NO_POSITIONS is not set, the HarfBuzz.glyph_position_t in the format:
    • If both HarfBuzz.glyph_position_t.x_offset and HarfBuzz.glyph_position_t.y_offset are not 0, ``x_offset,y_offset. Then,
    • +x_advance, then ,y_advance if HarfBuzz.glyph_position_t.y_advance is not 0. Then,
  • If #HB_BUFFER_SERIALIZE_FLAG_GLYPH_EXTENTS is set, the HarfBuzz.glyph_extents_t in the format <x_bearing,y_bearing,width,height>

json

A machine-readable, structured format. The serialized glyphs will look something like:

[{"g":"uni0651","cl":0,"dx":518,"dy":0,"ax":0,"ay":0},
{"g":"uni0628","cl":0,"dx":0,"dy":0,"ax":1897,"ay":0}]
Copy

Each glyph is a JSON object, with the following properties:

• g: the glyph name or glyph index if #HB_BUFFER_SERIALIZE_FLAG_NO_GLYPH_NAMES flag is set.
• cl: HarfBuzz.glyph_info_t.cluster if #HB_BUFFER_SERIALIZE_FLAG_NO_CLUSTERS is not set.
• dx,dy,ax,ay: HarfBuzz.glyph_position_t.x_offset, HarfBuzz.glyph_position_t.y_offset, HarfBuzz.glyph_position_t.x_advance and HarfBuzz.glyph_position_t.y_advance respectively, if #HB_BUFFER_SERIALIZE_FLAG_NO_POSITIONS is not set.
• xb,yb,w,h: HarfBuzz.glyph_extents_t.x_bearing, HarfBuzz.glyph_extents_t.y_bearing, HarfBuzz.glyph_extents_t.width and HarfBuzz.glyph_extents_t.height respectively if #HB_BUFFER_SERIALIZE_FLAG_GLYPH_EXTENTS is set.