After #3, hinting will need to be added, in 3 ways:
[ ] For the VFs with a CVAR table, likely with ttfautohint-vf
[ ] For statics instantiated from the VFs with fontTools, where CVAR table becomes CVT table (likely not posted for end-users, but this process should work)
[ ] For statics hand-generated by FontLab and a post-processing hinting step, which may actually be with FontLab; this should be to the full hinting level to match the "v1.x" Lato in the GF API today. @twardoch will look into doing this with a hinting specialist.
barmadrid
commented
3 years ago
After #3, hinting will need to be added, in 3 ways:
[ ] For the VFs with a CVAR table, likely with ttfautohint-vf
[ ] For statics instantiated from the VFs with fontTools, where CVAR table becomes CVT table (likely not posted for end-users, but this process should work)
[ ] For statics hand-generated by FontLab and a post-processing hinting step, which may actually be with FontLab; this should be to the full hinting level to match the "v1.x" Lato in the GF API today. @twardoch will look into doing this with a hinting specialist.