Observation recorded while implementing #8096 (objectui PR objectstack-ai/objectui#4638). Not fixed there — out of that card's scope.
What
The organizations.* key family in packages/i18n/src/locales/ has been renamed from "organization" to "workspace" terminology in en and zh only. The other eight packs (ar, de, es, fr, ja, ko, pt, ru) had just one key — create — followed, leaving the family internally inconsistent.
de.ts:
create: "Workspace erstellen" ← workspace
mine: "Meine Organisationen" ← organization
title: "Organisationen"
heading: "Ihre Organisationen"
searchPlaceholder: "Organisation suchen"
new: "Neue Organisation"
current: "Aktuelle Organisation"
Same shape in fr ("Créer un espace de travail" beside "Mes organisations"), ja ("ワークスペースを作成" beside "マイ組織"), and ko / es / pt / ru / ar. For comparison, en and zh are uniform:
en: mine: 'My Workspaces', create: 'Create workspace', title: 'Workspaces'
zh: mine: '我的工作区', create: '创建工作区', title: '工作区'
Why it is worth a card now
These keys render next to each other in one dropdown. After #4638 restores the avatar menu's "My Workspaces" entry, a German user sees Meine Organisationen directly above Workspace erstellen — two names for the same object, one menu, two lines apart. Before that PR organizations.mine was dormant (no call site), so the drift was invisible; it is now on screen in eight locales.
Why the existing gates do not catch it
This is a same-language vocabulary inconsistency, not a missing or stale key, so nothing currently in place sees it:
all-locales-key-parity — every pack has every key, so it is green.check:i18n-drift — compares each pack against changes to the en value; en has not moved recently, so there is nothing to follow.check:i18n-keys — validates that call-site keys resolve and that inline defaultValues match the en pack; the eight non-en packs are not in its comparison set.
Scope
Eight locale files, seven keys each in the organizations family (mine, title, heading, subtitle, searchPlaceholder, new, current, plus emptyTitle / emptyDescription / noMatches which carry the same noun). Worth checking whether the sibling organization.* family (org MANAGEMENT — a deliberately distinct namespace, per the comment between them in en.ts) was meant to follow the rename at all, or whether "organization" is correct there and only the picker family was renamed. That question should be answered before any bulk edit — the two families are separated on purpose.
Filed unlabeled for priority; tagged finding as an observation-class item (cosmetic / terminology consistency, no functional defect).
Observation recorded while implementing #8096 (objectui PR objectstack-ai/objectui#4638). Not fixed there — out of that card's scope.
What
The
organizations.*key family inpackages/i18n/src/locales/has been renamed from "organization" to "workspace" terminology in en and zh only. The other eight packs (ar, de, es, fr, ja, ko, pt, ru) had just one key —create— followed, leaving the family internally inconsistent.de.ts:Same shape in fr (
"Créer un espace de travail"beside"Mes organisations"), ja ("ワークスペースを作成"beside"マイ組織"), and ko / es / pt / ru / ar. For comparison, en and zh are uniform:Why it is worth a card now
These keys render next to each other in one dropdown. After #4638 restores the avatar menu's "My Workspaces" entry, a German user sees
Meine Organisationendirectly aboveWorkspace erstellen— two names for the same object, one menu, two lines apart. Before that PRorganizations.minewas dormant (no call site), so the drift was invisible; it is now on screen in eight locales.Why the existing gates do not catch it
This is a same-language vocabulary inconsistency, not a missing or stale key, so nothing currently in place sees it:
all-locales-key-parity— every pack has every key, so it is green.check:i18n-drift— compares each pack against changes to the en value; en has not moved recently, so there is nothing to follow.check:i18n-keys— validates that call-site keys resolve and that inlinedefaultValues match the en pack; the eight non-en packs are not in its comparison set.Scope
Eight locale files, seven keys each in the
organizationsfamily (mine,title,heading,subtitle,searchPlaceholder,new,current, plusemptyTitle/emptyDescription/noMatcheswhich carry the same noun). Worth checking whether the siblingorganization.*family (org MANAGEMENT — a deliberately distinct namespace, per the comment between them inen.ts) was meant to follow the rename at all, or whether "organization" is correct there and only the picker family was renamed. That question should be answered before any bulk edit — the two families are separated on purpose.Filed unlabeled for priority; tagged
findingas an observation-class item (cosmetic / terminology consistency, no functional defect).