Fontbakery Technical Report

If you think a check is flawed or have an idea for a check, please file an issue at https://github.com/fonttools/fontbakery/issues and remember to include a pointer to the repo and branch you're checking.

Summary

💥 ERROR 🔥 FAIL ⚠️ WARN ⏩ SKIP ℹ️ INFO ✅ PASS
0 8 17 61 8 147
0% 4% 9% 32% 4% 78%

Note: The following loglevels were omitted in this report: SKIP, INFO, PASS, DEBUG

Meaning of check results:

If you get ERRORs, please help us improve the tool by reporting them at our issue tracker.

(but other kinds of bug reports and/or feature requests are also always welcome, of course!)

FontBakery version: 0.9.2

Section: Google Fonts

🔥🔥🔥🔥⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️

Check Google Fonts glyph coverage.

Check ID: <FontBakeryCheck:com.google.fonts/check/glyph_coverage>
🔥 RozhaOne-Regular.ttf
  • 🔥 FAIL

    Missing required codepoints:

    - 0x0308 (COMBINING DIAERESIS)
    
    
    - 0x0300 (COMBINING GRAVE ACCENT)
    
    
    - 0x0301 (COMBINING ACUTE ACCENT)
    
    
    - 0x030B (COMBINING DOUBLE ACUTE ACCENT)
    
    
    - 0x0304 (COMBINING MACRON)
    
    
    - 0x1E9E (LATIN CAPITAL LETTER SHARP S)
    
    
    - 0x021A (LATIN CAPITAL LETTER T WITH COMMA BELOW)
    
    
    - 0x0237 (LATIN SMALL LETTER DOTLESS J)
    
    
    - 0x021B (LATIN SMALL LETTER T WITH COMMA BELOW)
    
    
    - 0x00AA (FEMININE ORDINAL INDICATOR)
    
    
    - 0x00BA (MASCULINE ORDINAL INDICATOR)
    
    
    - 0x0307 (COMBINING DOT ABOVE)
    
    
    - 0x0302 (COMBINING CIRCUMFLEX ACCENT)
    
    
    - 0x030C (COMBINING CARON)
    
    
    - 0x0306 (COMBINING BREVE)
    
    
    - 0x030A (COMBINING RING ABOVE)
    
    
    - 0x0303 (COMBINING TILDE)
    
    
    - 0x0312 (COMBINING TURNED COMMA ABOVE)
    
    
    - 0x0326 (COMBINING COMMA BELOW)
    
    
    - 0x0327 (COMBINING CEDILLA)
    
    
    - 0x0328 (COMBINING OGONEK)
    

    [code: missing-codepoints]

Check for codepoints not covered by METADATA subsets.

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/unreachable_subsetting>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    The following codepoints supported by the font are not covered by any subsets defined in the font's metadata file, and will never be served. You can solve this by either manually adding additional subset declarations to METADATA.pb, or by editing the glyphset definitions.

    • U+02C7 CARON: try adding one of: tifinagh, canadian-aboriginal
    • U+02D8 BREVE: try adding canadian-aboriginal
    • U+02D9 DOT ABOVE: try adding canadian-aboriginal
    • U+02DB OGONEK: try adding canadian-aboriginal
    • U+02DD DOUBLE ACUTE ACCENT: not included in any glyphset definition
    • U+2021 DOUBLE DAGGER: not included in any glyphset definition
    • U+2030 PER MILLE SIGN: not included in any glyphset definition
    • U+2070 SUPERSCRIPT ZERO: not included in any glyphset definition
    • U+2126 OHM SIGN: not included in any glyphset definition
    • U+212E ESTIMATED SYMBOL: not included in any glyphset definition
    • U+2202 PARTIAL DIFFERENTIAL: not included in any glyphset definition
    • U+2206 INCREMENT: not included in any glyphset definition
    • U+220F N-ARY PRODUCT: not included in any glyphset definition
    • U+2211 N-ARY SUMMATION: not included in any glyphset definition
    • U+221A SQUARE ROOT: not included in any glyphset definition
    • U+221E INFINITY: not included in any glyphset definition
    • U+2248 ALMOST EQUAL TO: not included in any glyphset definition
    • U+2260 NOT EQUAL TO: not included in any glyphset definition
    • U+2264 LESS-THAN OR EQUAL TO: not included in any glyphset definition
    • U+2265 GREATER-THAN OR EQUAL TO: not included in any glyphset definition
    • U+25CA LOZENGE: not included in any glyphset definition
    • U+F6C3 : not included in any glyphset definition
    • U+FB01 LATIN SMALL LIGATURE FI: not included in any glyphset definition
    • U+FB02 LATIN SMALL LIGATURE FL: not included in any glyphset definition

    Or you can add the above codepoints to one of the subsets supported by the font: devanagari, latin, latin-ext, menu [code: unreachable-subsetting]

