Noto Sans SignWriting: Version 2.005; ttfautohint (v1.8.4.7-5d5b) added #6456

simoncozens · 2023-06-27T07:10:03Z

a31b2cc: [gftools-packager] Noto Sans SignWriting: Version 2.005; ttfautohint (v1.8.4.7-5d5b) added

Noto Sans SignWriting Version 2.005; ttfautohint (v1.8.4.7-5d5b) taken from the upstream repo https://github.com/notofonts/sign-writing.git at commit https://github.com/notofonts/sign-writing/commit/.

…(v1.8.4.7-5d5b) added * Noto Sans SignWriting Version 2.005; ttfautohint (v1.8.4.7-5d5b) taken from the upstream repo https://github.com/notofonts/sign-writing.git at commit https://github.com/notofonts/sign-writing/commit/.

github-actions · 2023-06-27T07:20:03Z

Fontbakery report

Fontbakery version: 0.8.13

[1] Family checks

ℹ INFO: Check axis ordering on the STAT table. (com.google.fonts/check/STAT/axis_order)

ℹ INFO From a total of 1 font files, 1 of them (100.00%) lack a STAT table.

And these are the most common STAT axis orderings:
[code: summary]

[22] NotoSansSignWriting-Regular.ttf

🔥 FAIL: DESCRIPTION.en_us.html must have more than 200 bytes. (com.google.fonts/check/description/min_length)

🔥 FAIL DESCRIPTION.en_us.html must have size larger than 200 bytes. [code: too-short]

🔥 FAIL: Check font follows the Google Fonts vertical metric schema (com.google.fonts/check/vertical_metrics)

🔥 FAIL The sum of hhea.ascender + abs(hhea.descender) + hhea.lineGap is 1002 when it should be at least 1200 [code: bad-hhea-range]

🔥 FAIL: Ensure soft_dotted characters lose their dot when combined with marks that replace the dot. (com.google.fonts/check/soft_dotted)

🔥 FAIL The dot of soft dotted characters used in orthographies must disappear in the following strings: į̀ į́ į̂ į̃ į̄ į̌

The dot of soft dotted characters should disappear in other cases, for example: į̆ į̇ į̈ į̊ į̋ į̒ į̦̀ į̦́ į̦̂ į̦̃ į̦̄ į̦̆ į̦̇ į̦̈ į̦̊ į̦̋ į̦̌ į̦̒ į̧̀ į̧́ [code: soft-dotted]

⚠ WARN: DESCRIPTION.en_us.html should end in a linebreak. (com.google.fonts/check/description/eof_linebreak)

⚠ WARN The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]

⚠ WARN: Check for codepoints not covered by METADATA subsets. (com.google.fonts/check/metadata/unreachable_subsetting)

