3.2.5.1.1.1.13 Processing of GlyphIndex

The structure and fields of the GlyphIndex Primary Drawing Order are specified in section 2.2.2.2.1.2.5, and the techniques described in section 3.2.5.1.1.1 demonstrate how to decode and process the order.

If support for glyph caching was not specified in the Glyph Cache Capability Set (see [MS-RDPBCGR] section 2.2.7.1.8), the client SHOULD ignore this order as it requires the existence of the glyph caches (see section 3.1.1.1.2).

All of the glyphs associated with the glyph cache indices specified in the order MUST have been received by the client in a prior Revision 1 or 2 Cache Glyph Secondary Drawing Order (see sections 3.2.5.1.2.1.4 and 3.2.5.1.2.1.5), or a FastGlyph Primary Drawing Order (see section 3.2.5.1.1.1.15). If a fragment cache index is specified in a USE clause, that fragment MUST have been cached while processing an ADD clause in a prior GlyphIndex or FastIndex Order.

If a cached brush is specified in this order, that brush MUST have been received by the client in a prior Cache Brush Secondary Drawing Order (see section 3.2.5.1.2.1.6). If this is not the case, the client SHOULD ignore this order. Furthermore, if support for brush caching was not specified in the Brush Capability Set (see [MS-RDPBCGR] section 2.2.7.1.7), and a cached brush is included in the GlyphIndex order, the client SHOULD ignore this order.