OTS forces data chunks in a CMAP format 14 subtable being in order?
Options
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.8K Typeface Design
- 476 Type Design Critiques
- 555 Type Design Software
- 1.1K Type Design Technique & Theory
- 640 Type Business
- 831 Font Technology
- 29 Punchcutting
- 508 Typography
- 120 Type Education
- 313 Type History
- 75 Type Resources
- 109 Lettering and Calligraphy
- 30 Lettering Critiques
- 79 Lettering Technique & Theory
- 533 Announcements
- 86 Events
- 110 Job Postings
- 167 Type Releases
- 169 Miscellaneous News
- 274 About TypeDrawers
- 53 TypeDrawers Announcements
- 119 Suggestions and Bug Reports