⚠ 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: canadian-aboriginal, tifinagh, yi
U+02D8 BREVE: try adding one of: canadian-aboriginal, yi
U+02D9 DOT ABOVE: try adding one of: canadian-aboriginal, yi
U+02DB OGONEK: try adding one of: canadian-aboriginal, yi
U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: cherokee, math, coptic, tifinagh
U+0306 COMBINING BREVE: try adding one of: old-permic, tifinagh
U+0307 COMBINING DOT ABOVE: try adding one of: old-permic, tifinagh, coptic, malayalam, syriac, tai-le, math, canadian-aboriginal
U+030A COMBINING RING ABOVE: try adding syriac
U+030B COMBINING DOUBLE ACUTE ACCENT: try adding one of: cherokee, osage
U+030C COMBINING CARON: try adding one of: cherokee, tai-le
U+200C ZERO WIDTH NON-JOINER: try adding one of: tai-tham, manichaean, gunjala-gondi, limbu, hatran, sogdian, kannada, sharada, dogra, mahajani, warang-citi, grantha, avestan, tagalog, kayah-li, duployan, syloti-nagri, khmer, tai-le, batak, sinhala, hanifi-rohingya, kharoshthi, chakma, brahmi, devanagari, myanmar, nko, thaana, mongolian, buhid, tai-viet, telugu, saurashtra, malayalam, javanese, buginese, lepcha, phags-pa, tamil, sundanese, siddham, oriya, balinese, tibetan, bengali, gurmukhi, takri, tifinagh, tirhuta, new-tai-lue, cham, syriac, tagbanwa, meetei-mayek, rejang, thai, pahawh-hmong, psalter-pahlavi, gujarati, hanunoo, mandaic, modi, khudawadi, newa, khojki, yi, kaithi
U+25CC DOTTED CIRCLE: try adding one of: gunjala-gondi, kannada, syloti-nagri, batak, sinhala, hanifi-rohingya, chakma, brahmi, myanmar, bassa-vah, telugu, buhid, buginese, phags-pa, tamil, tirhuta, thai, adlam, mandaic, modi, masaram-gondi, mende-kikakui, sogdian, miao, grantha, soyombo, tai-le, zanabazar-square, mongolian, tai-viet, marchen, javanese, lepcha, math, siddham, balinese, tibetan, bengali, tifinagh, coptic, cham, syriac, meetei-mayek, rejang, symbols, newa, manichaean, limbu, bhaiksuki, hebrew, music, ahom, sharada, mahajani, tagalog, kayah-li, duployan, nko, thaana, sundanese, oriya, lao, gurmukhi, takri, pahawh-hmong, psalter-pahlavi, khojki, dogra, wancho, old-permic, caucasian-albanian, khmer, kharoshthi, devanagari, malayalam, elbasan, new-tai-lue, osage, tagbanwa, gujarati, hanunoo, khudawadi, yi, kaithi

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

⚠ WARN: Ensure files are not too large. (com.google.fonts/check/file_size)

⚠ WARN Font file is 7.5Mb; ideally it should be less than 1.0Mb [code: large-font]

⚠ WARN: Combined length of family and style must not exceed 27 characters. (com.google.fonts/check/name/family_and_style_max_length)

⚠ WARN The combined length of family and style exceeds 27 chars in the following 'WINDOWS' entries:
FONT_FAMILY_NAME = 'Noto Sans SignWriting' / SUBFAMILY_NAME = 'Regular'

Please take a look at the conversation at fonttools/fontbakery#2179 in order to understand the reasoning behind these name table records max-length criteria. [code: too-long]

⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts (com.google.fonts/check/repo/vf_has_static_fonts)

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

⚠ WARN: On a family update, the DESCRIPTION.en_us.html file should ideally also be updated. (com.google.fonts/check/description/family_update)

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

⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table. (com.google.fonts/check/meta/script_lang_tags)

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

⚠ WARN: Check font contains no unreachable glyphs (com.google.fonts/check/unreachable_glyphs)

⚠ WARN The following glyphs could not be reached by codepoint or substitution rules:
- nbspace
  [code: unreachable-glyphs]

⚠ WARN: Check if each glyph has the recommended amount of contours. (com.google.fonts/check/contour_count)

⚠ 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: aogonek	Contours detected: 3	Expected: 2

- Glyph name: uogonek	Contours detected: 2	Expected: 1

- Glyph name: aogonek	Contours detected: 3	Expected: 2 

- Glyph name: uogonek	Contours detected: 2	Expected: 1

[code: contour-count]

⚠ WARN: Check math signs have the same width. (com.google.fonts/check/math_signs_width)

⚠ WARN The most common width is 572 among a set of 6 math glyphs.
The following math glyphs have a different width, though:

Width = 322:
minus
[code: width-outliers]

⚠ WARN: Do any segments have colinear vectors? (com.google.fonts/check/outline_colinear_vectors)

⚠ WARN The following glyphs have colinear vectors:
- u1D881 (U+1D881): L<<677.0,319.0>--<672.0,310.0>> -> L<<672.0,310.0>--<502.0,16.0>>
- u1D9A6 (U+1D9A6): L<<471.0,327.0>--<454.0,345.0>> -> L<<454.0,345.0>--<427.0,373.0>>
- u1DA34 (U+1DA34): L<<385.0,375.0>--<435.0,325.0>> -> L<<435.0,325.0>--<459.0,300.0>>
- u1DA34 (U+1DA34): L<<541.0,300.0>--<565.0,325.0>> -> L<<565.0,325.0>--<615.0,375.0>> [code: found-colinear-vectors]

