The genos from googlefonts

Browsers Preview

Thin, ExtraLight, Light, Regular

Windows 10 Chrome_71

Windows 10 Edge_18

OS X High Sierra Safari_11

Interpolation problems in `Genos-Italic[wght].ttf`

Hello!

This is an automatically-generated report about possible interpolation problems in Genos-Italic[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=900.0':
    Contour 0 start point differs: 0 in '', 4 in 'wght=900.0'; reversed: False
    Contour 1 start point differs: 0 in '', 4 in 'wght=900.0'; reversed: False
Glyph backslash was not compatible:
  Masters: '', 'wght=900.0':
    Contour 0 start point differs: 0 in '', 2 in 'wght=900.0'; reversed: False
Glyph greaterequal was not compatible:
  Masters: '', 'wght=900.0':
    Contour 1 start point differs: 0 in '', 2 in 'wght=900.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 accept our apologies and ignore / close it.

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

Font Mastering

Diacritics

Composite glyphs need to be made out of components using anchors
Comb.case are missing
Misaligned diacritics
Create caron.alt and adjust Lcaron, lcaron, dcaron, tcaron

Glyphs

Missing glyphs: 0x2215 (DIVISION SLASH)
Add extreme points
Correct path direction (command)

OT Features

Ensure the OT features include everything and are working well (e.g. fi fl included)

Interpolation problems in `Genos[wght].ttf`

Hello!

This is an automatically-generated report about possible interpolation problems in Genos[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=900.0':
    Contour 0 start point differs: 0 in '', 4 in 'wght=900.0'; reversed: False
    Contour 1 start point differs: 0 in '', 4 in 'wght=900.0'; reversed: False
Glyph backslash was not compatible:
  Masters: '', 'wght=900.0':
    Contour 0 start point differs: 0 in '', 2 in 'wght=900.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 accept our apologies and ignore / close it.

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

Font Production

Design Issues

Google Fonts Latin Plus coverage

Design all the glyphs required in the GF Latin Plus encoding
Create all the comb marks as mentioned below
Leave only the compound glyphs (e.g. adblgrave) marked in dark grey as pending to be created using the components

Diacritics

Please ensure the definitive design is adjusted in the combining marks, so they will be ready to create the compound glyphs.
Once the definitive design is ensured in the comb marks Legacy marks, delete the legacy marks and add them back so they are made using the comb marks as components.
Diacritics need to be balanced (in weight, size, contrast) and matching the style of the typeface design.
Adjust the vertical position using glyphs app locked guidelines.
Ensure related marks are consistent between them, e.g. caron and circumflex
Caron.alt need to have the alternate shape used in Ľ Slovak On page 30 of this document you can find detailed info around the vertical Caron.
Leave a 0 sidebearings value for the marks

Glyphs

The ampersand and Eng need to be consistent (in size and style) with the font. See RUSerius as reference
The German Double SS need to be fixed. This article is a good reference
Currency symbols are related to the overall design and have balanced proportions
ordfeminine and ordmasculine as well as superior numbers are well proportioned and with a balanced stem thickness. Issue of reference

FB initial assessment report

Fontbakery report

Fontbakery version: 0.7.34

[22] GenosGX.ttf

🔥 FAIL: Checking file is named canonically.

com.google.fonts/check/canonical_filename

--- Rationale ---

A font's filename must be composed in the following manner:
<familyname>-<stylename>.ttf

- Nunito-Regular.ttf,
- Oswald-BoldItalic.ttf

Variable fonts must list the axis tags in alphabetical order in square brackets
and separated by commas:

- Roboto[wdth,wght].ttf
- Familyname-Italic[wght].ttf

🔥 FAIL The file 'GenosGX.ttf' must be renamed to 'Genos[wght].ttf' according to the Google Fonts naming policy for variable fonts. [code: bad-varfont-filename]

🔥 FAIL: Checking OS/2 fsType does not impose restrictions.

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]

🔥 FAIL: Check `Google Fonts Latin Core` glyph coverage.

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: 0x2215 (DIVISION SLASH) [code: missing-codepoints]

🔥 FAIL: Substitute copyright, registered and trademark symbols in name table entries.

com.google.fonts/check/name/unwanted_chars
🔥 FAIL NAMEID #10 contains symbols that should be replaced by '(c)'. [code: unwanted-chars]
🔥 FAIL NAMEID #10 contains symbols that should be replaced by '(c)'. [code: unwanted-chars]

🔥 FAIL: Checking OS/2 usWeightClass.

com.google.fonts/check/usweightclass

--- Rationale ---

Google Fonts expects variable fonts, static ttfs and static otfs to have
differing OS/2 usWeightClass values.

For Variable Fonts, Thin-Black must be 100-900
For static ttfs, Thin-Black can be 100-900 or 250-900
For static otfs, Thin-Black must be 250-900

If static otfs are set lower than 250, text may appear blurry in legacy Windows
applications.

Glyphsapp users can change the usWeightClass value of an instance by adding a
'weightClass' customParameter.

🔥 FAIL OS/2 usWeightClass is '400' when it should be '100'. [code: bad-value]

🔥 FAIL: Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?

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]