Check license file has good copyright string.

Check ID: <FontBakeryCheck:com.google.fonts/check/license/OFL_copyright>
🔥 RozhaOne-Regular.ttf
  • 🔥 FAIL

    First line in license file is:

    "copyright (c) 2014, indian type foundry (info@indiantypefoundry.com)."

    which does not match the expected format, similar to:

    "Copyright 2022 The Familyname Project Authors (git url)" [code: bad-format]

Check copyright namerecords match license file.

Check ID: <FontBakeryCheck:com.google.fonts/check/name/license>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]

  • ⚠️ WARN

    Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]

  • ⚠️ WARN

    For now we're still accepting http URLs, but you should consider using https instead. [code: http]

License URL matches License text on name table?

Check ID: <FontBakeryCheck:com.google.fonts/check/name/license_url>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]

  • ⚠️ WARN

    Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]

  • ⚠️ WARN

    Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]

  • ⚠️ WARN

    Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]

  • ⚠️ WARN

    Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]

  • ⚠️ WARN

    Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=14] [code: http-in-license-info]

  • ⚠️ WARN

    Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=14] [code: http-in-license-info]

  • ⚠️ WARN

    For now we're still accepting http URLs, but you should consider using https instead. [code: http]

Font has old ttfautohint applied?

Check ID: <FontBakeryCheck:com.google.fonts/check/old_ttfautohint>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    ttfautohint used in font = 1.1; latest = 1.8.4; Need to re-run with the newer version! [code: old-ttfa]

Copyright notices match canonical pattern in METADATA.pb

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>
🔥 RozhaOne-Regular.ttf
  • 🔥 FAIL

    METADATA.pb: Copyright notices should match a pattern similar to: "Copyright 2020 The Familyname Project Authors (git url)" But instead we have got: "copyright (c) 2014 indian type foundry (info@indiantypefoundry.com)" [code: bad-notice-format]

Copyright notices match canonical pattern in fonts

Check ID: <FontBakeryCheck:com.google.fonts/check/font_copyright>
🔥 RozhaOne-Regular.ttf
  • 🔥 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 (c) 2014 Indian Type Foundry (info@indiantypefoundry.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: "Copyright (c) 2014 Indian Type Foundry (info@indiantypefoundry.com)" [code: bad-notice-format]

Are there caret positions declared for every ligature?

Check ID: <FontBakeryCheck:com.google.fonts/check/ligature_carets>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]

A static fonts directory with at least two fonts must accompany variable fonts

Check ID: <FontBakeryCheck:com.google.fonts/check/repo/vf_has_static_fonts>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]

On a family update, the DESCRIPTION.en_us.html file should ideally also be updated.

Check ID: <FontBakeryCheck:com.google.fonts/check/description/family_update>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    The DESCRIPTION.en_us.html file in this family has not changed in comparison to the latest font release on the google/fonts github repo. Please consider mentioning note-worthy improvements made to the family recently. [code: description-not-updated]

Ensure fonts have ScriptLangTags declared on the 'meta' table.

Check ID: <FontBakeryCheck:com.google.fonts/check/meta/script_lang_tags>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    This font file does not have a 'meta' table. [code: lacks-meta-table]

Ensure fonts do not contain any pre-production tables.

Check ID: <FontBakeryCheck:com.google.fonts/check/no_debugging_tables>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    This font file contains the following pre-production tables: FFTM [code: has-debugging-tables]