⚠ WARN: Do outlines contain any jaggy segments? (com.google.fonts/check/outline_jaggy_segments)

⚠ WARN The following glyphs have jaggy segments:
- u1D80F (U+1D80F): B<<565.5,423.5>-<596.0,411.0>-<621.0,388.0>>/L<<621.0,388.0>--<369.0,640.0>> = 2.3859440303887243
- u1D81F (U+1D81F): B<<565.5,423.5>-<596.0,411.0>-<621.0,388.0>>/L<<621.0,388.0>--<369.0,640.0>> = 2.3859440303887243
- u1D82C (U+1D82C): L<<407.0,378.0>--<486.0,394.0>>/L<<486.0,394.0>--<424.0,394.0>> = 11.449337988500027
- u1D8A5 (U+1D8A5): B<<565.5,423.5>-<596.0,411.0>-<621.0,388.0>>/L<<621.0,388.0>--<369.0,640.0>> = 2.3859440303887243 [code: found-jaggy-segments]

⚠ WARN: Do outlines contain any semi-vertical or semi-horizontal lines? (com.google.fonts/check/outline_semi_vertical)

⚠ WARN The following glyphs have semi-vertical/semi-horizontal lines:
- u1D81C (U+1D81C): L<<479.0,436.0>--<478.0,575.0>>
- u1D923 (U+1D923): L<<528.0,307.0>--<527.0,434.0>>
- u1D924 (U+1D924): L<<492.0,399.0>--<619.0,398.0>>
- u1DA65 (U+1DA65): L<<642.0,31.0>--<358.0,30.0>>
- u1DA66 (U+1DA66): L<<642.0,31.0>--<358.0,30.0>> [code: found-semi-vertical]

ℹ INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)

ℹ INFO Hinting filesize impact:

	ofl/notosanssignwriting/NotoSansSignWriting-Regular.ttf
Dehinted Size	5.1Mb
Hinted Size	7.5Mb
Increase	2.4Mb
Change	48.0 %
[code: size-impact]

ℹ INFO: EPAR table present in font? (com.google.fonts/check/epar)

ℹ INFO EPAR table not present in font. To learn more see When missing EPAR table, just emit INFO alert fonttools/fontbakery#818 [code: lacks-EPAR]

ℹ INFO: Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (com.google.fonts/check/gasp)

ℹ INFO These are the ppm ranges declared on the gasp table:

PPM <= 65535:
flag = 0x0F
- Use grid-fitting
- Use grayscale rendering
- Use gridfitting with ClearType symmetric smoothing
- Use smoothing along multiple axes with ClearType®
[code: ranges]

ℹ INFO: Check for font-v versioning. (com.google.fonts/check/fontv)

ℹ INFO Version string is: "Version 2.005; ttfautohint (v1.8.4.7-5d5b)"
The version string must ideally include a git commit hash and either a "dev" or a "release" suffix such as in the example below:
"Version 1.3; git-0d08353-release" [code: bad-format]

ℹ INFO: Font contains all required tables? (com.google.fonts/check/required_tables)

ℹ INFO This font contains the following optional tables:
- cvt
- fpgm
- loca
- prep
- GPOS
- GSUB
- gasp [code: optional-tables]

ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)

ℹ INFO ofl/notosanssignwriting [code: family-path]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	3	13	65	7	158	0
0%	1%	5%	26%	3%	64%	0%

Note: The following loglevels were omitted in this report:

SKIP
PASS
DEBUG

simoncozens · 2023-06-27T08:21:32Z

This release: 

