Add Chiron Hei HK

[tamcy]

This issue supercedes https://github.com/google/fonts/issues/1842 which I opened in 2019. A lot have changed since then. To avoid confusion, I decide to close that issue and open a new one.

Font Project Git Repo URL:

https://github.com/chiron-fonts/chiron-hei-hk-gf

Note: The original repository is https://github.com/chiron-fonts/chiron-hei-hk, but it doesn't follow the latest repository structure and font file naming as required by Google Fonts. Also the documentation is not compatible as I need to strip the custom axis for the GF version. So I created another repository specialized for GF, which can be seen as some kind of meta-repository. Hope this is OK.

Super short description of the Font Family:

• A typeface for Traditional Chinese users.
• Derived from Source Han Sans CJK HK v2.004. Unlike the HK/TW version which follows the corresponding (voluntary) regional standard, Chiron Hei HK follows some kind of “ad-hoc” standard that is commonly seen in the Traditional Chinese environments (Hong Kong and Taiwan). The glyph forms are usually found in commercial offerings.
• More than 5,000 mappings changed. Among those, about 2,900 glyphs have been revised.
• Integrates the full glyph set of Source Sans 3.
• An italic version is also available, its LGC glyphs are from Source Sans 3 Italic.

Requirements:

I understand that Google Fonts will publish only fonts that matches its requirements, and I can confirm the project meets them (by ticking the cases, or putting x between the square brackets in text mode):

• [x] The entire font project is licensed under the OFL
• [x] There is no "Reserved Font Name" mention in the OFL license
• [x] Family name is unique according to namecheck.fontdata.com
• [x] The font supports at least GF Latin Core glyphset
• [x] The repository respect the upstream repo structure
• [x] The source files are available in the repository
• [x] I read, agree and comply with the full contributing requirements
• [x] I am the author of the font or the author agreed to this submission
• [x] I will maintain the repository

Image:

[RosaWagner]

Same as the other issue, can't access the new repo

[tamcy]

It's public now. Sorry about the glitch!

[chrissimpkins]

Consider upstreaming?

[chrissimpkins]

Consider upstreaming?

We spoke with the Adobe team and there is consensus to ship this as an independent project rather than attempt to upstream into the Adobe project.