🔥 FAIL: Copyright notices match canonical pattern in fonts

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:
"\2512011 by Robert E. Leuschke. All rights reserved." [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:
"\2512011 by Robert E. Leuschke. All rights reserved." [code: bad-notice-format]

🔥 FAIL: Check name table: FONT_SUBFAMILY_NAME entries.

com.google.fonts/check/name/subfamilyname
🔥 FAIL SUBFAMILY_NAME for Mac "Regular" must be "Thin" [code: bad-familyname]

🔥 FAIL: Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.

com.google.fonts/check/name/typographicsubfamilyname
🔥 FAIL TYPOGRAPHIC_SUBFAMILY_NAME for Win is missing. It must be "Thin". [code: missing-typo-win]

🔥 FAIL: Check that variable fonts have an HVAR table.

com.google.fonts/check/varfont/has_HVAR

--- Rationale ---

Not having a HVAR table can lead to costly text-layout operations on some
platforms, which we want to avoid.

So, all variable fonts on the Google Fonts collection should have an HVAR with
valid values.

More info on the HVAR table can be found at:
https://docs.microsoft.com/en-us/typography/opentype/spec
/otvaroverview#variation-data-tables-and-miscellaneous-requirements

🔥 FAIL All variable fonts on the Google Fonts collection must have a properly set HVAR table in order to avoid costly text-layout operations on certain platforms. [code: lacks-HVAR]

🔥 FAIL: Font enables smart dropout control in "prep" table instructions?

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]

🔥 FAIL: Name table entries should not contain line-breaks.

com.google.fonts/check/name/line_breaks

--- Rationale ---

There are some entries on the name table that may include more than one line of
text. The Google Fonts team, though, prefers to keep the name table entries
short and simple without line breaks.

For instance, some designers like to include the full text of a font license in
the "copyright notice" entry, but for the GFonts collection this entry should
only mention year, author and other basic info in a manner enforced by
com.google.fonts/check/font_copyright

🔥 FAIL Name entry LICENSE_DESCRIPTION on platform MACINTOSH contains a line-break. [code: line-break]
🔥 FAIL Name entry LICENSE_DESCRIPTION on platform WINDOWS contains a line-break. [code: line-break]

🔥 FAIL: Check variable font instances have correct coordinate values

com.google.fonts/check/varfont_instance_coordinates
🔥 FAIL Instance "Light" wght value is "200.0". It should be "300.0" [code: bad-coordinate]
🔥 FAIL Instance "Book" wght value is "300.0". It should be "400.0" [code: bad-coordinate]
🔥 FAIL Further info can be found in our spec https://github.com/googlefonts/gf-docs/tree/master/Spec#axes

🔥 FAIL: Check variable font instances have correct names

com.google.fonts/check/varfont_instance_names
🔥 FAIL Following instances are not supported:
- Book

Further info can be found in our spec https://github.com/googlefonts/gf-docs/tree/master/Spec#fvar-instances [code: bad-instance-names]

🔥 FAIL: Validate STAT particle names and values match the fallback names in GFAxisRegistry.

com.google.fonts/check/STAT/gf-axisregistry

--- Rationale ---

Check that particle names and values on STAT table match the fallback names in
each axis entry at the Google Fonts Axis Registry, available at
https://github.com/google/fonts/tree/master/axisregistry

🔥 FAIL Axis Value for 'wght':'Light' is expected to be '300.0' but this font has 'Light'='200.0'. [code: bad-coordinate]
🔥 FAIL On the font variation axis 'wght', the name 'Book' is not among the expected ones (Thin, ExtraLight, Light, Regular, Medium, SemiBold, Bold, ExtraBold, Black) according to the Google Fonts Axis Registry. [code: invalid-name]
🔥 FAIL On the font variation axis 'ital', the name 'Regular' is not among the expected ones (Roman, Italic) according to the Google Fonts Axis Registry. [code: invalid-name]

🔥 FAIL: Ensure variable fonts include an avar table.

com.google.fonts/check/mandatory_avar_table

--- Rationale ---

All high quality variable fonts include an avar table to correctly define axes
progression rates.

For example, a weight axis from 0% to 100% doesn't map directly to 100 to 1000,
because a 10% progression from 0% may be too much to define the 200, while 90%
may be too little to define the 900.

🔥 FAIL This variable font does not have an avar table. [code: missing-avar]

🔥 FAIL: Whitespace glyphs have ink?

com.google.fonts/check/whitespace_ink
🔥 FAIL Glyph "uni00A0" has ink. It needs to be replaced by an empty glyph. [code: has-ink]

🔥 FAIL: Space and non-breaking space have the same width?

com.google.fonts/check/whitespace_widths
🔥 FAIL Space and non-breaking space have differing width: The space glyph named space is 241 font units wide, non-breaking space named (uni00A0) is 300 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]

🔥 FAIL: Check glyphs do not have components which are themselves components.

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:
- uni0162
- uni0163
- napostrophe
- uni1EAE
- uni1EB6
- uni1EB0
- uni1EB2
- uni1EB4
- uni1EA4
- uni1EAC and 82 more. [code: found-nested-components]

⚠ WARN: Are there caret positions declared for every ligature?

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

--- 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 + l
- l + i
- i + l
- l + t
[code: lacks-kern-info]

⚠ WARN: Font contains '.notdef' as its first glyph?

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]

[23] GenosItalicGX.ttf