- Allows additional marks on the modified forms of the head (#6) 
- Allows multiple modifier marks on the face (#2) 
- Ensure that marks correctly overlay onto the head (#4)

github-actions · 2023-06-27T08:29:29Z

Fontbakery report

Fontbakery version: 0.8.13

[1] Family checks

ℹ INFO: Check axis ordering on the STAT table. (com.google.fonts/check/STAT/axis_order)

ℹ INFO From a total of 1 font files, 1 of them (100.00%) lack a STAT table.

And these are the most common STAT axis orderings:
[code: summary]

[22] NotoSansSignWriting-Regular.ttf

🔥 FAIL: DESCRIPTION.en_us.html must have more than 200 bytes. (com.google.fonts/check/description/min_length)

🔥 FAIL DESCRIPTION.en_us.html must have size larger than 200 bytes. [code: too-short]

🔥 FAIL: Check font follows the Google Fonts vertical metric schema (com.google.fonts/check/vertical_metrics)

🔥 FAIL The sum of hhea.ascender + abs(hhea.descender) + hhea.lineGap is 1002 when it should be at least 1200 [code: bad-hhea-range]

🔥 FAIL: Ensure soft_dotted characters lose their dot when combined with marks that replace the dot. (com.google.fonts/check/soft_dotted)

🔥 FAIL The dot of soft dotted characters used in orthographies must disappear in the following strings: į̀ į́ į̂ į̃ į̄ į̌

The dot of soft dotted characters should disappear in other cases, for example: į̆ į̇ į̈ į̊ į̋ į̒ į̦̀ į̦́ į̦̂ į̦̃ į̦̄ į̦̆ į̦̇ į̦̈ į̦̊ į̦̋ į̦̌ į̦̒ į̧̀ į̧́ [code: soft-dotted]

⚠ WARN: DESCRIPTION.en_us.html should end in a linebreak. (com.google.fonts/check/description/eof_linebreak)

⚠ WARN The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]

⚠ WARN: Check for codepoints not covered by METADATA subsets. (com.google.fonts/check/metadata/unreachable_subsetting)

⚠ 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: canadian-aboriginal, yi, tifinagh
U+02D8 BREVE: try adding one of: canadian-aboriginal, yi
U+02D9 DOT ABOVE: try adding one of: canadian-aboriginal, yi
U+02DB OGONEK: try adding one of: canadian-aboriginal, yi
U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: coptic, tifinagh, cherokee, math
U+0306 COMBINING BREVE: try adding one of: old-permic, tifinagh
U+0307 COMBINING DOT ABOVE: try adding one of: old-permic, tifinagh, canadian-aboriginal, tai-le, coptic, malayalam, syriac, math
U+030A COMBINING RING ABOVE: try adding syriac
U+030B COMBINING DOUBLE ACUTE ACCENT: try adding one of: osage, cherokee
U+030C COMBINING CARON: try adding one of: tai-le, cherokee
U+200C ZERO WIDTH NON-JOINER: try adding one of: dogra, chakma, cham, khudawadi, batak, devanagari, warang-citi, saurashtra, hanunoo, syriac, thai, duployan, hatran, kaithi, sundanese, javanese, mahajani, bengali, manichaean, siddham, tifinagh, tirhuta, new-tai-lue, tai-viet, hanifi-rohingya, mongolian, balinese, khmer, buhid, pahawh-hmong, newa, nko, takri, tagalog, modi, kannada, thaana, phags-pa, grantha, limbu, oriya, avestan, sogdian, meetei-mayek, rejang, tagbanwa, gujarati, tibetan, buginese, kayah-li, gurmukhi, brahmi, sharada, khojki, tai-le, tamil, yi, telugu, malayalam, tai-tham, psalter-pahlavi, lepcha, myanmar, gunjala-gondi, kharoshthi, syloti-nagri, sinhala, mandaic
U+25CC DOTTED CIRCLE: try adding one of: batak, wancho, mahajani, bengali, manichaean, tifinagh, balinese, music, soyombo, tagbanwa, caucasian-albanian, tibetan, khojki, tamil, math, kharoshthi, sinhala, mandaic, ahom, devanagari, duployan, kaithi, buhid, masaram-gondi, thaana, tagalog, modi, phags-pa, symbols, grantha, osage, buginese, tai-le, yi, hebrew, gunjala-gondi, syloti-nagri, chakma, cham, khudawadi, hanunoo, syriac, sundanese, javanese, tirhuta, new-tai-lue, hanifi-rohingya, marchen, mongolian, khmer, takri, bhaiksuki, adlam, limbu, elbasan, meetei-mayek, gujarati, miao, kayah-li, gurmukhi, old-permic, brahmi, sharada, malayalam, dogra, coptic, thai, siddham, tai-viet, pahawh-hmong, newa, nko, kannada, bassa-vah, oriya, sogdian, mende-kikakui, rejang, zanabazar-square, lao, telugu, psalter-pahlavi, lepcha, myanmar

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

⚠ WARN: Ensure files are not too large. (com.google.fonts/check/file_size)

⚠ WARN Font file is 7.5Mb; ideally it should be less than 1.0Mb [code: large-font]

⚠ WARN: Combined length of family and style must not exceed 27 characters. (com.google.fonts/check/name/family_and_style_max_length)

⚠ WARN The combined length of family and style exceeds 27 chars in the following 'WINDOWS' entries:
FONT_FAMILY_NAME = 'Noto Sans SignWriting' / SUBFAMILY_NAME = 'Regular'

Please take a look at the conversation at fonttools/fontbakery#2179 in order to understand the reasoning behind these name table records max-length criteria. [code: too-long]

⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts (com.google.fonts/check/repo/vf_has_static_fonts)

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

⚠ WARN: On a family update, the DESCRIPTION.en_us.html file should ideally also be updated. (com.google.fonts/check/description/family_update)

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

⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table. (com.google.fonts/check/meta/script_lang_tags)

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

⚠ WARN: Check font contains no unreachable glyphs (com.google.fonts/check/unreachable_glyphs)

⚠ WARN The following glyphs could not be reached by codepoint or substitution rules:
- nbspace
  [code: unreachable-glyphs]

⚠ WARN: Check if each glyph has the recommended amount of contours. (com.google.fonts/check/contour_count)

⚠ 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: aogonek	Contours detected: 3	Expected: 2

- Glyph name: uogonek	Contours detected: 2	Expected: 1

- Glyph name: aogonek	Contours detected: 3	Expected: 2 

- Glyph name: uogonek	Contours detected: 2	Expected: 1

[code: contour-count]

⚠ WARN: Check math signs have the same width. (com.google.fonts/check/math_signs_width)

⚠ WARN The most common width is 572 among a set of 6 math glyphs.
The following math glyphs have a different width, though:

Width = 322:
minus
[code: width-outliers]

⚠ WARN: Do any segments have colinear vectors? (com.google.fonts/check/outline_colinear_vectors)

⚠ WARN The following glyphs have colinear vectors:
- u1D881 (U+1D881): L<<677.0,319.0>--<672.0,310.0>> -> L<<672.0,310.0>--<502.0,16.0>>
- u1D9A6 (U+1D9A6): L<<471.0,327.0>--<454.0,345.0>> -> L<<454.0,345.0>--<427.0,373.0>>
- u1DA34 (U+1DA34): L<<385.0,375.0>--<435.0,325.0>> -> L<<435.0,325.0>--<459.0,300.0>>
- u1DA34 (U+1DA34): L<<541.0,300.0>--<565.0,325.0>> -> L<<565.0,325.0>--<615.0,375.0>> [code: found-colinear-vectors]

⚠ WARN: Do outlines contain any jaggy segments? (com.google.fonts/check/outline_jaggy_segments)

⚠ WARN The following glyphs have jaggy segments:
- u1D80F (U+1D80F): B<<565.5,423.5>-<596.0,411.0>-<621.0,388.0>>/L<<621.0,388.0>--<369.0,640.0>> = 2.3859440303887243
- u1D81F (U+1D81F): B<<565.5,423.5>-<596.0,411.0>-<621.0,388.0>>/L<<621.0,388.0>--<369.0,640.0>> = 2.3859440303887243
- u1D82C (U+1D82C): L<<407.0,378.0>--<486.0,394.0>>/L<<486.0,394.0>--<424.0,394.0>> = 11.449337988500027
- u1D8A5 (U+1D8A5): B<<565.5,423.5>-<596.0,411.0>-<621.0,388.0>>/L<<621.0,388.0>--<369.0,640.0>> = 2.3859440303887243 [code: found-jaggy-segments]

⚠ WARN: Do outlines contain any semi-vertical or semi-horizontal lines? (com.google.fonts/check/outline_semi_vertical)

⚠ WARN The following glyphs have semi-vertical/semi-horizontal lines:
- u1D81C (U+1D81C): L<<479.0,436.0>--<478.0,575.0>>
- u1D923 (U+1D923): L<<528.0,307.0>--<527.0,434.0>>
- u1D924 (U+1D924): L<<492.0,399.0>--<619.0,398.0>>
- u1DA65 (U+1DA65): L<<642.0,31.0>--<358.0,30.0>>
- u1DA66 (U+1DA66): L<<642.0,31.0>--<358.0,30.0>> [code: found-semi-vertical]

ℹ INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)

ℹ INFO Hinting filesize impact:

	ofl/notosanssignwriting/NotoSansSignWriting-Regular.ttf
Dehinted Size	5.1Mb
Hinted Size	7.5Mb
Increase	2.4Mb
Change	48.0 %
[code: size-impact]

ℹ INFO: EPAR table present in font? (com.google.fonts/check/epar)

ℹ INFO EPAR table not present in font. To learn more see When missing EPAR table, just emit INFO alert fonttools/fontbakery#818 [code: lacks-EPAR]

ℹ INFO: Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (com.google.fonts/check/gasp)

ℹ INFO These are the ppm ranges declared on the gasp table:

PPM <= 65535:
flag = 0x0F
- Use grid-fitting
- Use grayscale rendering
- Use gridfitting with ClearType symmetric smoothing
- Use smoothing along multiple axes with ClearType®
[code: ranges]

ℹ INFO: Check for font-v versioning. (com.google.fonts/check/fontv)

ℹ INFO Version string is: "Version 2.005; ttfautohint (v1.8.4.7-5d5b)"
The version string must ideally include a git commit hash and either a "dev" or a "release" suffix such as in the example below:
"Version 1.3; git-0d08353-release" [code: bad-format]

ℹ INFO: Font contains all required tables? (com.google.fonts/check/required_tables)

ℹ INFO This font contains the following optional tables:
- cvt
- fpgm
- loca
- prep
- GPOS
- GSUB
- gasp [code: optional-tables]

ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)

