## Fontbakery report Fontbakery version: 0.7.33
[14] Yrsa-SemiBold.ttf
💔 ERROR: Show hinting filesize impact. * [com.google.fonts/check/hinting_impact](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/hinting_impact)
--- Rationale ---

This check is merely informative, displaying and useful comparison of filesizes
of hinted versus unhinted font files.


* 💔 **ERROR** The condition had an error: OSError: Could not find the libc shared library
💔 ERROR: Font has old ttfautohint applied? * [com.google.fonts/check/old_ttfautohint](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/old_ttfautohint)
--- Rationale ---

This check finds which version of ttfautohint was used, by inspecting name
table entries and then finds which version of ttfautohint is currently
installed in the system.


* 💔 **ERROR** The check had an error: FailedConditionError: The condition had an error: OSError: Could not find the libc shared library
🔥 FAIL: Check license file has good copyright string. * [com.google.fonts/check/license/OFL_copyright](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/license/OFL_copyright)
--- Rationale ---

An OFL.txt file's first line should be the font copyright e.g:
"Copyright 2019 The Montserrat Project Authors
(https://github.com/julietaula/montserrat)"


* 🔥 **FAIL** First line in license file does not match expected format: "copyright 2010 yrsa and rasa project authors (info@rosettatype.com)"
🔥 FAIL: Check copyright namerecords match license file. * [com.google.fonts/check/name/license](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/name/license)
--- Rationale ---

A known licensing description must be provided in the NameID 14 (LICENSE
DESCRIPTION) entries of the name table.

The source of truth for this check (to determine which license is in use) is a
file placed side-by-side to your font project including the licensing terms.

Depending on the chosen license, one of the following string snippets is
expected to be found on the NameID 13 (LICENSE DESCRIPTION) entries of the name
table:
- "This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is available with a FAQ at: https://scripts.sil.org/OFL"
- "Licensed under the Apache License, Version 2.0"
- "Licensed under the Ubuntu Font Licence 1.0."


Currently accepted licenses are Apache or Open Font License.
For a small set of legacy families the Ubuntu Font License may be acceptable as
well.

When in doubt, please choose OFL for new font projects.


* 🔥 **FAIL** License file LICENSE.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 3 (WINDOWS) is not specified for that. Value was: "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://scripts.sil.org/OFL" Must be changed to "Licensed under the Apache License, Version 2.0" [code: wrong]
🔥 FAIL: Copyright notices match canonical pattern in fonts * [com.google.fonts/check/font_copyright](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/font_copyright) * 🔥 **FAIL** Name Table entry: Copyright notices should match a pattern similar to: "Copyright 2019 The Familyname Project Authors (git url)" But instead we have got: "Copyright 2010 Yrsa and Rasa Project Authors (info@rosettatype.com)" [code: bad-notice-format]
🔥 FAIL: Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts. * [com.google.fonts/check/vertical_metrics_regressions](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vertical_metrics_regressions)
--- Rationale ---

If the family already exists on Google Fonts, we need to ensure that the
checked family's vertical metrics are similar. This check will test the
following schema which was outlined in Fontbakery issue #1162 [1]:

- The family should visually have the same vertical metrics as the Regular
style hosted on Google Fonts.
- If the family on Google Fonts has differing hhea and typo metrics, the family
being checked should use the typo metrics for both the hhea and typo entries.
- If the family on Google Fonts has use typo metrics not enabled and the family
being checked has it enabled, the hhea and typo metrics should use the family
on Google Fonts winAscent and winDescent values.
- If the upms differ, the values must be scaled so the visual appearance is the
same.

[1] https://github.com/googlefonts/fontbakery/issues/1162


* 🔥 **FAIL** Yrsa SemiBold: OS/2 sTypoAscender is 971 when it should be 728 [code: bad-typo-ascender] * 🔥 **FAIL** Yrsa SemiBold: OS/2 sTypoDescender is -423 when it should be -272 [code: bad-typo-descender] * 🔥 **FAIL** Yrsa SemiBold: hhea Ascender is 971 when it should be 728 [code: bad-hhea-ascender] * 🔥 **FAIL** Yrsa SemiBold: hhea Descender is -423 when it should be -272 [code: bad-hhea-descender]
⚠ WARN: Glyphs are similiar to Google Fonts version? * [com.google.fonts/check/production_glyphs_similarity](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/production_glyphs_similarity) * ⚠ **WARN** Following glyphs differ greatly from Google Fonts version: [at, currency, dollar, dollar.tf, m, minute, percent, perthousand, second, uni1E9E, uni20B9, uni20B9.tf, uni20BA, uni20BA.tf]
⚠ WARN: Check if each glyph has the recommended amount of contours. * [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)
--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.


* ⚠ **WARN** This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct. The following glyphs do not have the recommended number of contours: Glyph name: uni1E08 Contours detected: 3 Expected: 2 Glyph name: uni1E09 Contours detected: 3 Expected: 2 Glyph name: uni1E1C Contours detected: 3 Expected: 2 Glyph name: uni1E1D Contours detected: 4 Expected: 3 Glyph name: uni1E08 Contours detected: 3 Expected: 2 Glyph name: uni1E09 Contours detected: 3 Expected: 2 Glyph name: uni1E1C Contours detected: 3 Expected: 2 Glyph name: uni1E1D Contours detected: 4 Expected: 3 [code: contour-count]
⚠ WARN: Are there caret positions declared for every ligature? * [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)
--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

If designing with UFOs, (as of Oct 2020) ligature carets are not yet compiled
by ufo2ft, and therefore will not build via FontMake. See
googlefonts/ufo2ft/issues/329


* ⚠ **WARN** This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]
⚠ WARN: Is there kerning info for non-ligated sequences? * [com.google.fonts/check/kerning_for_non_ligated_sequences](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/kerning_for_non_ligated_sequences)
--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).


