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
- 46 Introductions
- 3.9K Typeface Design
- 485 Type Design Critiques
- 560 Type Design Software
- 1.1K Type Design Technique & Theory
- 651 Type Business
- 848 Font Technology
- 29 Punchcutting
- 519 Typography
- 119 Type Education
- 323 Type History
- 77 Type Resources
- 110 Lettering and Calligraphy
- 31 Lettering Critiques
- 79 Lettering Technique & Theory
- 548 Announcements
- 90 Events
- 114 Job Postings
- 170 Type Releases
- 173 Miscellaneous News
- 275 About TypeDrawers
- 53 TypeDrawers Announcements
- 120 Suggestions and Bug Reports