tonsky / tonsky/FiraCode

Please consider to use a new name for variable font

Open
#1,332 1 comment 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Clojure
Stars
82k
Forks
3.2k
PR merge metrics
No merged PRs in 30d

Description

Now the static fonts and the variable version share the same name Fira Code, however, it will lead to some issues when both are installed. For example, macOS's font book will complain duplication, and TeX/dvipdfmx will fail to compile if in the look up ordering the variable version may be prior to the static ones (see #1156).

So please consider to use another name, such as Fira Code VF to resolve these problems. The same way has been adopted by Source Code Pro (Source Code Variable). Thank you!

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by locating the static and variable Fira Code font artifacts and reviewing issue #1156, then check how their names are produced. Confirm the variable font can use a distinct name such as “Fira Code VF” without breaking macOS Font Book or TeX/dvipdfmx lookup; the changed naming should prevent duplicate-font and compilation conflicts.

Written by the indexing model from the issue text.

Assessment

Domain
design
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.