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.8K Typeface Design
- 475 Type Design Critiques
- 555 Type Design Software
- 1.1K Type Design Technique & Theory
- 640 Type Business
- 830 Font Technology
- 29 Punchcutting
- 507 Typography
- 120 Type Education
- 313 Type History
- 74 Type Resources
- 109 Lettering and Calligraphy
- 30 Lettering Critiques
- 79 Lettering Technique & Theory
- 529 Announcements
- 84 Events
- 110 Job Postings
- 165 Type Releases
- 169 Miscellaneous News
- 274 About TypeDrawers
- 54 TypeDrawers Announcements
- 118 Suggestions and Bug Reports