Add Kalnia minisite URL

[chrissimpkins]

cc @vv-monsalve

[github-actions]

FontBakery report

fontbakery version: 0.10.4

[1] Experimental checks

🔥 FAIL: Shapes languages in all GF glyphsets. (com.google.fonts/check/glyphsets/shape_languages)

• 🔥 FAIL GF_Latin_Core glyphset:

Language	FAIL messages
nl_Latn (Dutch)	Shaper didn't attach acutecomb to uni0237
^	Shaper didn't attach acutecomb to J
mh_Latn (Marshallese)	Some base glyphs were missing: Ḷ, ḷ, Ṃ, ṃ, Ṇ, ṇ, Ọ, ọ
^	Some mark glyphs were missing: ◌̣
^	Shaper produced a .notdef
scn_Latn (Sicilian)	Some base glyphs were missing: Ḍ, ḍ
^	Shaper produced a .notdef
teo_Latn (Teso)	Some base glyphs were missing: Ɔ, Ɛ, Ɨ, Ʉ, ɔ, ɛ, ɨ, ʉ, ᵃ, ᵉ, ᵋ, ᵒ, ᵓ, ᵘ, ᶤ, ᶶ, ⁱ
^	Shaper produced a .notdef

[code: failed-language-shaping]

• ⚠ WARN GF_Latin_Core glyphset:

Language	FAIL messages
lg_Latn (Ganda)	No variant glyphs were found for Eng
dyo_Latn (Jola-Fonyi)	No variant glyphs were found for Eng
ny_Latn (Nyanja)	No variant glyphs were found for Eng
wo_Latn (Wolof)	No variant glyphs were found for Eng

[code: warning-language-shaping]

[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, 0 of them (0.00%) lack a STAT table.

  And these are the most common STAT axis orderings:
  ('wght-wdth', 1) [code: summary]

[13] Kalnia[wdth,wght].ttf

🔥 FAIL: METADATA.pb font.name field contains font name in right format? (com.google.fonts/check/metadata/valid_name_values)

• 🔥 FAIL METADATA.pb font.name field ("Kalnia") does not match correct font name format ("Kalnia Thin"). [code: mismatch]

⚠ WARN: Checking OS/2 achVendID. (com.google.fonts/check/vendor_id)

• ⚠ WARN OS/2 VendorID value 'NONE' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx
  [code: unknown]

⚠ 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: tifinagh, canadian-aboriginal, 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+02DD DOUBLE ACUTE ACCENT: not included in any glyphset definition

• U+0306 COMBINING BREVE: try adding one of: old-permic, tifinagh

• 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+0312 COMBINING TURNED COMMA ABOVE: not included in any glyphset definition
  7 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: latin, latin-ext, math, menu [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 + b

  • b + f

  • f + h

  • h + i

  • i + j

  • j + k

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

⚠ 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: ĩ̦ ĭ̦ i̦̇ i̦̊ i̦̋ ǐ̦ i̦̒ j̦̀ j̦́ ĵ̦ j̦̃ j̦̄ j̦̆ j̦̇ j̦̈ j̦̊ j̦̋ ǰ̦ j̦̒ į̦̀

Your font fully covers the following languages that require the soft-dotted feature: Lithuanian (Latn, 2,357,094 speakers), Navajo (Latn, 166,319 speakers).

Your font does not cover the following languages that require the soft-dotted feature: Lugbara (Latn, 2,200,000 speakers), Ma’di (Latn, 584,000 speakers), Koonzime (Latn, 40,000 speakers), Belarusian (Cyrl, 10,064,517 speakers), Avokaya (Latn, 100,000 speakers), Aghem (Latn, 38,843 speakers), Nateni (Latn, 100,000 speakers), Dan (Latn, 1,099,244 speakers), Ejagham (Latn, 120,000 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Igbo (Latn, 27,823,640 speakers), Dutch (Latn, 31,709,104 speakers), Basaa (Latn, 332,940 speakers), Ebira (Latn, 2,200,000 speakers), Kom (Latn, 360,685 speakers). [code: soft-dotted]

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

• ℹ INFO Hinting filesize impact:

	ofl/kalnia/Kalnia[wdth,wght].ttf
Dehinted Size	113.7kb
Hinted Size	113.7kb
Increase	24 bytes
Change	0.0 %
[code: size-impact]

ℹ INFO: Font has old ttfautohint applied? (com.google.fonts/check/old_ttfautohint)

• ℹ INFO Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.105'] [code: version-not-detected]

ℹ 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.105"
  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: Ensure fonts have ScriptLangTags declared on the 'meta' table. (com.google.fonts/check/meta/script_lang_tags)

• ℹ INFO Latn [code: dlng-tag]
• ℹ INFO Latn [code: slng-tag]

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

• ℹ INFO This font contains the following optional tables:

  • loca

  • prep

  • GPOS

  • GSUB

  • gasp [code: optional-tables]

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

• ℹ INFO ofl/kalnia [code: family-path]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	2	4	50	9	190	0
0%	1%	2%	20%	4%	75%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• PASS
• DEBUG

[vv-monsalve]

The current microsite for Kalnia still needs to be fully developed and is only a front page with an animation and two really short phrases about the font. In its current state, it is not a useful resource.

I think it would be better to include it once it is fully developed (if); otherwise, it would lead more to "user frustration" from a user experience pov.

[RosaWagner]

so… closing?

[vv-monsalve]

In a private chat conversation, we agreed on the following:

add a couple of images to the About section. They are more illustrative about the font than the current page.
If the designer further develops the info in the webpage for the Kalnia families once Kalnia Glaze, the colored version, is ready, we could add the enriched minisite later once we publish the latter.

I'll add the images to the About section and update it in a new PR.