Add Bytesized

[balt-dev]

Font Project Git Repo URL:

https://github.com/balt-dev/bytesized-gf

Super short description of the Font Family:

A tiny 3x4 pixel font, made to be as legible as possible within the tiny scale.

Requirements:

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

• [x] The entire font project is available in a Github repository (repo) and licensed under the OFL
• [x] The source files are available in the repo
• [x] I am the sole copyright author of the entire project, or, all other copyright authors have licensed their work to me under the OFL
• [x] 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.
• [x] The family name is unique according to namecheck.fontdata.com
• [x] The font supports at least the Google Fonts 'Latin Core' glyphset from github.com/googlefonts/glyphsets (direct link)
• [x] The repo has the Google Fonts preferred upstream repo structure
• [x] I have read, agree with, and comply with, the full Google Fonts contributing requirements
• [x] I will maintain the repository and participate in the onboarding process (addressing, solving, and responding to issues, merging pull requests, etc)

Image:

[balt-dev]

I wanted to add that one of the main reasons I made this font was that it can be printed at a ridiculously small font size and still be legible. I was able to get it down to 1.5pt on a 600dpi (I think) printer, leaving each character smaller than the thickness of my fingernails, but it was still perfectly readable using a magnifying glass!

[emmamarichal]

hi @balt-dev! thank you for your submission, we will take a look and will let you know!

For the build process, I understand you build the font from an image. We would need however, a source file like a .glyphs file, so we can reproduce easily the build process (if some contributors want to add some glyphs for example).

[balt-dev]

@emmamarichal I understand what you mean, but:

1. The image is easily editable, so it's easy to add new glyphs even without a .glyphs file - I've added instructions to the repo - and
2. I don't have access to any program that could generate a .glyphs file - being a college student with zero budget, I can't afford Glyphs, and I'd need to make a macOS virtual machine to even run it, which I've tried and my laptop overloads - and even then, editing them from a vector editor seems like much more work.

I could maybe see if I could generate a .glyphs file instead of a .ttf as a one-time thing, put that in the repo permanently, and then after that build like normal? I've found no tools to do this, however.

[balt-dev]

When first creating the generation script, I did try to find something free that would output .glyphs files, because I knew this would come up, but I didn't find anything.

[emmamarichal]

@balt-dev Ok, thank you for explanations! The format can also be a .ufo, don't know if you tried that?

[balt-dev]

I have not! I'll have to look into that when I have the time - should be able to within a few days.

---

From: Emma Marichal @.> Sent: Friday, October 25, 2024 3:31 AM To: google/fonts @.> Cc: Balt @.>; Mention @.> Subject: Re: [google/fonts] Add Bytesized (Issue #8279)

@balt-devhttps://github.com/balt-dev Ok, thank you for explanations! The format can also be a .ufo, don't know if you tried that?

— Reply to this email directly, view it on GitHubhttps://github.com/google/fonts/issues/8279#issuecomment-2437205430, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AODCRVTZDDICOMZV6BZUQ2TZ5H6WHAVCNFSM6AAAAABPOJUCEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZXGIYDKNBTGA. You are receiving this because you were mentioned.Message ID: @.***>