1. Fix locales that don't meet Core, list below. 2. Add unit test to forbid locales that don't meet Core.
in v41, Items < Core Either ⓒ default_content or ⓒ country_data; neither requires language knowledge, and are reasonably easy to do. Worst case with the artificial ones is we give a small number obtained from Wikipedia or by a quick search, eg 10 for Lojban, 100 for Ido, see also https://en.wikipedia.org/wiki/Volap%C3%BCk_Wikipedia#Statistics . For archaic, 1 unless we know better.
I don’t have a strong opinion about the constructed or historic languages – but we should find experts to fill in the missing information for Hmong Njua [hnj], Tai Dam [blt] and Kenyang [ken].
Steven R. Loomis February 4, 2025 at 8:07 PM
need to move code from the coverage chart out into a utility so that it can be part of a test.
Mark Davis February 4, 2025 at 7:54 PM
Edited
If they don’t get done, then remove them.
Annemarie Apple 🍎 April 4, 2024 at 5:20 AM
Bulk moving all issues to the next version which aren't in component type: brs, charts, docs, docs-spec
1. Fix locales that don't meet Core, list below.
2. Add unit test to forbid locales that don't meet Core.
in v41, Items < Core
Either ⓒ default_content or ⓒ country_data; neither requires language knowledge, and are reasonably easy to do. Worst case with the artificial ones is we give a small number obtained from Wikipedia or by a quick search, eg 10 for Lojban, 100 for Ido, see also https://en.wikipedia.org/wiki/Volap%C3%BCk_Wikipedia#Statistics . For archaic, 1 unless we know better.
First pass:
Code
Name
Speakers
en_Shaw
English (Shavian)
1 in GB
hnj
Hmong Njua
100,000 in Laos
jbo
Lojban
10 in US
io
Ido
100 in US
blt
Tai Dam
699,000 in Vietnam
prg
Prussian
50 in Poland
ken
Kenyang
65,000 in Cameroon
vo
Volapük
200 in ZZ
gez
Ge'ez
1 in Ethiopia?