omnibus-type / asap Goto Github PK

Issue #2436 on Google Fonts.

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.

Hello!

This is an automatically-generated report about possible interpolation problems in Asap[wdth,wght].ttf, as found in the Google Fonts catalog.

The particular version of the font that was tested was archive:.

To download a PDF version of this report with helpful visuals of the problems, click here; Or to view it on the GitHub website, click here.

The report follows:

Glyph lozenge was not compatible:
  Masters: 'wdth=125.0', 'wdth=125.0 wght=100.0':
    Contour 1 start point differs: 0 in 'wdth=125.0', 1 in 'wdth=125.0 wght=100.0'; reversed: False

This report was generated using the fonttools varLib.interpolatable tool. We understand that sometimes the tool generates false-positives. Particularly for more complicated font designs. If you did not find this report useful, please apologize and ignore & close it.

To give feedback about this report, please file an issue or open a discussion at fonttools.

@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]

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 🙂.