Section: Universal

🔥🔥🔥⚠️⚠️⚠️⏩⏩⏩⏩⏩ℹ️ℹ️

Font has **proper** whitespace glyph names?

Check ID: <FontBakeryCheck:com.google.fonts/check/whitespace_glyphnames>
🔥 RozhaOne-Regular.ttf
  • 🔥 FAIL

    Glyph 0x00A0 is called "nbsp": Change to "uni00A0" [code: non-compliant-00a0]

Are there unwanted tables?

Check ID: <FontBakeryCheck:com.google.fonts/check/unwanted_tables>
🔥 RozhaOne-Regular.ttf
  • 🔥 FAIL

    The following unwanted font tables were found:

    • FFTM - Table contains redundant FontForge timestamp info

    They can be removed with the 'fix-unwanted-tables' script provided by gftools. [code: unwanted-tables]

Check font contains no unreachable glyphs

Check ID: <FontBakeryCheck:com.google.fonts/check/unreachable_glyphs>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    The following glyphs could not be reached by codepoint or substitution rules:

    - acute.cap
    
    - breve.cap
    
    - caron.cap
    
    - cedilla.cap
    
    - circumflex.cap
    
    - dieresis.cap
    
    - dotaccent.cap
    
    - dvSH_VA.aSimp
    
    - grave.cap
    
    - hungarumlaut.cap
    
    - i.alt
    
    - itfLogo
    
    - itfStar
    
    - j.alt
    
    - macron.cap
    
    - nonmarkingreturn
    
    - ogonek.cap
    
    - ring.cap
    
    - tilde.cap
    
    - uni0915094D0930.aTrad
    
    - uni091B094D0930094D092F
    
    - uni0924094D0930094D0915.aTrad
    
    - uni093F.a02
    
    - uni093F.a28
    
    - uni093F.a29
    
    - uni093F.a31
    
    - uni094A0902
    
    - uni094D0928.post
    
    - uni094D092F.post
    
    - uni094D0930.post
    

    [code: unreachable-glyphs]

Check if each glyph has the recommended amount of contours.

Check ID: <FontBakeryCheck:com.google.fonts/check/contour_count>
🔥 RozhaOne-Regular.ttf
  • 🔥 FAIL

    The following glyphs have no contours even though they were expected to have some:

    - Glyph name: estimated	Expected: 2
    
    - Glyph name: estimated	Expected: 2
    

    [code: no-contour]

  • ⚠️ 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: Q	Contours detected: 1	Expected: 2
    
    - Glyph name: eth	Contours detected: 1	Expected: 2
    
    - Glyph name: uni090B	Contours detected: 2	Expected: 1
    
    - Glyph name: uni0910	Contours detected: 2	Expected: 1
    
    - Glyph name: uni0913	Contours detected: 2	Expected: 1
    
    - Glyph name: uni0914	Contours detected: 3	Expected: 1
    
    - Glyph name: uni0916	Contours detected: 2	Expected: 1 or 3
    
    - Glyph name: uni092D	Contours detected: 2	Expected: 1
    
    - Glyph name: uni092E	Contours detected: 3	Expected: 2
    
    - Glyph name: uni0936	Contours detected: 1	Expected: 2
    
    - Glyph name: uni0948	Contours detected: 2	Expected: 1
    
    - Glyph name: uni094B	Contours detected: 2	Expected: 1
    
    - Glyph name: uni094C	Contours detected: 3	Expected: 1
    
    - Glyph name: uni0950	Contours detected: 4	Expected: 3
    
    - Glyph name: uni0916093C	Contours detected: 3	Expected: 2 or 4
    
    - Glyph name: partialdiff	Contours detected: 1	Expected: 2
    
    - Glyph name: Q	Contours detected: 1	Expected: 2
    
    - Glyph name: eth	Contours detected: 1	Expected: 2
    
    - Glyph name: fi	Contours detected: 1	Expected: 3
    
    - Glyph name: fl	Contours detected: 1	Expected: 2
    
    - Glyph name: partialdiff	Contours detected: 1	Expected: 2
    
    - Glyph name: uni090B	Contours detected: 2	Expected: 1
    
    - Glyph name: uni0910	Contours detected: 2	Expected: 1
    
    - Glyph name: uni0913	Contours detected: 2	Expected: 1
    
    - Glyph name: uni0914	Contours detected: 3	Expected: 1
    
    - Glyph name: uni0916	Contours detected: 2	Expected: 1 or 3
    
    - Glyph name: uni092D	Contours detected: 2	Expected: 1
    
    - Glyph name: uni092E	Contours detected: 3	Expected: 2
    
    - Glyph name: uni0936	Contours detected: 1	Expected: 2
    
    - Glyph name: uni0948	Contours detected: 2	Expected: 1
    
    - Glyph name: uni094B	Contours detected: 2	Expected: 1
    
    - Glyph name: uni094C	Contours detected: 3	Expected: 1
    
    - Glyph name: uni0950	Contours detected: 4	Expected: 3
    

    [code: contour-count]

