OT features' hierarchy.

Eimantas Paškonis
Posts: 91
Sure, both OT code and hierarchy is simple if font is lightweight, but it gets confusing real fast when there's locl, case, calt, liga, dlig, smcp, c2sc, swsh, frac, ss01-07, sinf/sups/subs, numr/dnom, lnum/onum, pnum/tnum etc. to work with.
I know that everyone's have different methods and it varies from font to font, but what's your usual strategy? Do you put most common features at the top or vice versa? The ones that affect the most glyphs?
I know that everyone's have different methods and it varies from font to font, but what's your usual strategy? Do you put most common features at the top or vice versa? The ones that affect the most glyphs?
Tagged:
0
Comments
-
I mainly look out for possible interactions when multiple features are applied. For instance, I put smcp before liga. If I didn't, I'd have to figure out a way to transform fi, fl, ffi, ffl, etc. into small caps in the smcp feature. Similarly, I place frac and sinf/sups/subs before figure style transformations.2
Categories
- All Categories
- 43 Introductions
- 3.8K Typeface Design
- 815 Font Technology
- 1.1K Technique and Theory
- 633 Type Business
- 450 Type Design Critiques
- 549 Type Design Software
- 30 Punchcutting
- 138 Lettering and Calligraphy
- 85 Technique and Theory
- 53 Lettering Critiques
- 499 Typography
- 308 History of Typography
- 117 Education
- 74 Resources
- 513 Announcements
- 82 Events
- 107 Job Postings
- 156 Type Releases
- 167 Miscellaneous News
- 271 About TypeDrawers
- 53 TypeDrawers Announcements
- 117 Suggestions and Bug Reports