agbalumo: Version 1.000; ttfautohint (v1.8.4) added

[eliheuer]

8a7215a: [gftools-packager] agbalumo: Version 1.000; ttfautohint (v1.8.4) added

• agbalumo Version 1.000; ttfautohint (v1.8.4) taken from the upstream repo https://github.com/SorkinType/Agbalumo.git at commit SorkinType/Agbalumo@3e64aac.

Resolves #6515

[eliheuer]

Updated

Agbalumo: Version 1.000; ttfautohint (v1.8.4) added

---

0215c94: [gftools-packager] Agbalumo: Version 1.000; ttfautohint (v1.8.4) added

• Agbalumo Version 1.000; ttfautohint (v1.8.4) taken from the upstream repo https://github.com/SorkinType/Agbalumo.git at commit SorkinType/Agbalumo@3e64aac.

[eliheuer]

Updated

agbalumo: Version 1.000; ttfautohint (v1.8.4) added

---

c8dfc0c: [gftools-packager] agbalumo: Version 1.000; ttfautohint (v1.8.4) added

• agbalumo Version 1.000; ttfautohint (v1.8.4) taken from the upstream repo https://github.com/SorkinType/Agbalumo.git at commit SorkinType/Agbalumo@ae5e879.

[eliheuer]

Updated

Agbalumo: Version 1.000; ttfautohint (v1.8.4) added

---

b49e64f: [gftools-packager] Agbalumo: Version 1.000; ttfautohint (v1.8.4) added

• Agbalumo Version 1.000; ttfautohint (v1.8.4) taken from the upstream repo https://github.com/SorkinType/Agbalumo.git at commit SorkinType/Agbalumo@ae5e879.

[eliheuer]

This project used to be called Danfo, but the name was recently changed to Agbalumo.

Here is the add font issue: #6515

[RosaWagner]

Since the font is quite thick, we need to decide if it should have "One" appended to the name to be able to onboard other weights later.

[RosaWagner]

If the "development" panel doesn't work to link the issue to can add the issue number with a closing word to achieve the linking :)

[davelab6]

Since the font is quite thick, we need to decide if it should have "One" appended to the name to be able to onboard other weights later.

I confirm this is intended as a single style display face, and if it is expanded in future with a range of weights, the design itself would be modified to be more suitable for text, and so would be a separate family "Agbalumo Pro" or so.

[eliheuer]

Since the font is quite thick, we need to decide if it should have "One" appended to the name to be able to onboard other weights later.

This was resolved in various chats today, we are going to go ahead with onboarding this as just "Agbalumo" without "One" appended. The docs might need to be updated to make it clear this requirement isn't absolutely necessary and exceptions can be made.

[eliheuer]

I resolved all the issues brought up by Rosalie and Dave, making a new pull request soon for a second review.

[eliheuer]

Updated

Agbalumo: Version 1.000; ttfautohint (v1.8.4) added

---

6a9a2d7: [gftools-packager] Agbalumo: Version 1.000; ttfautohint (v1.8.4) added

• Agbalumo Version 1.000; ttfautohint (v1.8.4) taken from the upstream repo https://github.com/SorkinType/Agbalumo.git at commit SorkinType/Agbalumo@c6c381d.

[github-actions]

FontBakery report

fontbakery version: 0.9.2

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

[19] Agbalumo-Regular.ttf

⚠ WARN: Check Google Fonts glyph coverage. (com.google.fonts/check/glyph_coverage)

• ⚠ WARN GF_TransLatin_Pinyin is almost fulfilled. Missing codepoints:

  • 0x1D3A (MODIFIER LETTER CAPITAL N)

  • 0x0114 (LATIN CAPITAL LETTER E WITH BREVE)

  • 0x012C (LATIN CAPITAL LETTER I WITH BREVE)

  • 0x014E (LATIN CAPITAL LETTER O WITH BREVE)

  • 0x0115 (LATIN SMALL LETTER E WITH BREVE)

  • 0x012D (LATIN SMALL LETTER I WITH BREVE)

  • 0x014F (LATIN SMALL LETTER O WITH BREVE)
    [code: missing-codepoints]

• ⚠ WARN GF_Latin_African is almost fulfilled. Missing codepoints:

  • 0xA7B3 (LATIN CAPITAL LETTER CHI)

  • 0x01EE (LATIN CAPITAL LETTER EZH WITH CARON)

  • 0x1E28 (LATIN CAPITAL LETTER H WITH CEDILLA)

  • 0xA726 (LATIN CAPITAL LETTER HENG)

  • 0xA740 (LATIN CAPITAL LETTER K WITH STROKE)

  • 0xA7AD (LATIN CAPITAL LETTER L WITH BELT)

  • 0x2C60 (LATIN CAPITAL LETTER L WITH DOUBLE BAR)

  • 0x2C62 (LATIN CAPITAL LETTER L WITH MIDDLE TILDE)

  • 0x0220 (LATIN CAPITAL LETTER N WITH LONG RIGHT LEG)

  • 0x0222 (LATIN CAPITAL LETTER OU)

  • 7 more.