Check math signs have the same width.

Check ID: <FontBakeryCheck:com.google.fonts/check/math_signs_width>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    The most common width is 483 among a set of 4 math glyphs. The following math glyphs have a different width, though:

    Width = 485: plus, divide

    Width = 465: approxequal, equal

    Width = 505: plusminus, notequal, logicalnot, minus

    Width = 395: multiply [code: width-outliers]

Check accent of Lcaron, dcaron, lcaron, tcaron (derived from com.google.fonts/check/alt_caron)

Check ID: <FontBakeryCheck:com.google.fonts/check/alt_caron:googlefonts>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    dcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]

  • ⚠️ WARN

    Lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]

  • ⚠️ WARN

    lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]

  • ⚠️ WARN

    tcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]

Section: fontbakery.profiles.os2

⚠️⏩

Check if OS/2 xAvgCharWidth is correct.

Check ID: <FontBakeryCheck:com.google.fonts/check/xavgcharwidth>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    OS/2 xAvgCharWidth is 543 but it should be 710 which corresponds to the average of the widths of all glyphs in the font. [code: xAvgCharWidth-wrong]

Section: fontbakery.profiles.dsig

⚠️

Does the font have a DSIG table?

Check ID: <FontBakeryCheck:com.google.fonts/check/dsig>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    This font has a digital signature (DSIG table) which is only required - even if only a placeholder - on old programs like MS Office 2013 in order to work properly. The current recommendation is to completely remove the DSIG table. [code: found-DSIG]

Section: fontbakery.profiles.gdef

⚠️⚠️

Check glyphs in mark glyph class are non-spacing.

Check ID: <FontBakeryCheck:com.google.fonts/check/gdef_spacing_marks>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    The following spacing glyphs may be in the GDEF mark glyph class by mistake: uni0946 (U+0946) [code: spacing-mark-glyphs]

Check mark characters are in GDEF mark glyph class.

Check ID: <FontBakeryCheck:com.google.fonts/check/gdef_mark_chars>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    The following mark characters could be in the GDEF mark glyph class: uni093C (U+093C), uni0951 (U+0951), uni0952 (U+0952), uni0953 (U+0953) and uni0954 (U+0954) [code: mark-chars]

Section: fontbakery.profiles.gpos

⚠️

Does GPOS table have kerning information? This check skips monospaced fonts as defined by post.isFixedPitch value

Check ID: <FontBakeryCheck:com.google.fonts/check/gpos_kerning_info>
⚠️ RozhaOne-Regular.ttf
  • ⚠️ WARN

    GPOS table lacks kerning information. [code: lacks-kern-info]

Section: Shaping Checks

🔥⏩⏩⏩⏩

Ensure dotted circle glyph is present and can attach marks.

Check ID: <FontBakeryCheck:com.google.fonts/check/dotted_circle>
🔥 RozhaOne-Regular.ttf
  • 🔥 FAIL

    The following glyphs could not be attached to the dotted circle glyph:

    - uni0901
    
    - uni0902
    
    - uni0941
    
    - uni0942
    
    - uni0943
    
    - uni0944
    
    - uni0945
    
    - uni0947
    
    - uni0948
    
    - uni094D [code: unattached-dotted-circle-marks]