Closed cmyr closed 1 month ago
Noto fonts are doing something a bit clever. To allow seamless migration from their old idiosyncratic build system (which used this kind of config file) to builder2, they use a variant of gftools-builder called notobuilder
; where gftools-builder
has an implicit recipeProvider: googlefonts
, notobuilder
has an implicit recipeProvider: noto
. So they are not expected to build under gftools-builder
, but adding the explicit recipe provider is probably a good idea. At any rate, if anything a Noto bug not a gftools one.
And this key is present in at least some configs, e.g.
https://github.com/notofonts/imperial-aramaic/blob/main/sources/config-sans-imperial-aramaic.yaml and https://github.com/notofonts/takri/blob/main/sources/config-sans-takri.yaml.