search

TiroTypeworks / Indigo

32 stars 3 forks source link

Tiro Bangla - FB report #4

Closed vv-monsalve closed 2 years ago

vv-monsalve commented 2 years ago

Hi @tiroj, this is the report for the v1.51 Tiro Banlga

The Warns reported seem to be the expected.

Fontbakery report

Fontbakery version: 0.8.7

[10] TiroBangla-Italic.ttf
⚠ WARN: Ensure Stylistic Sets have description.
* [com.google.fonts/check/stylisticset_description](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/stylisticset_description) 
--- Rationale ---
Stylistic sets should provide description text. Programs such as InDesign,
TextEdit and Inkscape use that info to display to the users so that they know
what a given stylistic set offers.
* ⚠ **WARN** The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description] * ⚠ **WARN** The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description] * ⚠ **WARN** The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description] * ⚠ **WARN** The stylistic set ss05 lacks a description string on the 'name' table. [code: missing-description] * ⚠ **WARN** The stylistic set ss19 lacks a description string on the 'name' table. [code: missing-description] * ⚠ **WARN** The stylistic set ss20 lacks a description string on the 'name' table. [code: missing-description]
⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table.
* [com.google.fonts/check/meta/script_lang_tags](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/meta/script_lang_tags) 
--- Rationale ---
The OpenType 'meta' table originated at Apple. Microsoft added it to OT with
just two DataMap records:
- dlng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font is designed for
- slng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font supports
The slng structure is intended to describe which languages and scripts the font
overall supports. For example, a Traditional Chinese font that also contains
Latin characters, can indicate Hant,Latn, showing that it supports Hant, the
Traditional Chinese variant of the Hani script, and it also supports the Latn
script
The dlng structure is far more interesting. A font may contain various glyphs,
but only a particular subset of the glyphs may be truly "leading" in the design,
while other glyphs may have been included for technical reasons. Such a
Traditional Chinese font could only list Hant there, showing that it’s designed
for Traditional Chinese, but the font would omit Latn, because the developers
don’t think the font is really recommended for purely Latin-script use.
The tags used in the structures can comprise just script, or also language and
script. For example, if a font has Bulgarian Cyrillic alternates in the locl
feature for the cyrl BGR OT languagesystem, it could also indicate in dlng
explicitly that it supports bul-Cyrl. (Note that the scripts and languages in
meta use the ISO language and script codes, not the OpenType ones).
This check ensures that the font has the meta table containing the slng and dlng
structures.
All families in the Google Fonts collection should contain the 'meta' table.
Windows 10 already uses it when deciding on which fonts to fall back to. The
Google Fonts API and also other environments could use the data for smarter
filtering. Most importantly, those entries should be added to the Noto fonts.
In the font making process, some environments store this data in external files
already. But the meta table provides a convenient way to store this inside the
font file, so some tools may add the data, and unrelated tools may read this
data. This makes the solution much more portable and universal.
* ⚠ **WARN** This font file does not have a 'meta' table. [code: lacks-meta-table]
⚠ WARN: Font has **proper** whitespace glyph names?
* [com.google.fonts/check/whitespace_glyphnames](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/universal.html#com.google.fonts/check/whitespace_glyphnames) 
--- Rationale ---
This check enforces adherence to recommended whitespace (codepoints 0020 and
00A0) glyph names according to the Adobe Glyph List.
* ⚠ **WARN** Glyph 0x00A0 is called "nbspace": Change to "uni00A0" [code: not-recommended-00a0]
⚠ WARN: Glyph names are all valid?
* [com.google.fonts/check/valid_glyphnames](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/universal.html#com.google.fonts/check/valid_glyphnames) 
--- Rationale ---
Microsoft's recommendations for OpenType Fonts states the following:
'NOTE: The PostScript glyph name must be no longer than 31 characters, include
only uppercase or lowercase English letters, European digits, the period or the
underscore, i.e. from the set [A-Za-z0-9_.] and should start with a letter,
except the special glyph name ".notdef" which starts with a period.'
https://docs.microsoft.com/en-us/typography/opentype/spec/recom#post-table
In practice, though, particularly in modern environments, glyph names can be as
long as 63 characters.
According to the "Adobe Glyph List Specification" available at:
https://github.com/adobe-type-tools/agl-specification
* ⚠ **WARN** The following glyph names may be too long for some legacy systems which may expect a maximum 31-char length limit: L_ringbelowcomb_macroncomb_acutecomb, R_ringbelowcomb_macroncomb_acutecomb, l_ringbelowcomb_macroncomb_acutecomb, r_ringbelowcomb_macroncomb_acutecomb, L_ringbelowcomb_macroncomb_acutecomb.sc, R_ringbelowcomb_macroncomb_acutecomb.sc, G_macronbelowcomb_H_macronbelowcomb and G_macronbelowcomb_H_macronbelowcomb.sc [code: legacy-long-names]
⚠ WARN: Check font contains no unreachable glyphs
* [com.google.fonts/check/unreachable_glyphs](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/universal.html#com.google.fonts/check/unreachable_glyphs) 
--- Rationale ---
Glyphs are either accessible directly through Unicode codepoints or through
substitution rules. Any glyphs not accessible by either of these means are
redundant and serve only to increase the font's file size.
* ⚠ **WARN** The following glyphs could not be reached by codepoint or substitution rules: - dUdattaHeadline - And bCandrabindu.headline [code: unreachable-glyphs]
⚠ 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/universal.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 font has a 'Soft Hyphen' character (codepoint 0x00AD) which is supposed to be zero-width and invisible, and is used to mark a hyphenation possibility within a word in the absence of or overriding dictionary hyphenation. It is mostly an obsolete mechanism now, and the character is only included in fonts for legacy codepage coverage. [code: softhyphen] * ⚠ **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: rupee Contours detected: 1 Expected: 3 [code: contour-count]
⚠ WARN: Checking Vertical Metric Linegaps.
* [com.google.fonts/check/linegaps](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/hhea.html#com.google.fonts/check/linegaps) * ⚠ **WARN** hhea lineGap is not equal to 0. [code: hhea]
⚠ 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: acutecomb (U+0301), brevebelowcomb (U+032E), brevecomb (U+0306), candrabinducomb (U+0310), caroncomb (U+030C), cedillacomb (U+0327), circumflexcomb (U+0302), commaaccentcomb (U+0326), dieresisbelowcomb (U+0324), dieresiscomb (U+0308), dotaccentcomb (U+0307), dotbelowcomb (U+0323), gravecomb (U+0300), macronbelowcomb (U+0331), macroncomb (U+0304), macrondblbelowcomb (U+035F), ringbelowcomb (U+0325), ringcomb (U+030A) and tildecomb (U+0303) [code: mark-chars]
⚠ WARN: Check GDEF mark glyph class doesn't have characters that are not marks.
* [com.google.fonts/check/gdef_non_mark_chars](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/gdef.html#com.google.fonts/check/gdef_non_mark_chars) 
--- Rationale ---
Glyphs in the GDEF mark glyph class become non-spacing and may be repositioned
if they have mark anchors.
Only combining mark glyphs should be in that class. Any non-mark glyph must not
be in that class, in particular spacing glyphs.
* ⚠ **WARN** The following non-mark characters should not be in the GDEF mark glyph class: U+0982, U+0983 and U+09FC [code: non-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 check looks for consecutive line segments which have the same angle. This
normally happens if an outline point has been added by accident.
This check is not run for variable fonts, as they may legitimately have colinear
vectors.
* ⚠ **WARN** The following glyphs have colinear vectors: * b (U+0062): L<<250.0,565.0>--<221.0,424.0>> -> L<<221.0,424.0>--<206.0,364.0>> * bVocalicR (U+098B): L<<619.0,404.0>--<620.0,411.0>> -> L<<620.0,411.0>--<661.0,620.0>> * bVocalicRr (U+09E0): L<<619.0,404.0>--<620.0,411.0>> -> L<<620.0,411.0>--<661.0,620.0>> * h (U+0068): L<<250.0,565.0>--<218.0,413.0>> -> L<<218.0,413.0>--<202.0,345.0>> * hdotbelow (U+1E25): L<<255.0,565.0>--<223.0,413.0>> -> L<<223.0,413.0>--<207.0,345.0>> * hlinebelow (U+1E96): L<<255.0,565.0>--<223.0,413.0>> -> L<<223.0,413.0>--<207.0,345.0>> * k (U+006B): L<<179.0,207.0>--<178.0,203.0>> -> L<<178.0,203.0>--<136.0,0.0>> * k (U+006B): L<<252.0,565.0>--<221.0,415.0>> -> L<<221.0,415.0>--<202.0,337.0>> * kdotbelow (U+1E33): L<<182.0,207.0>--<181.0,203.0>> -> L<<181.0,203.0>--<139.0,0.0>> * kdotbelow (U+1E33): L<<255.0,565.0>--<224.0,415.0>> -> L<<224.0,415.0>--<205.0,337.0>> * klinebelow (U+1E35): L<<182.0,207.0>--<181.0,203.0>> -> L<<181.0,203.0>--<139.0,0.0>> * klinebelow (U+1E35): L<<255.0,565.0>--<224.0,415.0>> -> L<<224.0,415.0>--<205.0,337.0>> * n (U+006E): L<<193.0,190.0>--<191.0,182.0>> -> L<<191.0,182.0>--<149.0,0.0>> * ncommaaccent (U+0146): L<<193.0,190.0>--<191.0,182.0>> -> L<<191.0,182.0>--<149.0,0.0>> * ndotaccent (U+1E45): L<<193.0,190.0>--<191.0,182.0>> -> L<<191.0,182.0>--<149.0,0.0>> * ndotbelow (U+1E47): L<<193.0,190.0>--<191.0,182.0>> -> L<<191.0,182.0>--<149.0,0.0>> * nmacronbelow (U+1E49): L<<193.0,190.0>--<191.0,182.0>> -> L<<191.0,182.0>--<149.0,0.0>> * ntilde (U+00F1): L<<193.0,190.0>--<191.0,182.0>> -> L<<191.0,182.0>--<149.0,0.0>> * q (U+0071): L<<355.0,297.0>--<358.0,309.0>> -> L<<358.0,309.0>--<378.0,393.0>> and thorn (U+00FE): L<<256.0,565.0>--<226.0,420.0>> -> L<<226.0,420.0>--<214.0,365.0>> [code: found-colinear-vectors]

[10] TiroBangla-Regular.ttf
⚠ WARN: Ensure Stylistic Sets have description.
* [com.google.fonts/check/stylisticset_description](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/stylisticset_description) 
--- Rationale ---
Stylistic sets should provide description text. Programs such as InDesign,
TextEdit and Inkscape use that info to display to the users so that they know
what a given stylistic set offers.
* ⚠ **WARN** The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description] * ⚠ **WARN** The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description] * ⚠ **WARN** The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description] * ⚠ **WARN** The stylistic set ss05 lacks a description string on the 'name' table. [code: missing-description] * ⚠ **WARN** The stylistic set ss19 lacks a description string on the 'name' table. [code: missing-description] * ⚠ **WARN** The stylistic set ss20 lacks a description string on the 'name' table. [code: missing-description]
⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table.
* [com.google.fonts/check/meta/script_lang_tags](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/meta/script_lang_tags) 
--- Rationale ---
The OpenType 'meta' table originated at Apple. Microsoft added it to OT with
just two DataMap records:
- dlng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font is designed for
- slng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font supports
The slng structure is intended to describe which languages and scripts the font
overall supports. For example, a Traditional Chinese font that also contains
Latin characters, can indicate Hant,Latn, showing that it supports Hant, the
Traditional Chinese variant of the Hani script, and it also supports the Latn
script
The dlng structure is far more interesting. A font may contain various glyphs,
but only a particular subset of the glyphs may be truly "leading" in the design,
while other glyphs may have been included for technical reasons. Such a
Traditional Chinese font could only list Hant there, showing that it’s designed
for Traditional Chinese, but the font would omit Latn, because the developers
don’t think the font is really recommended for purely Latin-script use.
The tags used in the structures can comprise just script, or also language and
script. For example, if a font has Bulgarian Cyrillic alternates in the locl
feature for the cyrl BGR OT languagesystem, it could also indicate in dlng
explicitly that it supports bul-Cyrl. (Note that the scripts and languages in
meta use the ISO language and script codes, not the OpenType ones).
This check ensures that the font has the meta table containing the slng and dlng
structures.
All families in the Google Fonts collection should contain the 'meta' table.
Windows 10 already uses it when deciding on which fonts to fall back to. The
Google Fonts API and also other environments could use the data for smarter
filtering. Most importantly, those entries should be added to the Noto fonts.
In the font making process, some environments store this data in external files
already. But the meta table provides a convenient way to store this inside the
font file, so some tools may add the data, and unrelated tools may read this
data. This makes the solution much more portable and universal.
* ⚠ **WARN** This font file does not have a 'meta' table. [code: lacks-meta-table]
⚠ WARN: Font has **proper** whitespace glyph names?
* [com.google.fonts/check/whitespace_glyphnames](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/universal.html#com.google.fonts/check/whitespace_glyphnames) 
--- Rationale ---
This check enforces adherence to recommended whitespace (codepoints 0020 and
00A0) glyph names according to the Adobe Glyph List.
* ⚠ **WARN** Glyph 0x00A0 is called "nbspace": Change to "uni00A0" [code: not-recommended-00a0]
⚠ WARN: Glyph names are all valid?
* [com.google.fonts/check/valid_glyphnames](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/universal.html#com.google.fonts/check/valid_glyphnames) 
--- Rationale ---
Microsoft's recommendations for OpenType Fonts states the following:
'NOTE: The PostScript glyph name must be no longer than 31 characters, include
only uppercase or lowercase English letters, European digits, the period or the
underscore, i.e. from the set [A-Za-z0-9_.] and should start with a letter,
except the special glyph name ".notdef" which starts with a period.'
https://docs.microsoft.com/en-us/typography/opentype/spec/recom#post-table
In practice, though, particularly in modern environments, glyph names can be as
long as 63 characters.
According to the "Adobe Glyph List Specification" available at:
https://github.com/adobe-type-tools/agl-specification
* ⚠ **WARN** The following glyph names may be too long for some legacy systems which may expect a maximum 31-char length limit: L_ringbelowcomb_macroncomb_acutecomb, R_ringbelowcomb_macroncomb_acutecomb, l_ringbelowcomb_macroncomb_acutecomb, r_ringbelowcomb_macroncomb_acutecomb, L_ringbelowcomb_macroncomb_acutecomb.sc, R_ringbelowcomb_macroncomb_acutecomb.sc, G_macronbelowcomb_H_macronbelowcomb and G_macronbelowcomb_H_macronbelowcomb.sc [code: legacy-long-names]
⚠ WARN: Check font contains no unreachable glyphs
* [com.google.fonts/check/unreachable_glyphs](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/universal.html#com.google.fonts/check/unreachable_glyphs) 
--- Rationale ---
Glyphs are either accessible directly through Unicode codepoints or through
substitution rules. Any glyphs not accessible by either of these means are
redundant and serve only to increase the font's file size.
* ⚠ **WARN** The following glyphs could not be reached by codepoint or substitution rules: - dUdattaHeadline - And bCandrabindu.headline [code: unreachable-glyphs]
⚠ 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/universal.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 font has a 'Soft Hyphen' character (codepoint 0x00AD) which is supposed to be zero-width and invisible, and is used to mark a hyphenation possibility within a word in the absence of or overriding dictionary hyphenation. It is mostly an obsolete mechanism now, and the character is only included in fonts for legacy codepage coverage. [code: softhyphen] * ⚠ **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: rupee Contours detected: 1 Expected: 3 [code: contour-count]
⚠ WARN: Checking Vertical Metric Linegaps.
* [com.google.fonts/check/linegaps](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/hhea.html#com.google.fonts/check/linegaps) * ⚠ **WARN** hhea lineGap is not equal to 0. [code: hhea]
⚠ 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: acutecomb (U+0301), brevebelowcomb (U+032E), brevecomb (U+0306), candrabinducomb (U+0310), caroncomb (U+030C), cedillacomb (U+0327), circumflexcomb (U+0302), commaaccentcomb (U+0326), dieresisbelowcomb (U+0324), dieresiscomb (U+0308), dotaccentcomb (U+0307), dotbelowcomb (U+0323), gravecomb (U+0300), macronbelowcomb (U+0331), macroncomb (U+0304), macrondblbelowcomb (U+035F), ringbelowcomb (U+0325), ringcomb (U+030A) and tildecomb (U+0303) [code: mark-chars]
⚠ WARN: Check GDEF mark glyph class doesn't have characters that are not marks.
* [com.google.fonts/check/gdef_non_mark_chars](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/gdef.html#com.google.fonts/check/gdef_non_mark_chars) 
--- Rationale ---
Glyphs in the GDEF mark glyph class become non-spacing and may be repositioned
if they have mark anchors.
Only combining mark glyphs should be in that class. Any non-mark glyph must not
be in that class, in particular spacing glyphs.
* ⚠ **WARN** The following non-mark characters should not be in the GDEF mark glyph class: U+0982, U+0983 and U+09FC [code: non-mark-chars]
⚠ 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 check 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 check is disabled for italic styles, which often contain nearly-upright
lines.
* ⚠ **WARN** The following glyphs have semi-vertical/semi-horizontal lines: * bAuMark (U+09D7): L<<95.0,10.0>--<97.0,552.0>> * bSignAu (U+09CC): L<<1224.0,10.0>--<1226.0,552.0>> * bSignI (U+09BF): L<<95.0,10.0>--<97.0,552.0>> * bSignIi (U+09C0): L<<95.0,10.0>--<97.0,552.0>> * fivesuperior (U+2075): L<<101.0,783.0>--<334.0,785.0>> and vAtikrama (U+1CF7): L<<92.0,-197.0>--<94.0,628.0>> [code: found-semi-vertical]

Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
0 0 20 218 15 177 0
0% 0% 5% 51% 3% 41% 0%

Note: The following loglevels were omitted in this report:

tiroj commented 2 years ago

v1.51

Warnings reviewed and confirmed as expected for this release: issues either features not implementable in current tool chain, by design, or harmless artifacts of outline merging.