Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Proposal - Custom font support

Open
#66 4 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
22/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
zig
Domain
desktop

Research direction

Start in the assets folder, where the bundled CozetteVector font file is loaded, and find the Zig code that reads it at startup. The payload also mentions the cursor file, which is loaded the same way, so check whether that path can be reused. Done would mean a settings option that selects a font file at runtime, with the design of the settings UI and fallback behaviour agreed first, since the issue does not settle either.

Written by the indexing model from the issue text.

Description

I see that in the assets folder there is font files. So is there a way to to make it so in the settings you can change it by getting another font file? I already tried just renaming my file to CozetteVector and putting it in the assets folder, which worked just fine, it is just a bit weird to have to do that.

Edit: This could also probably be done really easily with the cursor file, as it seems to be handled in a similar way of just grabbing from the file, although it would probably be a lot more complex with different sizes and getting it to work right.

(Love the program btw lowkey thinking about learning Zig just to help with it)

Dominant language
Zig
Stars
1.5k
Forks
40
Avg merge
7h 10m
Merged PRs (30d)
98

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fizzyedit/fizzy

All issues in fizzyedit/fizzy

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.