omnibus-type / asap Goto Github PK

Issue #2436 on Google Fonts.

Quite a few fonts nowadays offer a capital I with crossbars as a character variant. The idea is that offering this variant allows people to use the font in contexts where ambiguity between capital I, lowercase l, and the number 1 is unacceptable, for example when the font is used to display passwords or serial numbers.

It would be cool if Asap had this 🙂.

If a component's mark glyph doesn't have the same contour direction as the base glyph, you get bad rendering in OS X

cc @pichotta

We had this issue in Roboto as well. The solution was to fix the contour direction for the offending glyphs.

@Yorlmar
@Omnibus-Type
@davelab6

Hello Pablo and Omnibus,

The Google fonts team would love to see a variable font version of ‘Asap'. 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. 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.

Does this repository have the most current font data for 'Asap'?

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
[email protected]