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
- 47 Introductions
- 4K Typeface Design
- 505 Type Design Critiques
- 597 Type Design Software
- 1.1K Type Design Technique & Theory
- 681 Type Business
- 912 Font Technology
- 29 Punchcutting
- 548 Typography
- 132 Type Education
- 334 Type History
- 82 Type Resources
- 114 Lettering and Calligraphy
- 33 Lettering Critiques
- 81 Lettering Technique & Theory
- 592 Announcements
- 102 Events
- 119 Job Postings
- 181 Type Releases
- 189 Miscellaneous News
- 270 About TypeDrawers
- 54 TypeDrawers Announcements
- 114 Suggestions and Bug Reports
