fridamedrano / kalnia-typeface Goto Github PK

License: SIL Open Font License 1.1

Makefile 0.21% Python 0.50% HTML 99.29%

kalnia-typeface's Introduction

Kalnia Typeface

Overview

Kalnia is a variable font with weight and width axes designed with high contrast and refined terminals, drawing inspiration from the Victorian era. This historical period marked a transition from manual to machine production, and the 'fat face' style emerged—a bold and attention-grabbing typography used for poster headlines to stand out from traditional typefaces.

Kalnia embodies the delicate and the boldness, bridging the gap between the old and the new. This display font family comprises a total of eight styles, making it a versatile choice for poster headlines and expressive design projects.

About Frida Medrano

Frida Medrano is a Mexican type and interaction designer currently based in San Fransisco, California. She is interested in design automation and exploration projects where code and design converge. She won the SOTA Catalyst Award in 2018 and has presented her work in forums like ATypI, TypeLab, TypeCon, IxDA, Letrástica, and TMX.

fridamedrano.com | Instagram | GitHub | Twitter

Building

Fonts are built automatically by GitHub Actions - take a look in the "Actions" tab for the latest build.

If you want to build fonts manually on your own computer:

make build will produce font files.
make test will run FontBakery's quality assurance tests.
make proof will generate HTML proof files.

The proof files and QA tests are also available automatically via GitHub Actions.

Changelog

15 October 2022. Version 1.00
18 October 2023. Version 1.105 - Font ready to be onboarded to Google Fonts

License

This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at https://scripts.sil.org/OFL

Repository Layout

This font repository structure is inspired by Unified Font Repository v0.3, modified for the Google Fonts workflow.

kalnia-typeface's People

Contributors

Stargazers

Watchers

kalnia-typeface's Issues

Kerning

Please give the kerning and overall revision and ensure the common pairs are solved. E.g. ATA FA LY AWA AVA PA LV

Update to new template Error

Actions error when using the new template:

TypeError: init() got an unexpected keyword argument 'omit_if_default'
make: *** [Makefile:23: build.stamp] Error 1
Error: Process completed with exit code 2.

Check semi-expanded

Ŋ

Kerning & Spacing: Special puntuations

¿?¡!(){}[]

Guillemet weight

Typically, the guillemets should share the punctuation symbols' style (weight, contrast). Currently, they look too light for the system. Please review them and confirm they are as intended. They could share the style of the caron mark for the heavy masters :)

Meta table error

The error that I got from the meta table is:

File "/Users/fridamedrano/Desktop/Github/Test-2023-Sep11/Kalnia-Color/venv/lib/python3.11/site-packages/glyphsLib/builder/custom_params.py", line 573, in to_ufo_meta_table
tag, data = entry["tag"], entry["data"]
TypeError: string indices must be integers, not 'str'

I deleted the meta table to pass and export everything on the Actions.
The line deleted is (in the glyphs file):

name = "meta Table";
value = "{\012 data = Latn;\012 tag = dlng;\012}\012{\012 data = Latn;\012 tag = slng;\012}";

Marks consistency

Please review the consistency among marks in terms of size (width) and weight

Diagonal marks (acute, grave, circumflex, caron) look lighter than the others in the Thin weight
macron looks too light in the bolder and wider masters
Define a width for the marks. breve looks narrower and tilde too wide for the system (circumflex looks like an intermediate point).
Review the vertical alignment of breve, dotaccent, and macron. Ideally, marks are aligned on the vertical axis, and the dot in the i should match the dot accent.
It is suggested for the outline of the marks to be in the combining mark, and use it as component in the Legacy one.
commaaccet is particularly heavy in the heavy and wider masters.
Review the distance between the base glyph and the mark for round uppercase letters. E.g. Cdotaccent

replacementCharacter

Is this character � needed for Latin core?
If not, I will delete it from the font (I will keep the not-def that I currently have).

Description Update

Catalan punt volat should appear centered between L’s

periodcentered.loclCAT should appear centered between two lowercase l’s

periodcentered.loclCAT.case should appear centered between two uppercase L’s

ldot and Ldot can be derived from L/l + periodcentered.loclCAT(.case)

