google / google/fonts

Add Maorik

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

Description

**Font Project Git Repo URL:**

https://github.com/sallemaor-a11y/Maorikfont

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

Maorik is a geometric Hebrew display family with a Latin companion, drawn for architectural visualisation work. One weight axis, wght 250–700, with drawn masters at both ends. Every curve in the face is a superellipse quadrant at n = 2.16 on a single measured aspect, so the family is consistent in tension rather than in radius. It covers the Hebrew alphabet including final forms, the full niqqud set and the Unicode presentation forms, alongside GF Latin Core.

**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)

---

### Notes I would rather raise now than have you find

**Menu name.** `Maorik`. Five named instances: Light, Regular, Medium, SemiBold, Bold.

**Derivation and upstream copyright.** Maorik is a derivative work, all of it OFL 1.1:

- **Assistant** (Ben Nathan, Latin by Paul Hunt) — the Hebrew was recut from it onto a single construction; widths and sidebearings are taken from Assistant at the matching axis position.
- **Jost** (indestructible type) — figures, punctuation and the Latin.
- **Source Sans Pro** (Adobe) — reached indirectly, through Assistant's Latin.

`AUTHORS.txt` credits all of them and name ID 0 carries the full chain.

**Reserved Font Name.** Source Sans Pro reserves `Source`. It is inherited through Assistant, and `Source` appears nowhere in this family's name or in any of its name records. Neither Assistant nor Jost declares an RFN of its own. Flagging it so the inherited notice in name ID 0 and `OFL.txt` is not a surprise.

**AI disclosure.** AI assistance (Claude) was used substantially in this project, and per the checkbox above I am disclosing it rather than leaving it to be inferred:

- **Design decisions are mine.** The construction — the superellipse at n = 2.16, Jost's measured aspect, the stroke ladder, letter height held at 545 across the axis, the rule that the box comes from Assistant at the matching weight — were my calls, argued out and recorded in `documentation/DECISIONS.md`.
- **AI did the engineering and the conformance work**, and some of it touches the design: re-deriving all 252 mark anchors per master so the niqqud stay centred at every weight; grafting the 74 GF Latin Core codepoints from Jost; reversing contour direction; the vertical metrics; the name table and STAT; converting the two masters to the UFO sources in `sources/`; and the repository itself.
- Happy to go into more detail on any of it.

**Axis note.** The axis runs 250–700. The lightest named instance is Light at 300, not ExtraLight, because the GF axis registry places ExtraLight at 200 and this axis does not reach it — the drawn master at 250 is intact and reachable by dialling, it simply is not named. Happy to extend the axis to 200 instead if you would prefer a named ExtraLight.

**Status.** Fontbakery `check-googlefonts` reports **0 FAIL / 171 PASS** on the packaged family. Remaining WARNs are documented; the two worth naming are the inherited `Source` RFN notice above, and an unregistered vendor ID (`MAOR`), which I am registering.

Tagged release: [v1.000](https://github.com/sallemaor-a11y/Maorikfont/releases/tag/v1.000)

**Image:**

Maorik specimen

Contributor guide

Open the contributing guide

Research direction

Start with the linked Maorikfont repository and inspect sources/, documentation/DECISIONS.md, AUTHORS.txt, and the v1.000 release. Run Fontbakery check-googlefonts and review the documented warnings, then confirm the licensing, glyph coverage, naming, metrics, and upstream structure meet Google Fonts requirements before onboarding is complete.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.