From: Felipe Correa da Silva Sanches Date: Mon, 27 Apr 2026 15:22:33 +0000 (+0100) Subject: betaniapatmosin: note v11.002 onboarding + OFL companion commit X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=923a408ea805a8916b3ec4eda3527491dc87fee2;p=thirdparty%2Fgoogle%2Ffonts.git betaniapatmosin: note v11.002 onboarding + OFL companion commit 5-family Betania Patmos set onboarded to google/fonts from huertatipografica/betania-patmos at commit 08c83ac9 in January 2026. Source block was populated by gftools-packager in the v11.002 commit; no corrections needed. Assisted by an AI agent (Claude Opus 4.7 (1M context)) --- diff --git a/ofl/betaniapatmosin/upstream_info.md b/ofl/betaniapatmosin/upstream_info.md index 961ef4745..2ff22f5eb 100644 --- a/ofl/betaniapatmosin/upstream_info.md +++ b/ofl/betaniapatmosin/upstream_info.md @@ -46,3 +46,10 @@ This is the same commit hash used for all Betania Patmos variants. The commit is 1. The METADATA.pb source block is missing the `config_yaml` field. Should it be added? 2. There is also a "BetaniaPatmosInGDL" variant in the upstream repo that was not onboarded to Google Fonts. It may be a companion "guideline" version of "Betania Patmos In", similar to how "Betania Patmos GDL" is the guideline version of "Betania Patmos". + +## Recent upstream/main activity (post-investigation) + +- **2026-01-23** — Emma Marichal, commit [`caf0f148c`](https://github.com/google/fonts/commit/caf0f148c) ("Betania Patmos In: Version 11.002; ttfautohint (v1.8.4.16-eb64) added"): initial onboarding via gftools-packager. Created METADATA.pb with source block referencing `huertatipografica/betania-patmos@08c83ac9` (shared with the Betania Patmos sibling families). +- **2026-01-23** — Emma Marichal, commit [`8fffe23cc`](https://github.com/google/fonts/commit/8fffe23cc) ("update OFL"): same-day OFL.txt update. + +Source block reflects the recorded upstream commit; no corrections needed.