From fe80021ab1b24df6793e1a9519b6d62396774fad Mon Sep 17 00:00:00 2001
From: James Antill <james.antill@redhat.com>
Date: Apr 09 2020 17:07:48 +0000
Subject: Merge #951 `Fonts: document the “I need some font files to be present to function (any will do)”`


---

diff --git a/guidelines/modules/ROOT/pages/FontsPolicy.adoc b/guidelines/modules/ROOT/pages/FontsPolicy.adoc
index aa50aed..9f501ce 100644
--- a/guidelines/modules/ROOT/pages/FontsPolicy.adoc
+++ b/guidelines/modules/ROOT/pages/FontsPolicy.adoc
@@ -177,6 +177,8 @@ For compatibility reasons, OpenType font files MAY be exposed outside `/usr/shar
 * [x] Non-font packages SHOULD NOT require specific font packages, and leave font selection to end-users,
 ** except when the packaged software actually relies on those specific font packages,
 ** except for convenience font metapackages, as defined in <<Assembling different-family font packages: font metapackages>>.
+* [x] Non-font packages SHOULD require `font(:lang=en)` when they fail in the absence of system fonts,
+** hardcoding specific font families is not future-proof.
 * [x] Non-font packages MAY require font packages by name, when relying on specific on-disk font file paths,
 ** ie when software is not `fontconfig`-aware,
 ** however, there is no obligation for font packagers to keep those paths stable between releases. Font file formats are flexible, making any on-disk file layout temporary. Converting applications to fontconfig use is best.