* ⚠ **WARN** GPOS table lacks kerning info for the following non-ligated sequences: - f + i - i + j - j + t - germandbls + i - f.ascender + i - f.f + i [code: lacks-kern-info]
⚠ WARN: Check mark characters are in GDEF mark glyph class * [com.google.fonts/check/gdef_mark_chars](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/gdef.html#com.google.fonts/check/gdef_mark_chars)
--- Rationale ---

Mark characters should be in the GDEF mark glyph class.


* ⚠ **WARN** The following mark characters could be in the GDEF mark glyph class: U+0335 [code: mark-chars]
⚠ WARN: Do any segments have colinear vectors? * [com.google.fonts/check/outline_colinear_vectors](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/.html#com.google.fonts/check/outline_colinear_vectors)
--- Rationale ---

This test looks for consecutive line segments which have the same angle. This
normally happens if an outline point has been added by accident.

This test is not run for variable fonts, as they may legitimately have colinear
vectors.


* ⚠ **WARN** The following glyphs have colinear vectors: * arrowboth: L<<734.0,246.0>--<237.0,246.0>> -> L<<237.0,246.0>--<182.0,251.0>> * arrowleft: L<<182.0,317.0>--<237.0,322.0>> -> L<<237.0,322.0>--<529.0,322.0>> * dagger: L<<125.0,413.0>--<120.0,505.0>> -> L<<120.0,505.0>--<120.0,572.0>> * dagger: L<<240.0,572.0>--<240.0,505.0>> -> L<<240.0,505.0>--<235.0,413.0>> * daggerdbl: L<<130.0,413.0>--<124.0,505.0>> -> L<<124.0,505.0>--<124.0,572.0>> * daggerdbl: L<<245.0,572.0>--<245.0,505.0>> -> L<<245.0,505.0>--<240.0,413.0>> * exclam: L<<192.0,606.0>--<192.0,535.0>> -> L<<192.0,535.0>--<163.0,180.0>> * exclam: L<<95.0,180.0>--<66.0,535.0>> -> L<<66.0,535.0>--<66.0,606.0>> * exclamdown.case: L<<154.0,395.0>--<183.0,40.0>> -> L<<183.0,40.0>--<183.0,-31.0>> * exclamdown.case: L<<57.0,-31.0>--<57.0,40.0>> -> L<<57.0,40.0>--<86.0,395.0>> and 16 more. [code: found-colinear-vectors]
⚠ WARN: Do outlines contain any jaggy segments? * [com.google.fonts/check/outline_jaggy_segments](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/.html#com.google.fonts/check/outline_jaggy_segments)
--- Rationale ---

This test heuristically detects outline segments which form a particularly
small angle, indicative of an outline error. This may cause false positives in
cases such as extreme ink traps, so should be regarded as advisory and backed
up by manual inspection.


* ⚠ **WARN** The following glyphs have jaggy segments: * aogonek: L<<326.0,-4.0>--<326.0,-4.0>>/B<<326.0,-4.0>-<286.0,4.0>-<272.0,43.0>> = 11.309932474020195 * at.case: B<<463.5,197.0>-<465.0,216.0>-<467.0,236.0>>/B<<467.0,236.0>-<420.0,78.0>-<326.0,78.0>> = 10.855482761010082 * at: B<<463.5,107.0>-<465.0,126.0>-<467.0,146.0>>/B<<467.0,146.0>-<420.0,-12.0>-<326.0,-12.0>> = 10.855482761010082 * three.dnom: B<<283.0,216.0>-<254.0,194.0>-<223.0,189.0>>/B<<223.0,189.0>-<262.0,189.0>-<294.5,168.5>> = 9.162347045721706 * three.lf.tf: B<<366.0,355.0>-<328.0,318.0>-<273.0,306.0>>/B<<273.0,306.0>-<311.0,307.0>-<347.5,292.5>> = 10.800580058652953 * three.lf: B<<353.0,355.0>-<315.0,318.0>-<260.0,306.0>>/B<<260.0,306.0>-<298.0,307.0>-<334.5,292.5>> = 10.800580058652953 * three.numr: B<<283.0,443.0>-<254.0,421.0>-<223.0,416.0>>/B<<223.0,416.0>-<262.0,416.0>-<294.5,395.5>> = 9.162347045721706 * three.tf: B<<354.0,314.5>-<320.0,281.0>-<272.0,268.0>>/B<<272.0,268.0>-<306.0,269.0>-<339.0,257.0>> = 13.469383732416311 * three: B<<331.0,314.5>-<297.0,281.0>-<249.0,268.0>>/B<<249.0,268.0>-<283.0,269.0>-<316.0,257.0>> = 13.469383732416311 * threequarters: B<<283.0,443.0>-<254.0,421.0>-<223.0,416.0>>/B<<223.0,416.0>-<262.0,416.0>-<294.5,395.5>> = 9.162347045721706 and 5 more. [code: found-jaggy-segments]
⚠ WARN: Do outlines contain any semi-vertical or semi-horizontal lines? * [com.google.fonts/check/outline_semi_vertical](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/.html#com.google.fonts/check/outline_semi_vertical)
--- Rationale ---

This test detects line segments which are nearly, but not quite, exactly
horizontal or vertical. Sometimes such lines are created by design, but often
they are indicative of a design error.

This test is disabled for italic styles, which often contain nearly-upright
lines.


* ⚠ **WARN** The following glyphs have semi-vertical/semi-horizontal lines: * bar: L<<161.0,692.0>--<160.0,-114.0>> * pi: L<<183.0,421.0>--<507.0,422.0>> * uni018F: L<<45.0,284.0>--<395.0,283.0>> * uni20BC.tf: L<<319.0,0.0>--<318.0,293.0>> and uni20BC: L<<81.0,77.0>--<80.0,285.0>> [code: found-semi-vertical]

### Summary | 💔 ERROR | 🔥 FAIL | ⚠ WARN | 💤 SKIP | ℹ INFO | 🍞 PASS | 🔎 DEBUG | |:-----:|:----:|:----:|:----:|:----:|:----:|:----:| | 2 | 4 | 8 | 89 | 7 | 84 | 0 | | 1% | 2% | 4% | 46% | 4% | 43% | 0% | **Note:** The following loglevels were omitted in this report: * **SKIP** * **INFO** * **PASS** * **DEBUG**