If there’s stats for a language, but no l10n file, it should not be silently ignored, as it is now (rWPOR data/stats.js:84-86 (at 8ce0bdb7b3c406d5360e6004ea1c781507f963be)). Options:
- Throw an error, don’t let the portal to be built without all necessary l10n data being available. Unblocking the build is as easy as creating the relevant l10n file with the content {"language-name":"<language name>"}; the language name can be got from various places, e.g. from the project list on Meta (e.g. https://meta.wikimedia.org/wiki/List_of_Wikipedias).
- Show only a warning. This doesn’t break the developer workflow, but it’s easier to overlook.
- Handle the case when there’s no translation, e.g. by using the language code instead of the language name. Ugly, but still better than not showing the wiki at all.
- Remove the language-name message, leaving no required messages (and don’t skip the language if there’s no l10n file). There are zillions of places that contain native language names, why do we force people to manually maintain an n+1st copy for the portal pages on translatewiki.net? language-name-romanized and language-name-romanized-sorted are a bit trickier, but maybe those could be automated as well.
Incident caused by this silent ignorance: T319137
