Closed m4rc1e closed 4 years ago
It may also make things cleaner to make fonts/Roboto[ital,wdth,wght].ttf
a variable e.g VF_OUT=fonts/Roboto[ital,wdth,wght].ttf
.
We can then use this for each tool e.g fontmake -m Roboto-min.designspace --output-path $VF_OUT
Roboto classic uses a makefile which allows users to build different font sets. We should have similar functionality with an identical interface if we want to make this project a true replacement.
@sannorozco please can you submit your commits as pull requests going forward. This gives me a better way to review what we're doing.
I've just taken a quick look at the build-min. The fonts build which is great but we should make it neater.
Here are some quick changes I'd make:
Current:
New:
Current:
New:
We have a gftools script for this.
Current:
New:
Mike's hinting work should be kept in the sources dir and stored as xml. This way we can see his changes instead of a binary blob
Current:
New:
Are we sure this is going to work? Idk but maybe this table is always recalculated by fonttools each time we make a modification? I also dislike that the values are hardcoded which means we'll constantly need to update it each time we modify the fonts. If this table isn't regenerated by fonttools, perhaps we should write our own maxp table generator?
Current:
New:
When you compile the hints, use the
--ship
flag. This will remove these tables automatically.cc @davelab6