@Mark Simonson@Hrant H. Papazian Thank You. Most probably Idea for "Width" as "keep it simple" win It will be hard enough to show CNC-users that a typeface can be variable.
DJR's latest font, Extendomatic, contains a similar function. In the variable font, the width axis is referred to as "Tracking". Whether that's the most appropriate term is up for debate, but it certainly makes sense to me.
You're right, "Tracking" could be a good term for it, but from my point of view is too confusing with the slider found in most programs and "bad tracking of scripts".
btw. my new test of 2 axes - width (letterspacing) & stroke
I wasn’t going to chime in, but since so many people are favoring “width,” I feel like I should maybe share my opinion in case you’re interested in hearing an opposing stance.
As a graphic designer who uses fonts more than I design them, I favor either “letter spacing,” “spacing,” or “tracking.”
Just because the letters are connected does not mean there isn’t space between the characters. I would argue that there is the core form of the letter (which has a width), and then there is the connections between the letters which make up the perceived letter spacing.
In your first animation, I see your letters getting tighter not narrower.
This isn’t necessarily a hill I’m willing to die on (especially if you don’t see yourself drawing an axis with narrower or wider base/core letterforms), but I figured I’d share my thoughts in case you find them valuable.
Since you are planning to add such an axis in future, I retract my proposal.
I'm curious what you propose instead of width.
In the parametric axes system, changes isolated to X and Y dimensions use that as basis of the first letter of the axis code, and then if it's effects ink (opacity) or space (transparency) for the second letter. So I will probably register something "XT??" for this with Google Fonts. XTRK for X Transparency Tracking? XTSP for X Transparency Spacing?
Right, if there is a significant chance of having both kinds of width axis in the future, def save the one called “width” for the more normal implementation.
first "quick and dirty" prototype of normal Width axis made me sure that it is worth keeping the name for the future - cooperation of these two axes has potential now I like the Span proposal of @Hrant H. Papazian more and more...
I think its good for users to have separate control of the 'X Transparency' changes within a glyph from the 'X Transparency Spacing' changes between glyphs, instead of blending them.
The initial lexend.com fonts by Thomas Jockin did this, with a single LXND axis, and the latest ones at https://github.com/FontBureau/fb-lexend split them out.
Comments
I encourage you to use wdth and wght axes for this.
Conceptually, it is a connected script with a width axis. No reason to invent something new.
Just because the letters are connected does not mean there isn’t space between the characters. I would argue that there is the core form of the letter (which has a width), and then there is the connections between the letters which make up the perceived letter spacing.
I'm yet to see any demo font that does this, despite it being talked about since 2016.
Has anyone seen such a font?
thanks for paying my attention. I will probably want to add such an axis in future and I would have to change axes names
Since you are planning to add such an axis in future, I retract my proposal.
I'm curious what you propose instead of width.
In the parametric axes system, changes isolated to X and Y dimensions use that as basis of the first letter of the axis code, and then if it's effects ink (opacity) or space (transparency) for the second letter. So I will probably register something "XT??" for this with Google Fonts. XTRK for X Transparency Tracking? XTSP for X Transparency Spacing?
now I like the Span proposal of @Hrant H. Papazian more and more...
The initial lexend.com fonts by Thomas Jockin did this, with a single LXND axis, and the latest ones at https://github.com/FontBureau/fb-lexend split them out.
Congrats, and good luck.