Add JyunsaiKaai
- 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/quangdinh-aimuahanhk/jyunsaikaai
**Super short description of the Font Family:**
Based on Iansui with modified glyphs to meet Hong Kong standard.
**Requirements:**
By opening this issue, I confirm the project meets the following requirements:
- The entire font project is available in a Github repository (repo) and licensed under the [OFL](https://openfontlicense.org/open-font-license-official-text/)
- The source files are available in the repo
- 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.
- 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.
- The family name is unique according to [namecheck.fontdata.com](https://namecheck.fontdata.com/)
- 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.
- The font supports at least the Google Fonts 'Latin Core' glyphset from [github.com/googlefonts/glyphsets](https://github.com/googlefonts/glyphsets) ([direct link](https://github.com/googlefonts/glyphsets/blob/main/data/results/txt/nice-names/GF_Latin_Core.txt))
- The repo has the [Google Fonts preferred upstream repo structure](https://googlefonts.github.io/gf-guide/upstream.html)
- 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)
- I will maintain the repository and participate in the onboarding process (addressing, solving, and responding to issues, merging pull requests, etc)
**Image:**
Contributor guide
Research direction
Start by reviewing the linked JyunsaiKaai repository and the Google Fonts contributing requirements listed in the issue, including OFL licensing, source availability, naming, glyph coverage, and upstream structure. Done means the font meets those requirements and the submitter participates in onboarding and maintenance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- content
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100