The net result is that the output sequence of glyphs may map back to a single Unicode, or multiple Unicodes, or none at all.
In some cases, specifically with Hindi and other Indic languages, the output glyph sequence may even be in a different order than the logical Unicode input sequence. It can even specify contexts under which the conversion will occur (for example, it could say something like "convert 'A' to 'B' but only when the 'A' is preceded by a 'C'", so CA -> CB but DA -> DA).
#WHY CANT I CREATE A GLYPH ACCOUNT SERIES#
Thus with this alone, you cannot reliably reverse-map a glyph to a single Unicode.īut it gets even more difficult: the GSUB may specify numerous rules and may convert one input glyph to many output glyphs, or a series of input glyphs into one output glyph. Also, many glyphs in the font may not even be mapped in the cmap. This is a commonly-used scheme in many fonts. The cmap may specify multiple Unicodes mapping to a single glyph (multi-mapping). The cmap maps Unicode values to font-specific glyphs. The two of most interest are the cmap and the GSUB. This is done using a number of tables in the font data.
This is the result of something known as complex script shaping, which translates a sequence of input Unicodes into a sequence of output glyphs. This is noted in the documentation for GetGlyphIndices: (v=vs.85).aspxĢ) There is no way to reliably do what you want to do for all cases.
1) For all but very simple cases, you should use Uniscribe functions (not GetGlyphIndices) for converting a string (sequence of Unicodes) into glyphs.
0 kommentar(er)
