OTS forces data chunks in a CMAP format 14 subtable being in order?
Belleve Invis
Posts: 269
As read the source it looks like that, data chunks of Default UVS Tables and Non-Default UVS Tables must be ordered the same as
If the data chunks are not ordered, OTS would report an error, triggered by line 531 in cmap.cc (https://github.com/khaledhosny/ots/blob/master/src/cmap.cc#L531). The code forces that, the UVS data chunk referenced by the last varSelector must end at the end of the entire CMAP subtable.
varSelectors, but I did not see any requirements in the Spec restricting the order of data chunks.If the data chunks are not ordered, OTS would report an error, triggered by line 531 in cmap.cc (https://github.com/khaledhosny/ots/blob/master/src/cmap.cc#L531). The code forces that, the UVS data chunk referenced by the last varSelector must end at the end of the entire CMAP subtable.
0
Categories
- All Categories
- 46 Introductions
- 3.9K Typeface Design
- 489 Type Design Critiques
- 572 Type Design Software
- 1.1K Type Design Technique & Theory
- 662 Type Business
- 875 Font Technology
- 29 Punchcutting
- 529 Typography
- 121 Type Education
- 328 Type History
- 80 Type Resources
- 111 Lettering and Calligraphy
- 32 Lettering Critiques
- 79 Lettering Technique & Theory
- 561 Announcements
- 96 Events
- 116 Job Postings
- 169 Type Releases
- 179 Miscellaneous News
- 269 About TypeDrawers
- 53 TypeDrawers Announcements
- 114 Suggestions and Bug Reports