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
- 47 Introductions
- 4K Typeface Design
- 505 Type Design Critiques
- 597 Type Design Software
- 1.1K Type Design Technique & Theory
- 678 Type Business
- 911 Font Technology
- 29 Punchcutting
- 544 Typography
- 129 Type Education
- 333 Type History
- 82 Type Resources
- 114 Lettering and Calligraphy
- 33 Lettering Critiques
- 81 Lettering Technique & Theory
- 588 Announcements
- 102 Events
- 118 Job Postings
- 179 Type Releases
- 188 Miscellaneous News
- 270 About TypeDrawers
- 54 TypeDrawers Announcements
- 114 Suggestions and Bug Reports