Useful scripts: mekkablue > Build Glyphs > Center punt volat and Build Ldot

I am bringing here the issue opened by Rainer in Kalnia-Color repo.

The period looks closer to the left l.

Interpolation problems in `Kalnia[wdth,wght].ttf`

Hello!

This is an automatically-generated report about possible interpolation problems in Kalnia[wdth,wght].ttf, as found in the Google Fonts catalog.

The particular version of the font that was tested was archive:.

To download a PDF version of this report with helpful visuals of the problems, click here; Or to view it on the GitHub website, click here.

The report follows:

Glyph percent was not compatible:
  Masters: '', 'wght=700.0':
    Contour 3 start point differs: 0 in '', 28 in 'wght=700.0'; reversed: False
Glyph perthousand was not compatible:
  Masters: '', 'wght=700.0':
    Contour 6 start point differs: 0 in '', 28 in 'wght=700.0'; reversed: False

This report was generated using the fonttools varLib.interpolatable tool. We understand that sometimes the tool generates false-positives. Particularly for more complicated font designs. If you did not find this report useful, please apologize and ignore & close it.

To give feedback about this report, please file an issue or open a discussion at fonttools.

FB Warnings

Reported after building font with source file at commit 9dd6f18

Remember to abbreviate the description included in the font info.

⚠ WARN: Description strings in the name table must not exceed 200 characters. (com.google.fonts/check/name/description_max_length)

An old FontLab version had a bug which caused it to store copyright notices in nameID 10 entries.

In order to detect those and distinguish them from actual legitimate usage of this name table entry, we expect that such strings do not exceed a reasonable length of 200 chars.

Longer strings are likely instances of the FontLab bug.

⚠ WARN A few name table entries with ID=10 (NameID.DESCRIPTION) are longer than 200 characters. Please check whether those entries are copyright notices mistakenly stored in the description string entries by a bug in an old FontLab version. If that's the case, then such copyright notices must be removed from these entries. [code: too-long]

Percent and perthousand had been already checked. Please review the others.

⚠ WARN: Detect any interpolation issues in the font. (com.google.fonts/check/interpolation_issues)

When creating a variable font, the designer must make sure that corresponding paths have the same start points across masters, as well as that corresponding component shapes are placed in the same order within a glyph across masters. If this is not done, the glyph will not interpolate correctly.

Here we check for the presence of potential interpolation errors using the fontTools.varLib.interpolatable module.

⚠ WARN Interpolation issues were found in the font:
- Contour 1 start point differs in glyph 'percent' between location wght=100,wdth=100 and location wght=700,wdth=100
- Contour 3 start point differs in glyph 'percent' between location wght=100,wdth=100 and location wght=700,wdth=100
- Contour 4 start point differs in glyph 'perthousand' between location wght=100,wdth=100 and location wght=700,wdth=100
- Contour 6 start point differs in glyph 'perthousand' between location wght=100,wdth=100 and location wght=700,wdth=100
- Contour 2 start point differs in glyph '.notdef' between location wght=100,wdth=100 and location wght=100,wdth=125
- Contour 2 start point differs in glyph '.notdef' between location wght=100,wdth=100 and location wght=700,wdth=125
- Contour 0 start point differs in glyph 'Oslash' between location wght=100,wdth=100 and location wght=700,wdth=100
- Contour 0 start point differs in glyph 'Oslash' between location wght=100,wdth=100 and location wght=700,wdth=125 [code: interpolation-issues]

Lcaron, dcaron, lcaron, tcaron should NOT be composed with quoteright or quotesingle or comma or caron(comb). It should be composed with a distinctive glyph which doesn't look like an apostrophe.

Source: https://ilovetypography.com/2009/01/24/on-diacritics/ http://diacritics.typo.cz/index.php?id=5 https://www.typotheque.com/articles/lcaron

🔥 FAIL Lcaron uses component quoteright. [code: bad-mark]
🔥 FAIL dcaron uses component quoteright. [code: bad-mark]
🔥 FAIL lcaron uses component quoteright. [code: bad-mark]
🔥 FAIL tcaron uses component quoteright. [code: bad-mark]