https://bugzilla.redhat.com/show_bug.cgi?id=1532523
--- Comment #10 from Nicolas Mailhot nicolas.mailhot@laposte.net --- PS Droid Fallback is a high coverage – low quality compromise. As a rule the same glyphs in locale-specific Droid parts will always be higher quality.
That’s why the package tries to ship as many locale-specific bits as possible and Droid has a complex fontconfig file that mashes everything in a single droid family making sure fallback is only used when there is no better Droid part available.
Well, the fontconfig file is not complex as in hard, it’s complex as a bit involved and requiring enough packager involvement to understand the fontconfig logic instead of cargo-culting default config file templates with no understanding.
Noto should probably benefit from the same setup, as it has the same characteristics (wide encoding font spread over many files that need merging in a single Noto font family by fontconfig instead of forcing users to assemple them manually)