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
- 568 Type Design Software
- 1.1K Type Design Technique & Theory
- 662 Type Business
- 868 Font Technology
- 29 Punchcutting
- 526 Typography
- 121 Type Education
- 326 Type History
- 79 Type Resources
- 112 Lettering and Calligraphy
- 33 Lettering Critiques
- 79 Lettering Technique & Theory
- 564 Announcements
- 95 Events
- 116 Job Postings
- 170 Type Releases
- 182 Miscellaneous News
- 278 About TypeDrawers
- 55 TypeDrawers Announcements
- 121 Suggestions and Bug Reports