Use -F or --full-lists to disable shortening of long lists. [code: missing-codepoints]

• ⚠ WARN GF_Latin_Beyond is almost fulfilled. Missing codepoints:

  • 0x03BB (GREEK SMALL LETTER LAMDA)

  • 0x03C7 (GREEK SMALL LETTER CHI)

  • 0x01EE (LATIN CAPITAL LETTER EZH WITH CARON)

  • 0x2C62 (LATIN CAPITAL LETTER L WITH MIDDLE TILDE)

  • 0x023E (LATIN CAPITAL LETTER T WITH DIAGONAL STROKE)

  • 0x01EF (LATIN SMALL LETTER EZH WITH CARON)

  • 0x02C0 (MODIFIER LETTER GLOTTAL STOP)

  • 0x0166 (LATIN CAPITAL LETTER T WITH STROKE)

  • 0x01F0 (LATIN SMALL LETTER J WITH CARON)

  • 0x0138 (LATIN SMALL LETTER KRA)

  • 8 more.

Use -F or --full-lists to disable shortening of long lists. [code: missing-codepoints]

• ⚠ WARN GF_TransLatin_Arabic is almost fulfilled. Missing codepoints:

  • 0x1E96 (LATIN SMALL LETTER H WITH LINE BELOW)

  • 0x1E97 (LATIN SMALL LETTER T WITH DIAERESIS)

  • 0x02BD (MODIFIER LETTER REVERSED COMMA)
    [code: missing-codepoints]

⚠ 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+02B0 MODIFIER LETTER SMALL H: not included in any glyphset definition

• U+02B7 MODIFIER LETTER SMALL W: not included in any glyphset definition

• U+02BE MODIFIER LETTER RIGHT HALF RING: not included in any glyphset definition

• U+02BF MODIFIER LETTER LEFT HALF RING: not included in any glyphset definition

• U+02C7 CARON: try adding one of: tifinagh, canadian-aboriginal, yi

• U+02CA MODIFIER LETTER ACUTE ACCENT: not included in any glyphset definition

• U+02CB MODIFIER LETTER GRAVE ACCENT: not included in any glyphset definition

• U+02D7 MODIFIER LETTER MINUS SIGN: not included in any glyphset definition

• U+02D8 BREVE: try adding one of: canadian-aboriginal, yi

• U+02D9 DOT ABOVE: try adding one of: canadian-aboriginal, yi
  79 more.

Use -F or --full-lists to disable shortening of long lists.

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

⚠ WARN: Is there kerning info for non-ligated sequences? (com.google.fonts/check/kerning_for_non_ligated_sequences)

• ⚠ WARN GPOS table lacks kerning info for the following non-ligated sequences:

  • f + i

  • i + l [code: lacks-kern-info]

⚠ 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: METADATA.pb: Designers are listed correctly on the Google Fonts catalog? (com.google.fonts/check/metadata/designer_profiles)

• ⚠ WARN It seems that Raphael Alegbeleye is still not listed on the designers catalog. Please submit a photo and a link to a webpage where people can learn more about the work of this designer/typefoundry. [code: profile-not-found]

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

  • M_gravecomb

  • a.alt2

  • a.alt5

  • acutecomb.narrow

  • ampersand.001

  • ampersand.003

  • ampersand.004

  • ampersand.005

  • ampersand.006

  • ampersand.007

  • 14 more.

