google / google/fonts

Add Buena Mono

Open
#10,861 1 comment 2 reactions 0 assignees View on GitHub
I New Font II Submission
Dominant language
HTML
Stars
20.5k
Forks
2.9k
Avg merge
1d 22h
Merged PRs (30d)
96

Description

**Font Project Git Repo URL:**

https://github.com/buenagames/buena-mono

**Super short description of the Font Family:**

Buena Mono is a writer-first variable monospace — built for extended prose in markdown and code editors while keeping code legible. Two axes in the direct-download build (**wght 100–800**, **slnt 0 to −10°**) from 8 masters; the Google Fonts submission is the wght-only Roman + Italic pair. 5,406 glyphs over 4,285 codepoints, 971 languages, 51 OpenType features, 164 ligature glyphs, and full box-drawing, block, Braille and Powerline coverage.

Specimen and live tester: https://buena-mono.buenalabs.io

**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](https://openfontlicense.org/open-font-license-official-text/)
- [x] I confirm that by 'entire font project', no "plus" or "pro" or other larger version of the project exists as a retail font anywhere
- [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, and I commit to clearly disclosing if AI tools were used in the creation of this project.
- [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](https://namecheck.fontdata.com/)
- [x] 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.
- [x] The font supports at least the Google Fonts 'Latin Core' glyphset from [github.com/googlefonts/glyphsets](https://github.com/googlefonts/glyphsets)
- [x] The repo has the [Google Fonts preferred upstream repo structure](https://googlefonts.github.io/gf-guide/upstream.html)
- [x] I have read, agree with, and comply with, the full [Google Fonts contributing requirements](https://googlefonts.github.io/gf-guide/index#pre-production-getting-your-fonts-ready-for-gf)
- [x] I will maintain the repository and participate in the onboarding process (addressing, solving, and responding to issues, merging pull requests, etc)

---

### Derivation — please read, this family is not an original design

Buena Mono is a **derivative work**. Its core Latin outlines were imported from [Fragment Mono](https://github.com/weiweihuanghuang/fragment-mono) (Wei Huang, OFL 1.1), which itself derives from Nimbus Sans (URW Design Studio), and were then substantially transformed — respaced to a 618-unit cell, reweighted across 8 masters, and extended.

Every donor is credited in `OFL.txt` and the derivation chain is recorded in `FONTLOG.txt`:

| Upstream | Contribution |
|---|---|
| [Fragment Mono](https://github.com/weiweihuanghuang/fragment-mono) | core Latin outlines |
| [IBM Plex](https://github.com/IBM/plex) · [Noto](https://github.com/notofonts/latin-greek-cyrillic) | Cyrillic |
| [Cascadia Code](https://github.com/microsoft/cascadia-code) · [JetBrains Mono](https://github.com/JetBrains/JetBrainsMono) | Greek & Coptic |
| [Bravura](https://github.com/steinbergmedia/bravura) | treble and bass clefs (U+1D11E, U+1D122) |

No upstream project's Reserved Font Name is used in whole or in part; the family is named **Buena Mono** and carries no RFN of its own. The chess pieces (U+2654–265F) are original art.

### AI disclosure

Claude was used on this project for build and QA tooling, the reports suite, documentation and the specimen site. **It was not used to draw, space or kern glyphs** — the outlines derive from Fragment Mono as described above and were transformed by script and by hand, as recorded in `FONTLOG.txt`.

### Submission shape

Wght-only **Roman + Italic pair**, since Google Workspace cannot reach slanted designspace locations:

- `BuenaMono[wght].ttf` — wght 100–800, default 400; 8 instances: Thin, ExtraLight, Light, Regular, Medium, SemiBold, Bold, ExtraBold
- `BuenaMono-Italic[wght].ttf` — same axis; 8 instances: Thin Italic … ExtraBold Italic

The 2-axis `BuenaMono-VF` (wght + slnt) remains the direct-download build.

### Verification, at v1.231

| Check | Result |
|---|---|
| fontspector, googlefonts profile, on the packaged pair | 358 checks — **0 FAIL, 0 FATAL, 0 ERROR** (231 PASS, 372 WARN, 84 SKIP) |
| GF Latin Core (324 entries) | full coverage, no gaps |
| namecheck.fontdata.com — "Buena Mono" | 0 matches at every confidence level; no trademark |
| Vendor ID | `BUEN` — [registered with Microsoft](https://learn.microsoft.com/en-us/typography/vendors/) (Foundry "Buena"), stamped as `achVendID=BUEN` |
| Upstream structure | `upstream.yaml` with `build: make package`; `make package` verified to run clean in the public repo itself, which is the tree GF tooling builds from |

One residual `googlefonts/vendor_id` WARN just reflects fontspector's bundled vendor registry lagging Microsoft's live list — `BUEN` is present upstream today.

### Repo

Sources (`.glyphs` + 8 UFO masters + designspace), full build via `make`, `OFL.txt`, `FONTLOG.txt`, `METADATA.pb`, `DESCRIPTION.en_us.html`, `ARTICLE.en_us.html`, and a technical QA report suite at https://buena-mono.buenalabs.io/reports/

**Image:**

Image

Image

Image

Contributor guide

Open the contributing guide

Research direction

Start in the Buena Mono repository by reading upstream.yaml, OFL.txt, FONTLOG.txt, and METADATA.pb, then run the documented make package build. Review the packaged Roman and Italic fonts against the listed Google Fonts requirements and QA results; done means the submission passes the onboarding review and required metadata, licensing, structure, and coverage checks.

Written by the indexing model from the issue text.

Assessment

Domain
content, design
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.