Requirements for a language to be used are too soft and do not guarantee quality for websites
Current situation
A language is qualified if all of these happen:
-
languages
is inconfig.yaml
; - If there's no content file to translate, then there must be at least one i18n string translated;
- If there's at least one file to translate, then there must be at least one file qualified.
A content file is qualified (and only generated then) if one of these happen:
- There's at least one translation in frontmatter;
- There's no content to translate (i.e. there's nothing in the file other than the frontmatter);
- More than half (0.5) of the content is translated.
However, content files can be generated even in languages that are not qualified (e.g. Russian on 25years-k-o, or Russian and Traditional Chinese on eco-k-o) because such languages do not have any translation for i18n strings. These files are redundant, not used anywhere.
Approach
It was agreed in okular-kde-org!19 (merged) that a banner should be shown for each page that is insufficiently translated, and there's no need to change how a language is qualified.
Edited by Phu Nguyen