The Google fonts team would love to see a variable fonts version of ‘Assistant'. They have commissioned us @TypeNetwork to work on upgrading a number of font projects to be variable fonts with a single weight axis.
In order to achieve the highest quality and most efficient long term results we will be converting the source data from Glyphs to UFO. The new source data will be generated in the RoboFont environment using fontmake and ttfautohint. There has been progress on tools to make an easy path to move between the Glyphs and Robofont environment.
During the process we will be looking to improve any errors while preserving how the font appears and renders on different platforms.
@hafontia
Hello Nathan,
The Google fonts team would love to see a variable fonts version of ‘Assistant'. They have commissioned us @TypeNetwork to work on upgrading a number of font projects to be variable fonts with a single weight axis.
In order to achieve the highest quality and most efficient long term results we will be converting the source data from Glyphs to UFO. The new source data will be generated in the RoboFont environment using fontmake and ttfautohint. There has been progress on tools to make an easy path to move between the Glyphs and Robofont environment.
During the process we will be looking to improve any errors while preserving how the font appears and renders on different platforms.
We have started by making a fork off of this git repository. There is currently a beta VF.ttf on the TN fea-conv-ufo fork. https://github.com/TypeNetwork/Assistant/tree/fea-ufo-conv/Fonts
The upgrade will be completed for you in the near future. When the proposed final font is approved by Google they will accept a pull request.
We hope this answers some of your questions about the process. Please let us know if you have any additional comments.
Best Regards,
Jill Pichotta Vice President Type Network pichotta@typenetwork.com