[MPEG-OTSPEC] B64K: sbix 'dupe' tag

[Ned Holbrook]

Or stick with the favored convention for SFNT tables and call it 'DUPE' ?

> On Feb 9, 2024, at 12:03 PM, Peter Constable via mpeg-otspec <mpeg-otspec at lists.aau.at> wrote:
> 
> Within the sbix glyph data, graphicType = ‘dupe’ indicates that the data that follows is a 16-bit glyph ID. (This type means that the bitmap data of the referenced glyph is used for the current glyph ID.) Since the docs currently assume that sbix data can be used for >64K glyphs, then I think a new tag ‘dp24’ (or ‘dp32’?) should be defined.
>  
> In 5.5.7.3, the existing paragraph that begins “The special graphicType of ‘dupe’…” could be replaced with the following:
> The special graphicType value 'dupe' and 'dp24' indicate that the data field contains a two- or three-byte, big-endian glyph ID. With either type, the bitmap data for the indicated glyph shall be used for the current glyph. The type 'dp24' shall only be used in fonts that have a MAXP table and use 24-bit glyph IDs. If an application supports the ‘sbix’ table but does not support 24-bit glyph IDs, glyph data with graphicType = 'dp24' may be ignored.
>  
>  
>  
> Peter
> _______________________________________________
> mpeg-otspec mailing list
> mpeg-otspec at lists.aau.at <mailto:mpeg-otspec at lists.aau.at>
> https://lists.aau.at/mailman/listinfo/mpeg-otspec

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20240209/5b84156b/attachment-0001.htm>