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
- 482 Type Design Critiques
- 560 Type Design Software
- 1.1K Type Design Technique & Theory
- 649 Type Business
- 844 Font Technology
- 29 Punchcutting
- 517 Typography
- 119 Type Education
- 321 Type History
- 77 Type Resources
- 110 Lettering and Calligraphy
- 31 Lettering Critiques
- 79 Lettering Technique & Theory
- 544 Announcements
- 88 Events
- 112 Job Postings
- 170 Type Releases
- 173 Miscellaneous News
- 275 About TypeDrawers
- 53 TypeDrawers Announcements
- 120 Suggestions and Bug Reports