Does one kern a duplex font?
Options

Raphaël Ronot
Posts: 33
Hi, this question hit me the other day. I was wondering if some of you had faced this problem before.
Making a regular and bold weight fit into the exact same width is already difficult, but giving them the same kerning values for every pair seems impossible, right? Take a simple `To` for example. The bolder weight won't allow the `o` to "slide" under the horizontal bar of the `T`.
So what do we do? Should we find an in-between "one size fits all" kerning system that works decently for both masters?
Thanks in advance
Making a regular and bold weight fit into the exact same width is already difficult, but giving them the same kerning values for every pair seems impossible, right? Take a simple `To` for example. The bolder weight won't allow the `o` to "slide" under the horizontal bar of the `T`.
So what do we do? Should we find an in-between "one size fits all" kerning system that works decently for both masters?
Thanks in advance

0
Comments
-
Identical kerning should be shared among the duplex/multiplex/uniwidth weights. Martin Majoor’s Comma Base and Nick Sherman’s HEX Franklin have identical kerning across their entire weight range, respectively. Matthew Butterick’s Concourse has identical kerning shared within weights 2 (Thin), 3 (Book), 4 (Medium), and 6 (Semibold), furthermore its roman and italic are duplexed and also share identical kerning; though the bolder weights of Concourse break free from this constraint.
6
Categories
- All Categories
- 46 Introductions
- 3.8K Typeface Design
- 476 Type Design Critiques
- 556 Type Design Software
- 1.1K Type Design Technique & Theory
- 640 Type Business
- 831 Font Technology
- 29 Punchcutting
- 508 Typography
- 120 Type Education
- 313 Type History
- 75 Type Resources
- 110 Lettering and Calligraphy
- 31 Lettering Critiques
- 79 Lettering Technique & Theory
- 533 Announcements
- 86 Events
- 110 Job Postings
- 167 Type Releases
- 169 Miscellaneous News
- 274 About TypeDrawers
- 53 TypeDrawers Announcements
- 119 Suggestions and Bug Reports