Interpolation problems in Quicksand[wght].ttf

[behdad]

Hello!

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

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 approxequal was not compatible:
  Masters: '', 'wght=700.0':
    Contour 0 has a kink at 12: '', 'wght=700.0'
    Contour 1 has a kink at 12: '', 'wght=700.0'
Glyph asciitilde was not compatible:
  Masters: '', 'wght=700.0':
    Contour 0 has a kink at 12: '', 'wght=700.0'
Glyph g was not compatible:
  Masters: '', 'wght=700.0':
    Contour 0 has a kink at 31: '', 'wght=700.0'
Glyph tildecomb was not compatible:
  Masters: '', 'wght=700.0':
    Contour 0 has a kink at 46: '', 'wght=700.0'
Glyph tildecomb.case was not compatible:
  Masters: '', 'wght=700.0':
    Contour 0 has a kink at 42: '', 'wght=700.0'
Glyph uni0306 was not compatible:
  Masters: '', 'wght=700.0':
    Contour 0 has a kink at 14: '', 'wght=700.0'
Glyph uni0311 was not compatible:
  Masters: '', 'wght=700.0':
    Contour 0 has a kink at 14: '', 'wght=700.0'
Glyph uni032E was not compatible:
  Masters: '', 'wght=700.0':
    Contour 0 has a kink at 14: '', 'wght=700.0'
Glyph uni032E.case was not compatible:
  Masters: '', 'wght=700.0':
    Contour 0 has a kink at 14: '', 'wght=700.0'

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 accept our apologies and ignore / close it.

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

Please note that I am doing this as a community service and do not represent Google Fonts.