Use -F or --full-lists to disable shortening of long lists.
[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: y	Contours detected: 2	Expected: 1

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

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

- Glyph name: ydieresis	Contours detected: 4	Expected: 3

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

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

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

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

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

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

- 73 more.

Use -F or --full-lists to disable shortening of long lists.
[code: contour-count]

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

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

Width = 554:
plus

Width = 515:
less

Width = 521:
greater

Width = 565:
logicalnot

Width = 579:
plusminus

Width = 541:
multiply

Width = 548:
minus, divide

Width = 546:
approxequal

Width = 502:
lessequal

Width = 506:
greaterequal
[code: width-outliers]

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

• ⚠ WARN The following glyphs have jaggy segments:

  • Eng (U+014A): B<<392.5,483.0>-<431.0,369.0>-<454.0,212.0>>/L<<454.0,212.0>--<458.0,292.0>> = 11.196769743469542

  • h (U+0068): B<<255.0,432.0>-<244.0,386.0>-<233.0,346.0>>/B<<233.0,346.0>-<252.0,383.0>-<283.5,419.5>> = 11.804859836651074

  • hbar (U+0127): B<<254.5,418.5>-<245.0,379.0>-<237.0,346.0>>/B<<237.0,346.0>-<256.0,383.0>-<287.5,419.5>> = 13.554116225585668

  • hcircumflex (U+0125): B<<255.0,432.0>-<244.0,386.0>-<233.0,346.0>>/B<<233.0,346.0>-<252.0,383.0>-<283.5,419.5>> = 11.804859836651074

  • ordfeminine (U+00AA): B<<226.0,293.5>-<226.0,297.0>-<227.0,301.0>>/B<<227.0,301.0>-<206.0,258.0>-<178.5,237.5>> = 11.993348723586983

  • uni021F (U+021F): B<<255.0,432.0>-<244.0,386.0>-<233.0,346.0>>/B<<233.0,346.0>-<252.0,383.0>-<283.5,419.5>> = 11.804859836651074

  • uni0265 (U+0265): B<<321.5,68.0>-<333.0,114.0>-<343.0,154.0>>/B<<343.0,154.0>-<324.0,117.0>-<292.5,80.5>> = 13.144867617550734

  • uni02B0 (U+02B0): B<<207.0,529.0>-<198.0,496.0>-<189.0,467.0>>/B<<189.0,467.0>-<205.0,494.0>-<232.5,520.5>> = 13.409208558112896

  • uni1E23 (U+1E23): B<<255.0,432.0>-<244.0,386.0>-<233.0,346.0>>/B<<233.0,346.0>-<252.0,383.0>-<283.5,419.5>> = 11.804859836651074

  • uni1E25 (U+1E25): B<<255.0,432.0>-<244.0,386.0>-<233.0,346.0>>/B<<233.0,346.0>-<252.0,383.0>-<283.5,419.5>> = 11.804859836651074

  • 5 more.

Use -F or --full-lists to disable shortening of long lists. [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:

  • summation (U+2211): L<<412.0,564.0>--<247.0,563.0>>

  • uni01A9 (U+01A9): L<<408.0,574.0>--<230.0,573.0>> [code: found-semi-vertical]

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

• ⚠ WARN The dot of soft dotted characters should disappear in other cases, for example: ɉ̀ ɉ́ ɉ̂ ɉ̃ ɉ̄ ɉ̆ ɉ̇ ɉ̈ ɉ̉ ɉ̊ ɉ̋ ɉ̌ ɉ̍ ɉ̏ ɉ̐ ɉ̑ ɉ̒ ɉ̓ ɉ᷄ ɉ᷅

Your font fully covers the following languages that require the soft-dotted feature: Koonzime (Latn, 40,000 speakers), Kom (Latn, 360,685 speakers), Avokaya (Latn, 100,000 speakers), Lithuanian (Latn, 2,357,094 speakers), Dutch (Latn, 31,709,104 speakers), Ebira (Latn, 2,200,000 speakers), Nateni (Latn, 100,000 speakers), Aghem (Latn, 38,843 speakers), Navajo (Latn, 166,319 speakers), Igbo (Latn, 27,823,640 speakers), Ma’di (Latn, 584,000 speakers), Lugbara (Latn, 2,200,000 speakers), Basaa (Latn, 332,940 speakers).

Your font does not cover the following languages that require the soft-dotted feature: Dan (Latn, 1,099,244 speakers), Ejagham (Latn, 120,000 speakers), Belarusian (Cyrl, 10,064,517 speakers), Ukrainian (Cyrl, 29,273,587 speakers). [code: soft-dotted]

ℹ INFO: Does DESCRIPTION file contain a upstream Git repo URL? (com.google.fonts/check/description/git_url)

• ℹ INFO Found a git repo URL: https://github.com/SorkinType/Agbalumo [code: url-found]

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

• ℹ INFO Hinting filesize impact:

	ofl/agbalumo/Agbalumo-Regular.ttf
Dehinted Size	370.7kb
Hinted Size	423.2kb
Increase	52.4kb
Change	14.1 %
[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 1.000; ttfautohint (v1.8.4)"
  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/agbalumo [code: family-path]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	0	12	64	8	165	0
0%	0%	5%	26%	3%	66%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• PASS
• DEBUG

[eliheuer]

@RosaWagner About the designer credits, Raphael should be Principal Design, but Eben should be included as a secondary designer.

I included both Sorkin Type and Eben Sorkin in the credits because the font is hosted on the Sorkin Type GitHub, lists Sorkin Type as the manufacturer, and other similar fonts already on Google fonts do the same thing, I looked at Calistoga as an example: https://fonts.google.com/specimen/Calistoga/about

ColumnType is a label Raphael wants to use to release more fonts under. The ColumnType website is not live, and the only online presence I know of is an Instagram page with a few posts: https://www.instagram.com/columntype

The issues have been fixed

[RosaWagner]

I see only one small issue so it won't block the merging, but maybe @eliheuer you can raise an issue upstream so it can be fixed in a next update.

There is an inconsistency between Ldot and L periodcentered.loclCAT.case;

1. since the locl feature is making the substitution with periodcentered.loclCAT, Ldot is a bit useless here, it can be kept for backward compatibility or removed.
2. L periodcentered.loclCAT.case L doesn't display the dot in the middle of the 2 L.

A good practice would be to achieve that through with sidebearing of periodcentered.loclCAT.case, then if Ldot is meant to stay, it can be a component of L periodcentered.loclCAT.case with automatic alignment to make sure both strings are consistent.

[eliheuer]

Thanks! I filled an issue upstream. Eben and the designer are planning on a v 1.100 update this year, so I will try to make sure this is fixed.