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.
varSelector
s, 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
- 43 Introductions
- 3.7K Typeface Design
- 803 Font Technology
- 1K Technique and Theory
- 620 Type Business
- 444 Type Design Critiques
- 542 Type Design Software
- 30 Punchcutting
- 136 Lettering and Calligraphy
- 83 Technique and Theory
- 53 Lettering Critiques
- 484 Typography
- 302 History of Typography
- 114 Education
- 68 Resources
- 499 Announcements
- 80 Events
- 105 Job Postings
- 148 Type Releases
- 165 Miscellaneous News
- 270 About TypeDrawers
- 53 TypeDrawers Announcements
- 116 Suggestions and Bug Reports