Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 2.6K All Categories
- 1 Introductions
- 2.1K Typeface Design
- 240 Font Technology
- 721 Technique and Theory
- 276 Type Business
- 264 Type Design Critiques
- 386 Type Design Software
- 27 Punchcutting
- 54 Lettering and Calligraphy
- 34 Technique and Theory
- 20 Lettering Critiques
- 204 Typography
- 141 History of Typography
- 63 Education
- 302 Announcements
- 54 Events
- 55 Job Postings
- 89 Type Releases
- 103 Miscellaneous News
- 163 About TypeDrawers
- 40 TypeDrawers Announcements
- 72 Suggestions and Bug Reports
OTS forces data chunks in a CMAP format 14 subtable being in order?
Belleve Invis
Posts: 232
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