googlefonts / italianno Goto Github PK

• com.google.fonts/check/fstype

--- Rationale ---

The fsType in the OS/2 table is a legacy DRM-related field. Fonts in the Google
Fonts collection must have it set to zero (also known as "Installable
Embedding"). This setting indicates that the fonts can be embedded in documents
and permanently installed by applications on remote systems.

More detailed info is available at:
https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype

• 🔥 FAIL In this font fsType is set to 4 meaning that:
  The font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.

No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead. [code: drm]

• com.google.fonts/check/glyph_coverage

--- Rationale ---

Google Fonts expects that fonts in its collection support at least the minimal
set of characters defined in the `GF-latin-core` glyph-set.

• 🔥 FAIL Missing required codepoints: 0x00AD (SOFT HYPHEN) and 0x2215 (DIVISION SLASH) [code: missing-codepoints]

• com.google.fonts/check/gasp

--- Rationale ---

Traditionally version 0 'gasp' tables were set so that font sizes below 8 ppem
had no grid fitting but did have antialiasing. From 9-16 ppem, just grid
fitting. And fonts above 17ppem had both antialiasing and grid fitting toggled
on. The use of accelerated graphics cards and higher resolution screens make
this approach obsolete. Microsoft's DirectWrite pushed this even further with
much improved rendering built into the OS and apps.

In this scenario it makes sense to simply toggle all 4 flags ON for all font
sizes.

• 🔥 FAIL Font is missing the 'gasp' table. Try exporting the font with autohinting enabled.
  If you are dealing with an unhinted font, it can be fixed by running the fonts through the command 'gftools fix-nonhinting'
  GFTools is available at https://pypi.org/project/gftools/ [code: lacks-gasp]

• 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:
  "\251 2009 Robert E. Leuschke -- This font is not Shareware and may not be copied, sold, distributed or shared without permission from Gideon, Inc. 114 Long and Winding Road, St. Peters, MO 63376 USA Distributed by MyFONTS.com" [code: bad-notice-format]

• 🔥 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:
  "\251 2009 Robert E. Leuschke -- This font is not Shareware and may not be copied, sold, distributed or shared without permission from Gideon, Inc. 114 Long and Winding Road, St. Peters, MO 63376 USA Distributed by MyFONTS.com" [code: bad-notice-format]

• com.google.fonts/check/name/familyname

--- Rationale ---

Checks that the family name infered from the font filename matches the string
at nameID 1 (NAMEID_FONT_FAMILY_NAME) if it conforms to RIBBI and otherwise
checks that nameID 1 is the family name + the style name.

• 🔥 FAIL Entry [FONT_FAMILY_NAME(1):MACINTOSH(1)] on the "name" table: Expected "Italianno Rob" but got "ItaliannoRob". [code: mismatch]
• 🔥 FAIL Entry [FONT_FAMILY_NAME(1):WINDOWS(3)] on the "name" table: Expected "Italianno Rob" but got "ItaliannoRob". [code: mismatch]

• com.google.fonts/check/name/fullfontname

• 🔥 FAIL Entry [FULL_FONT_NAME(4):MACINTOSH(1)] on the "name" table: Expected "Italianno Rob Regular" but got "ItaliannoRob-Regular". [code: bad-entry]

• 🔥 FAIL Entry [FULL_FONT_NAME(4):WINDOWS(3)] on the "name" table: Expected "Italianno Rob Regular" but got "ItaliannoRob-Regular". [code: bad-entry]

• com.google.fonts/check/smart_dropout

--- Rationale ---

This setup is meant to ensure consistent rendering quality for fonts across all
devices (with different rendering/hinting capabilities).

Below is the snippet of instructions we expect to see in the fonts:
B8 01 FF    PUSHW 0x01FF
85          SCANCTRL (unconditinally turn on
                      dropout control mode)
B0 04       PUSHB 0x04
8D          SCANTYPE (enable smart dropout control)

"Smart dropout control" means activating rules 1, 2 and 5:
Rule 1: If a pixel's center falls within the glyph outline,
        that pixel is turned on.
Rule 2: If a contour falls exactly on a pixel's center,
        that pixel is turned on.
Rule 5: If a scan line between two adjacent pixel centers
        (either vertical or horizontal) is intersected
        by both an on-Transition contour and an off-Transition
        contour and neither of the pixels was already turned on
        by rules 1 and 2, turn on the pixel which is closer to
        the midpoint between the on-Transition contour and
        off-Transition contour. This is "Smart" dropout control.

For more detailed info (such as other rules not enabled in this snippet),
please refer to the TrueType Instruction Set documentation.

• 🔥 FAIL The 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script. [code: lacks-smart-dropout]

• com.google.fonts/check/family/win_ascent_and_descent

--- Rationale ---

A font's winAscent and winDescent values should be greater than the head
table's yMax, abs(yMin) values. If they are less than these values, clipping
can occur on Windows platforms
(https://github.com/RedHatBrand/Overpass/issues/33).

If the font includes tall/deep writing systems such as Arabic or Devanagari,
the winAscent and winDescent can be greater than the yMax and abs(yMin) to
accommodate vowel marks.

When the win Metrics are significantly greater than the upm, the linespacing
can appear too loose. To counteract this, enabling the OS/2 fsSelection bit 7
(Use_Typo_Metrics), will force Windows to use the OS/2 typo values instead.
This means the font developer can control the linespacing with the typo values,
whilst avoiding clipping by setting the win values to values greater than the
yMax and abs(yMin).

• 🔥 FAIL OS/2.usWinAscent value should be equal or greater than 817, but got 699 instead [code: ascent]
• 🔥 FAIL OS/2.usWinDescent value should be equal or greater than 450, but got 387 instead. [code: descent]

• com.google.fonts/check/os2_metrics_match_hhea

--- Rationale ---

When OS/2 and hhea vertical metrics match, the same linespacing results on
macOS, GNU+Linux and Windows. Unfortunately as of 2018, Google Fonts has
released many fonts with vertical metrics that don't match in this way. When we
fix this issue in these existing families, we will create a visible change in
line/paragraph layout for either Windows or macOS users, which will upset some
of them.

But we have a duty to fix broken stuff, and inconsistent paragraph layout is
unacceptably broken when it is possible to avoid it.

If users complain and prefer the old broken version, they have the freedom to
take care of their own situation.

• 🔥 FAIL OS/2 sTypoAscender (613) and hhea ascent (699) must be equal. [code: ascender]

• com.google.fonts/check/whitespace_widths

• 🔥 FAIL Space and non-breaking space have differing width: The space glyph named space is 169 font units wide, non-breaking space named (uni00A0) is 166 font units wide, and both should be positive and the same. GlyphsApp has "Sidebearing arithmetic" (https://glyphsapp.com/tutorials/spacing) which allows you to set the non-breaking space width to always equal the space width. [code: different-widths]

• com.google.fonts/check/glyf_nested_components

--- Rationale ---

There have been bugs rendering variable fonts with nested components.
Additionally, some static fonts with nested components have been reported to
have rendering and printing issues.

For more info, see:
* https://github.com/googlefonts/fontbakery/issues/2961
* https://github.com/arrowtype/recursive/issues/412

• 🔥 FAIL The following glyphs have components which themselves are component glyphs:
  • uni1EAA
  • uni1EC4
  • uni1ED6
  • uni1EAB
  • uni1EC5 and uni1ED7 [code: found-nested-components]

• com.google.fonts/check/vendor_id

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

• ⚠ WARN OS/2 VendorID is 'UKWN', a font editor default. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx
  [code: bad]

• 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: percent Contours detected: 2 Expected: 5
Glyph name: ampersand Contours detected: 4 Expected: 1, 2 or 3
Glyph name: A Contours detected: 1 Expected: 2
Glyph name: underscore Contours detected: 0 Expected: 1
Glyph name: l Contours detected: 2 Expected: 1
Glyph name: onequarter Contours detected: 1 Expected: 3 or 4
Glyph name: Agrave Contours detected: 2 Expected: 3
Glyph name: Aacute Contours detected: 2 Expected: 3
Glyph name: Acircumflex Contours detected: 2 Expected: 3
Glyph name: Atilde Contours detected: 2 Expected: 3
Glyph name: Adieresis Contours detected: 3 Expected: 4
Glyph name: AE Contours detected: 1 Expected: 2
Glyph name: Amacron Contours detected: 2 Expected: 3
Glyph name: Abreve Contours detected: 2 Expected: 3
Glyph name: aogonek Contours detected: 3 Expected: 2
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: eogonek Contours detected: 3 Expected: 2
Glyph name: hbar Contours detected: 2 Expected: 1
Glyph name: lacute Contours detected: 3 Expected: 2
Glyph name: uni013C Contours detected: 3 Expected: 2
Glyph name: lcaron Contours detected: 3 Expected: 2
Glyph name: lslash Contours detected: 3 Expected: 1
Glyph name: Racute Contours detected: 2 Expected: 3
Glyph name: uni0156 Contours detected: 2 Expected: 3
Glyph name: Rcaron Contours detected: 2 Expected: 3
Glyph name: Tbar Contours detected: 2 Expected: 1
Glyph name: tbar Contours detected: 2 Expected: 1
Glyph name: Uogonek Contours detected: 2 Expected: 1
Glyph name: uogonek Contours detected: 2 Expected: 1
Glyph name: ohorn Contours detected: 3 Expected: 2
Glyph name: Uhorn Contours detected: 2 Expected: 1
Glyph name: uhorn Contours detected: 2 Expected: 1
Glyph name: uni1E9E Contours detected: 2 Expected: 1
Glyph name: uni1EA0 Contours detected: 2 Expected: 3
Glyph name: uni1EA2 Contours detected: 2 Expected: 3
Glyph name: uni1EA4 Contours detected: 3 Expected: 4
Glyph name: uni1EA6 Contours detected: 3 Expected: 4
Glyph name: uni1EA8 Contours detected: 3 Expected: 4
Glyph name: uni1EAA Contours detected: 3 Expected: 4
Glyph name: uni1EAC Contours detected: 3 Expected: 4
Glyph name: uni1EAE Contours detected: 3 Expected: 4
Glyph name: uni1EB0 Contours detected: 3 Expected: 4
Glyph name: uni1EB2 Contours detected: 3 Expected: 4
Glyph name: uni1EB4 Contours detected: 3 Expected: 4
Glyph name: uni1EB6 Contours detected: 3 Expected: 4
Glyph name: uni1EDB Contours detected: 4 Expected: 3
Glyph name: uni1EDD Contours detected: 4 Expected: 3
Glyph name: uni1EDF Contours detected: 4 Expected: 3
Glyph name: uni1EE1 Contours detected: 4 Expected: 3
Glyph name: uni1EE3 Contours detected: 4 Expected: 3
Glyph name: uni1EE8 Contours detected: 3 Expected: 2
Glyph name: uni1EE9 Contours detected: 3 Expected: 2
Glyph name: uni1EEA Contours detected: 3 Expected: 2
Glyph name: uni1EEB Contours detected: 3 Expected: 2
Glyph name: uni1EEC Contours detected: 3 Expected: 2
Glyph name: uni1EED Contours detected: 3 Expected: 2
Glyph name: uni1EEE Contours detected: 3 Expected: 2
Glyph name: uni1EEF Contours detected: 3 Expected: 2
Glyph name: uni1EF0 Contours detected: 3 Expected: 2
Glyph name: uni1EF1 Contours detected: 3 Expected: 2
Glyph name: perthousand Contours detected: 3 Expected: 6 or 7
Glyph name: partialdiff Contours detected: 1 Expected: 2
Glyph name: radical Contours detected: 2 Expected: 1
Glyph name: f_f Contours detected: 3 Expected: 1 or 2
Glyph name: A Contours detected: 1 Expected: 2
Glyph name: AE Contours detected: 1 Expected: 2
Glyph name: Aacute Contours detected: 2 Expected: 3
Glyph name: Abreve Contours detected: 2 Expected: 3
Glyph name: Acircumflex Contours detected: 2 Expected: 3
Glyph name: Adieresis Contours detected: 3 Expected: 4
Glyph name: Agrave Contours detected: 2 Expected: 3
Glyph name: Amacron Contours detected: 2 Expected: 3
Glyph name: Atilde Contours detected: 2 Expected: 3
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: Racute Contours detected: 2 Expected: 3
Glyph name: Rcaron Contours detected: 2 Expected: 3
Glyph name: Tbar Contours detected: 2 Expected: 1
Glyph name: Uhorn Contours detected: 2 Expected: 1
Glyph name: Uogonek Contours detected: 2 Expected: 1
Glyph name: ampersand Contours detected: 4 Expected: 1, 2 or 3
Glyph name: aogonek Contours detected: 3 Expected: 2
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: eogonek Contours detected: 3 Expected: 2
Glyph name: f_f Contours detected: 3 Expected: 1 or 2
Glyph name: fi Contours detected: 2 Expected: 3
Glyph name: hbar Contours detected: 2 Expected: 1
Glyph name: l Contours detected: 2 Expected: 1
Glyph name: lacute Contours detected: 3 Expected: 2
Glyph name: lcaron Contours detected: 3 Expected: 2
Glyph name: lslash Contours detected: 3 Expected: 1
Glyph name: ohorn Contours detected: 3 Expected: 2
Glyph name: onequarter Contours detected: 1 Expected: 3 or 4
Glyph name: partialdiff Contours detected: 1 Expected: 2
Glyph name: percent Contours detected: 2 Expected: 5
Glyph name: perthousand Contours detected: 3 Expected: 6 or 7
Glyph name: radical Contours detected: 2 Expected: 1
Glyph name: tbar Contours detected: 2 Expected: 1
Glyph name: uhorn Contours detected: 2 Expected: 1
Glyph name: underscore Contours detected: 0 Expected: 1
Glyph name: uni013C Contours detected: 3 Expected: 2
Glyph name: uni0156 Contours detected: 2 Expected: 3
Glyph name: uni1E9E Contours detected: 2 Expected: 1
Glyph name: uni1EA0 Contours detected: 2 Expected: 3
Glyph name: uni1EA2 Contours detected: 2 Expected: 3
Glyph name: uni1EA4 Contours detected: 3 Expected: 4
Glyph name: uni1EA6 Contours detected: 3 Expected: 4
Glyph name: uni1EA8 Contours detected: 3 Expected: 4
Glyph name: uni1EAA Contours detected: 3 Expected: 4
Glyph name: uni1EAC Contours detected: 3 Expected: 4
Glyph name: uni1EAE Contours detected: 3 Expected: 4
Glyph name: uni1EB0 Contours detected: 3 Expected: 4
Glyph name: uni1EB2 Contours detected: 3 Expected: 4
Glyph name: uni1EB4 Contours detected: 3 Expected: 4
Glyph name: uni1EB6 Contours detected: 3 Expected: 4
Glyph name: uni1EDB Contours detected: 4 Expected: 3
Glyph name: uni1EDD Contours detected: 4 Expected: 3
Glyph name: uni1EDF Contours detected: 4 Expected: 3
Glyph name: uni1EE1 Contours detected: 4 Expected: 3
Glyph name: uni1EE3 Contours detected: 4 Expected: 3
Glyph name: uni1EE8 Contours detected: 3 Expected: 2
Glyph name: uni1EE9 Contours detected: 3 Expected: 2
Glyph name: uni1EEA Contours detected: 3 Expected: 2
Glyph name: uni1EEB Contours detected: 3 Expected: 2
Glyph name: uni1EEC Contours detected: 3 Expected: 2
Glyph name: uni1EED Contours detected: 3 Expected: 2
Glyph name: uni1EEE Contours detected: 3 Expected: 2
Glyph name: uni1EEF Contours detected: 3 Expected: 2
Glyph name: uni1EF0 Contours detected: 3 Expected: 2
Glyph name: uni1EF1 Contours detected: 3 Expected: 2
Glyph name: uogonek Contours detected: 2 Expected: 1 [code: contour-count]

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

• 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 + f
  • f + i
  • i + f
  • f + l
  • l + f
  • i + l

  [code: lacks-kern-info]

• com.google.fonts/check/mandatory_glyphs

--- Rationale ---

The OpenType specification v1.8.2 recommends that the first glyph is the
'.notdef' glyph without a codepoint assigned and with a drawing.

https://docs.microsoft.com/en-us/typography/opentype/spec
/recom#glyph-0-the-notdef-glyph

Pre-v1.8, it was recommended that fonts should also contain 'space', 'CR' and
'.null' glyphs. This might have been relevant for MacOS 9 applications.

• ⚠ WARN Glyph '.notdef' should contain a drawing, but it is empty. [code: empty]

• com.google.fonts/check/linegaps

• ⚠ WARN OS/2 sTypoLineGap is not equal to 0. [code: OS/2]

• [com.google.fonts/check/outline_jaggy_segments](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/<Section: Outline Correctness Checks>.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:
  • A.roman: L<<571.0,-2.0>--<571.0,-2.0>>/B<<571.0,-2.0>-<491.0,2.0>-<469.0,2.0>> = 2.862405226111651
  • A.sm: L<<397.0,-1.0>--<397.0,-1.0>>/B<<397.0,-1.0>-<356.0,1.0>-<325.0,1.0>> = 2.792702365713218
  • A_acute.roman: L<<571.0,-2.0>--<571.0,-2.0>>/B<<571.0,-2.0>-<491.0,2.0>-<469.0,2.0>> = 2.862405226111651
  • A_acute.sm: L<<397.0,-1.0>--<397.0,-1.0>>/B<<397.0,-1.0>-<356.0,1.0>-<325.0,1.0>> = 2.792702365713218
  • A_breve.roman: L<<571.0,-2.0>--<571.0,-2.0>>/B<<571.0,-2.0>-<491.0,2.0>-<469.0,2.0>> = 2.862405226111651
  • A_breve.sm: L<<397.0,-1.0>--<397.0,-1.0>>/B<<397.0,-1.0>-<356.0,1.0>-<325.0,1.0>> = 2.792702365713218
  • A_circumflex.roman: B<<334.0,584.0>-<329.0,582.0>-<320.0,584.0>>/L<<320.0,584.0>--<320.0,584.0>> = 12.528807709151492
  • A_circumflex.roman: L<<571.0,-2.0>--<571.0,-2.0>>/B<<571.0,-2.0>-<491.0,2.0>-<469.0,2.0>> = 2.862405226111651
  • A_circumflex.sm: B<<206.0,418.0>-<201.0,416.0>-<192.0,418.0>>/L<<192.0,418.0>--<192.0,418.0>> = 12.528807709151492
  • A_circumflex.sm: L<<397.0,-1.0>--<397.0,-1.0>>/B<<397.0,-1.0>-<356.0,1.0>-<325.0,1.0>> = 2.792702365713218 and 342 more. [code: found-jaggy-segments]

• [com.google.fonts/check/outline_semi_vertical](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/<Section: Outline Correctness Checks>.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:
  • AE.roman: L<<671.0,529.0>--<791.0,530.0>>
  • B: L<<234.0,544.0>--<383.0,545.0>>
  • E.roman: L<<362.0,529.0>--<482.0,530.0>>
  • E_acute.roman: L<<362.0,529.0>--<482.0,530.0>>
  • E_caron.roman: L<<362.0,529.0>--<482.0,530.0>>
  • E_circumflex.roman: L<<362.0,529.0>--<482.0,530.0>>
  • E_dieresis.roman: L<<362.0,529.0>--<482.0,530.0>>
  • E_dotaccent.roman: L<<362.0,529.0>--<482.0,530.0>>
  • E_grave.roman: L<<362.0,529.0>--<482.0,530.0>>
  • E_macron.roman: L<<362.0,529.0>--<482.0,530.0>> and 72 more. [code: found-semi-vertical]