1c7104e90b
library/lists/lists.json carried one English label per list, so every surface
that showed a list's name printed English in every locale (reported by upg100,
which worked around it inside the packet's own strings).
- A `lists` catalogue area, library/i18n/locales/<lc>/lists.json: a label and a
definition for each of the five lists, in all 11 locales.
- listLabel(id, t) / listDefinition(id, t) in peopleGroupList.js resolve
lists.<id>.label through the caller's translator (useI18n's t, tStatic, or any
key -> string), accept ids and aliases ('700'), and fall back to the
registry's English. The module still imports no i18n runtime, so it stays pure
and testable in Node.
- The registry's labels are now documented as the English fallback only, and the
doxa list gains the definition its catalogue entry has.
- check:list-prop-unit (24 cases, was 17): the Arabic and German catalogues come
through, a missing translator or a raw key falls back to English, the English
catalogue must equal the registry word for word (a drifted registry label fails
it, naming the list), and every locale must carry both fields for every list.
- documentation/reference-universal-props.md: read names through listLabel.
Headless: list-prop-unit, i18n-parity, i18n-never-translated,
no-free-identifiers and universal-props pass. No consumer calls listLabel yet
(the packet has its own strings), so nothing renders differently until one does.
22 lines
799 B
JSON
22 lines
799 B
JSON
{
|
||
"doxa": {
|
||
"label": "2000 计划：DOXA 服侍的族群",
|
||
"definition": "DOXA 服侍的族群，以其实时名单为准"
|
||
},
|
||
"unreached": {
|
||
"label": "7000 计划：未得之民族群",
|
||
"definition": "IMB 失丧优先级 0–2（前沿、先锋或扩展中的未得之民：福音派少于 2%）"
|
||
},
|
||
"frontier": {
|
||
"label": "4700 计划：前沿族群",
|
||
"definition": "IMB 失丧优先级 0（前沿未得之民：福音派 0.1% 或更少）"
|
||
},
|
||
"frontier-500k": {
|
||
"label": "700 计划：人口 50 万或以上的前沿族群",
|
||
"definition": "IMB 失丧优先级 0，且人口至少 50 万"
|
||
},
|
||
"unengaged": {
|
||
"label": "尚无人参与的未得之民族群",
|
||
"definition": "IMB 失丧优先级 0–2，且参与状态为：无人参与"
|
||
}
|
||
}
|