Closed davelab6 closed 5 years ago
@ThomasJockin ping on this; we are blocked from a Google Fonts launch on these issues.
I also propose renaming the axis from LXND
to REVR
so that it isn't font-specific and could be adopted by other projects.
Also, the filenames and Font Info (name table) metadata should be family names and style names should be regular (400 weight, 100 width)
current filename | required filename |
---|---|
Lexend-Default.ttf | Lexend-Regular.ttf |
Lexend-Exa.ttf | LexendExa-Regular.ttf |
Lexend-Giga.ttf | LexendGiga-Regular.ttf |
Lexend-Kilo.ttf | LexendKilo-Regular.ttf |
Lexend-Mega.ttf | LexendMega-Regular.ttf |
Lexend-Peta.ttf | LexendPeta-Regular.ttf |
Lexend-Tera.ttf | LexendTera-Regular.ttf |
LexendGX.ttf | Lexend[REVR].ttf |
Noted. Will address issues once back from Istanbul. Axis name proposal will be discussed with Bonnie later today. Will circle back decision later today.
I wonder that perhaps even using the Microsoft registered wdth
axis would be better, as more applications will have support for that with direct UIs. It isn't a typical Width axis but I don't see why that can't work :)
For the sake of keeping things simple for the audience at ISType, I recommend we keep LXND
.
LXND is hinted in the fun logo detail Micah added ;-)
I spoke to @ThomasJockin about this and he persuaded me that since this is doing two things - increasing space inside letters and between letters - then wdth
is not appropriate.
@ThomasJockin also wants it to be a project specific axes for now.
SGTM
I'll take over this issue so we comfortably hit our deadine
As Dave pointed out with the filenames, I'm making each individual style its own family so this project complies with our API.
Please build a new release: