Add Viriya #11262

Font Project Git Repo URL:

https://github.com/pnfo/sinhala-unicode-fonts (family sources: sources/Viriya/, release v1.001)

Super short description of the Font Family:

Viriya (විරිය, Pali for "energy") is a narrow Sinhala display typeface for headings, posters and signs.

Designer: Pushpananda Ekanayake. He drew the design for a legacy (pre-Unicode) Sinhala encoding. The Path Nirvana Foundation, a US non-profit, converted it to Unicode with full OpenType Sinhala shaping and releases it under OFL 1.1, by written agreement with him. The agreement grants a worldwide, permanent, irrevocable right to modify, rename and release the Unicode version under the OFL. We can provide the signed written agreement to Google Fonts if needed.

Notes for review:

• Sinhala has only five families on Google Fonts. This is one of three families submitted together from the same repo: Saddha, Seela and Viriya, each in its own issue.
• The glyph set and Sinhala OpenType features are built on Abhaya Libre (OFL, no RFN). They cover conjuncts, touching letters (bandi akuru), rakaransaya, yansaya, repaya, and the Pali forms needed for Tipiṭaka text. All 81 Sinhala code points are supported.
• The Latin is adapted from Noto (OFL) and covers GF Latin Core plus the Pali romanisation letters.
• The fonts are built from UFO sources with gftools builder. The build is checked against our reference fonts: 0 differences in glyph outlines and in HarfBuzz shaping of about 15,000 Sinhala test strings.
• Vertical metrics: typo = hhea, line gap 0, with a line height of 128% of the UPM. This is needed for the tall Sinhala vowel signs above and below the letters.
• Fontbakery (googlefonts profile, with METADATA.pb) reports 0 FAILs apart from description/min_length. That one is a false positive in fontbakery 1.1.0: there is no DESCRIPTION file, and the check reads fontbakery's own label for METADATA.pb as the description. Draft METADATA.pb and ARTICLE.en_us.html are in documentation/metadata/viriya and documentation/article/viriya.

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
• I confirm that by 'entire font project', no "plus" or "pro" or other larger version of the project exists as a retail font anywhere
• 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
• 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)

AI disclosure: an AI coding assistant (Claude) helped write the conversion and build scripts. No glyph outlines were generated by AI. All letterforms are Pushpananda Ekanayake's drawings, or come from the OFL upstreams Abhaya Libre and Noto.

Image: