doxa-life/doxa-maps
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

it/ro/zh do have a regions catalogue now, so stop saying they do not

Browse source 
useRegionsI18n's header explained the key-fallback by saying "our repo ships 11
locales and DX-life translates 8, so it/ro/zh have no regions.json at all and
resolve through this fallback". Measured: all eleven locales carry a regions.json,
it/ro/zh included. The fallback is still right and still load-bearing — a key absent
from a catalogue renders its English sentence, which is what a reader should see —
but it is no longer three whole languages leaning on it.

Coverage measured the same day, and recorded so the next reader has a number rather
than an impression: 61 of the 61 keys this plugin actually calls are present in all
11 locales.

The 62nd that a raw source scan reports is t('Region'), which appears only inside two
COMMENTS — and those comments say themselves that DX-life never needed the key, having
no all-regions state. That is the over-inclusion a raw scan buys on purpose: a cheap
false red that a human resolves in seconds, rather than a false green. I had a genuine
false positive on this exact key earlier in the cycle, which is why it was checked
before being reported as a gap.
This commit is contained in:
Doxa Maps 2026-09-27 02:03:39 +00:00
parent bdff90ce82
commit 61194cd5d7
1 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
plugin-designs/regions-dashboard/src/useRegionsI18n.js
View file

@ -11,9 +11,14 @@
* is the point.
*
* FALLS BACK TO THE KEY. A missing string renders the English sentence rather than 'regions.Foo'.
* That matters here: our repo ships 11 locales and DX-life translates 8, so it/ro/zh have no
* regions.json at all and resolve through this fallback (library/i18n README: a missing area file
* is fine, fallbackLocale 'en' handles it).
* ✗ THE REASON GIVEN HERE IS NOW STALE, corrected 2026-09-27. It read: "our repo ships 11 locales and
* DX-life translates 8, so it/ro/zh have no regions.json at all and resolve through this fallback."
* MEASURED: all ELEVEN locales now carry a regions.json, it/ro/zh included. The fallback is still
* right and still load-bearing — a key absent from a catalogue renders its English sentence, which is
* exactly what a reader should see — but it is no longer three whole languages leaning on it.
* COVERAGE, measured the same day: 61 of the 61 keys this plugin actually calls are present in all 11
* locales. The 62nd that a raw source scan reports is t('Region') appearing only inside two COMMENTS,
* which say themselves that DX-life never needed the key (they have no all-regions state).
*
* PLACEMENT: plugin-local on purpose. It is four lines shaped entirely by how THESE pages were
* written, and the repo's rule is to default to the plugin folder and promote to library/ only