-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Description
https://github.com/silnrsi/font-bjcree
The BJCree font is a Canadian Syllabics [Cans] font for the Algonquian family of languages. It was originally designed in conjunction with the Naskapi community in the 1990s. All the Algonquian language family languages that use Unified Canadian Aboriginal Syllabics are covered by the BJCree glyph inventory.
The name of the font does not pass fontspector's naming convention. However, the name was established over 20 years ago, is the language community’s preference, and can’t reasonably be changed. Victor Gaultney and Dave Crossland discussed this and Dave agreed we should keep BJCree.
Release:
https://github.com/silnrsi/font-bjcree/releases/tag/v7.000
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
- 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
- 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
- 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 (direct link)
- The repo has the Google Fonts preferred upstream repo structure
- I have read, agree with, and comply with, the full Google Fonts contributing requirements
- I will maintain the repository and participate in the onboarding process (addressing, solving, and responding to issues, merging pull requests, etc)
Image:

Metadata
Metadata
Assignees
Labels
Type
Projects
Status