Naming the extreme styles on a contrast axis?
Johannes Neumeier
Posts: 381
I'm working on a (variable) font that has masters with stroke contrast ranging from clearly modulated to monolinear. While I am mostly fine with the contrast axis name, I wonder what name you would find descriptive of those extremes when exported as separate style families?
So far I am working with "normal" and "linear", but especially the "normal" rubs me totally wrong. While for this design it is true that the "natural" state is the master with contrast I don't want to communicate that one is the default or favorable compared to the other. I am not sure how descriptive the "linear" is to graphic designers, either, but my hunch is that many don't instinctively understand what contrast refers to in the context of a typeface family range.
Any references or idea?
0
Comments
-
High and low?1
-
Let me clarify. So for the OTVar the axis is what the user accesses, say in a layout application, but when also exporting the two extremes as separate styles I would end up with fonts in the menu like:AcmeFont Normal RegularAcmeFont Normal Regular ObliqueAcmeFont Normal BoldAcmeFont Normal Bold ObliqueAcmeFont Linear RegularAcmeFont Linear Regular ObliqueAcmeFont Linear BoldAcmeFont Linear Bold Oblique
So in that context neither "Normal" works, nor does "High" and "Low", although it does describe the contrast.
0 -
Large, as in, intended for large sizes (and large amount of contrast)
Small, as in, useful in smaller sizes (and small amount of contrast)?
I assume you don't want to use display and text?
Edit: I see that's not what you mean...0 -
Normal plus Regular may cause a problem. Both those terms mean the basic (default) text weight of the family so they do not differentiate from each other1
-
Anything wrong with 'modulated' and 'linear'?1
-
If they’re optical sizes use small, medium, large, huge, etc.. If they’re just contrast grades use coarse, medium, fine, hairline, etc..0
-
For 4.5 point and below, call it "micetype".
0 -
Font1 and Font2? ;-)
I'm not entirely kidding: contrast is a parameter that affects the character of a typeface more than most others. It could be fun and might seem convenient to bundle contrasty and monoline versions, but to me they become essentially different typefaces, undermining the logic of type selection. Too much versatility can kill focus. Now if the contrast variance is intended as an optical compensation (as some people have been tempted to interpret it above) then that's OK – and then the naming can follow precedents (although "coarse" for one doesn't really jibe in my book).
2 -
Essentially, weight is a function of how thick the stems are, and contrast a function of how thick the hairlines are. So how about, in jargon-free terms:
AcmeFont ThinThins ThinThicksAcmeFont ThinThins ThinThicks SlantedAcmeFont ThinThins ThickThicksAcmeFont ThinThins ThickThicks SlantedAcmeFont ThickThins ThinThicksAcmeFont ThickThins ThinThicks SlantedAcmeFont ThickThins ThickThicksAcmeFont ThickThins ThickThicks Slanted
0 -
Thanks for the discussion. The Font1 and Font2 suggestion is not too far off. I wouldn't give them entirely different names, since the "familiarity" of these two alternates (and the space between) is the whole point, but a blunt AcmeFont A and AcmeFont B would at least communicate quite succinctly that these are variants.Based on discussion here and elsewhere my current favorites are "Contrast & Linear" (Monolinear would be more descriptive, but even longer still), but not 100% convinced — thankfully there is other things to improve uponNeedless to say that font menus are all over the place with this, following no conclusive logic or style linking from what I can tell (some are alphabetical, to an extent, then grouping some weights together, but not all, ...).0
-
I've just remembered the wonderfully named Bernini system by JAF, composed of Bernina and Bernino!
I think Contrast & Linear is pretty good though.0 -
There was a VGC face in the seventies called Baker Sans that had three different contrast styles: Mono (very similar to Helvetica), Display, and Fineline. I wouldn't necessarily endorse it as a solution, but thought it was worth mentioning.3
-
I wouldn’t endorse that, either. One problem with “Mono” by itself is that it is ambiguous, as it could mean either monoline or monospaced.5
-
What would happen if you just leave the "normal" value unmarked? I.e., instead ofAcmeFont Normal RegularAcmeFont Normal Regular ObliqueAcmeFont Normal BoldAcmeFont Normal Bold ObliqueAcmeFont Linear RegularAcmeFont Linear Regular ObliqueAcmeFont Linear BoldAcmeFont Linear Bold Oblique
do this:AcmeFont RegularAcmeFont Regular ObliqueAcmeFont BoldAcmeFont Bold ObliqueAcmeFont Linear RegularAcmeFont Linear Regular ObliqueAcmeFont Linear BoldAcmeFont Linear Bold Oblique
0 -
Thanks for the insightful answers. I agree the mono adds more confusion than it solves, but I like the use-case oriented approach to the naming — it just might not fit this style range. It kind of goes back to what display, text and caption do for optical sizes by describing the essential sum of differences, not just one attribute.@Peter Constable That's what I started off with, but felt it designates one style as the default, the other as a variation; when really I want them to be a pair of same lineage, but different in voice.0
Categories
- All Categories
- 43 Introductions
- 3.7K Typeface Design
- 805 Font Technology
- 1K Technique and Theory
- 622 Type Business
- 444 Type Design Critiques
- 542 Type Design Software
- 30 Punchcutting
- 137 Lettering and Calligraphy
- 84 Technique and Theory
- 53 Lettering Critiques
- 485 Typography
- 303 History of Typography
- 114 Education
- 68 Resources
- 499 Announcements
- 80 Events
- 105 Job Postings
- 148 Type Releases
- 165 Miscellaneous News
- 270 About TypeDrawers
- 53 TypeDrawers Announcements
- 116 Suggestions and Bug Reports