ℹ INFO ofl/notosanssignwriting [code: family-path]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	3	13	65	7	158	0
0%	1%	5%	26%	3%	64%	0%

Note: The following loglevels were omitted in this report:

SKIP
PASS
DEBUG

Restore sample text

0c81e8d

simoncozens added the I Font Upgrade label Jun 27, 2023

simoncozens linked an issue Jul 18, 2023 that may be closed by this pull request

Update Tier 3 Noto Fonts (summary) #6176

Closed

simoncozens mentioned this pull request Jul 18, 2023

Update Tier 3 Noto Fonts (summary) #6176

Closed

RosaWagner self-requested a review September 5, 2023 12:52

RosaWagner approved these changes Sep 5, 2023

View reviewed changes

RosaWagner merged commit aa5cbdf into main Sep 5, 2023

RosaWagner deleted the gftools_packager_ofl_notosanssignwriting branch September 5, 2023 12:54

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Noto Sans SignWriting: Version 2.005; ttfautohint (v1.8.4.7-5d5b) added #6456

Noto Sans SignWriting: Version 2.005; ttfautohint (v1.8.4.7-5d5b) added #6456

simoncozens commented Jun 27, 2023

github-actions bot commented Jun 27, 2023

simoncozens commented Jun 27, 2023

github-actions bot commented Jun 27, 2023

Noto Sans SignWriting: Version 2.005; ttfautohint (v1.8.4.7-5d5b) added #6456

Noto Sans SignWriting: Version 2.005; ttfautohint (v1.8.4.7-5d5b) added #6456

Conversation

simoncozens commented Jun 27, 2023

github-actions bot commented Jun 27, 2023

Fontbakery report

Summary

simoncozens commented Jun 27, 2023

github-actions bot commented Jun 27, 2023

Fontbakery report

Summary