Visitar URL original
Add Snark · Issue #11172 · google/fonts · GitHub
Skip to content

Add Snark #11172

New issue
New issue
Open
Open
Add Snark#11172
Labels
I New FontII Submissionpending proposal for non-commissioned fonts suggested in the issue tracker
Milestone
Submissions to review

Description

@linusareng
linusareng
opened on Oct 25, 2026

Font Project Git Repo URL:
https://github.com/linusareng/Snark

Super short description of the Font Family:
Snark is a felt-tip hand written at speed — a single-weight display face with decisive strokes, round open bowls and a wandering baseline. The letterforms are the designer's own hand. It covers the Google Fonts Latin Core glyphset in full and passes the googlefonts FontBakery profile with no failures.

Requirements:

By opening this issue, I confirm the project meets the following requirements:

  • The entire font project is available in a Github repository (repo) and licensed under the OFL
  • I confirm that by 'entire font project', no "plus" or "pro" or other larger version of the project exists as a retail font anywhere
  • The source files are available in the repo
  • I am the sole copyright author of the entire project, or all other copyright authors have licensed their work to me under the OFL, and I commit to clearly disclosing if AI tools were used in the creation of this project.
  • There are no "Reserved Font Names" in the OFL license information, or in the project documentation of any known upstream projects. If there are RFNs, they are not used in whole or in part in this family name, or, I want to discuss how Google can work with my use of them.
  • The family name is unique according to namecheck.fontdata.com
  • The name of the font family expected to appear on app menus must be very clearly communicated and definitive. It should not include any copyright holder's full names or acronyms.
  • The font supports at least the Google Fonts 'Latin Core' glyphset from github.com/googlefonts/glyphsets (direct link)
  • The repo has the Google Fonts preferred upstream repo structure
  • I have read, agree with, and comply with, the full Google Fonts contributing requirements
  • I will maintain the repository and participate in the onboarding process (addressing, solving, and responding to issues, merging pull requests, etc)

Image:
Image

Activity

  1. linusareng
    added
    I New Font
    II Submissionpending proposal for non-commissioned fonts suggested in the issue tracker
    on Oct 25, 2026

  2. github-actions commented on Oct 25, 2026

    @github-actions
    github-actionsBot
    on Oct 25, 2026 – with GitHub Actions
    Contributor

    Font Submission Triage Summary: Snark

    Thank you for submitting Snark to Google Fonts! Here is the summary of our initial automated triage:

    • Template and Requirements Checklist:

      • The submission issue adheres to the standard issue template.
      • All requirements in the checklist have been confirmed.

    • Repository Layout and googlefonts-project-template:

      • The repository layout follows Google Fonts upstream conventions with "sources/", "fonts/ttf/", and "documentation/" directories.
      • A build configuration is provided at "sources/config.yaml" for gftools builder.
      • While it uses "config.yaml" and a GitHub Actions build workflow (.github/workflows/build.yaml), it does not use the full googlefonts-project-template repository boilerplate (it does not include a Makefile or requirements.in).

    • Font Sources:

      • Font source files are present in a preferred format: sources/Snark.glyphs (.glyphs format).

    • Licensing and Reserved Font Names (RFN):

      • Licensed under the SIL Open Font License, Version 1.1 (OFL.txt).
      • No Reserved Font Name (RFN) is requested or declared in OFL.txt or project documentation.
      • Copyright is attributed to "The Snark Project Authors (https://github.com/linusareng/Snark)", with Linus Areng listed in AUTHORS.txt and CONTRIBUTORS.txt.

    • Binary and Glyph Coverage Checks:

      • Font binary tested: fonts/ttf/Snark-Regular.ttf.
      • Tested with fontspector using the googlefonts profile.
      • Latin Core Coverage: Passed! The font covers the complete Google Fonts Latin Core glyphset (0 missing codepoints).
      • General quality checks show expected characteristics for a handwriting display face with decisive strokes and a wandering baseline, with no blocking errors.
  3. emmamarichal
    added this to Google Fontson Oct 26, 2026
  4. github-project-automation
    moved this to Todo in Google Fontson Oct 26, 2026
  5. emmamarichal
    added this to the Submissions to review milestone on Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    I New FontII Submissionpending proposal for non-commissioned fonts suggested in the issue tracker

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions