pt 的 detail.concurrentUpdateDescription 在洞前留了裸 "de",插入名词短语时渲染出 "de este registro"(葡语必须缩合成 deste)—— 叶子值无论怎么写都不可能对

[yinlianghui]

现场

ConcurrentUpdateDialog(OCC 冲突对话框)把 detail.concurrentUpdateDescription 按 {{field}} 切成两半,中间粗体渲染 conflict.label || conflict.field:

packages/plugin-detail/src/ConcurrentUpdateDialog.tsx:124
  const descriptionTemplate = t('detail.concurrentUpdateDescription', { field: '{{field}}' });
  const [beforeField, afterField] = descriptionTemplate.split('{{field}}');

pt 包值:

"Outro usuário salvou uma versão mais recente de {{field}} durante sua edição. …"

洞前是裸介词 de 。当 {{field}} 收到的是字段名(Status、Amount)时没问题;但多字段冲突走的是另一支,label 是一个带指示词的名词短语 —— InlineEditSaveBar.tsx:144 传 detail.concurrentUpdateRecordLabel(#3546 切片七刚回填,pt = este registro),于是 pt 用户看到:

uma versão mais recente de este registro durante sua edição
                          ^^^^^^^^^

葡语里 de + este 必须缩合成 deste。de este 是母语者一眼可见的语法错误。

为什么不能在叶子值上修

• 写 deste registro → 渲染成 de deste registro,更糟;
• 写裸 registro(无限定词)→ de registro,语法上说得过去但像机翻;
• de 在外层句子里,而外层句子是既有包值。

同类问题只有 pt 一个包:es de este registro、fr de cet enregistrement、de(与)von diesem Datensatz、ru версию этой записи 都不需要缩合(#3546 切片七的测试里逐包钉了 de 的第三格与 ru 的第二格)。

建议修法(二选一,倾向 A)

A. 改写 pt 的外层句子,让洞前不是裸介词。 例如

"Outro usuário salvou uma versão mais recente do seguinte campo: {{field}} durante sua edição. …"

或把介词挪进从句。改的是 pt 一个既有值,check-i18n-en-drift.mjs 不会红(en 未变),但要在同一 PR 里说明理由。优点:一处修死,叶子值不必迁就语法;缺点:pt 句式与其余九包略有分歧。

B. 让调用点传入已成句的标签。 InlineEditSaveBar 多字段分支不传名词短语,而是传字段名列表(它本来就有 keys.join(', ')),把"这条记录"的措辞交给一个独立的整句 key。优点:所有语言都不再有"洞前介词"的耦合;缺点:改的是行为(用户看到字段名而不是"这条记录"),属产品裁量,且 detail.concurrentUpdateRecordLabel 刚回填十包就会变成死键。

现状已在测试里钉住,不是被忽略

packages/i18n/src/__tests__/residue-namespaces-3546.test.tsx 里有

expect(composed('pt')).toContain('mais recente de este registro');

外加注释说明这是"当前真相"而非笔误,以及修法在外层句子。这一单落地时那条断言必须一起改。

关联:#3546(切片七回填 detail.concurrentUpdateRecordLabel)、#3512(同一族的无 provider 插值缺陷)。

[claude]

Triage: pm:queue — concrete defect, named location, fix directions articulated on the card.

• Anchor (read, not inferred): verified on origin/main @ b750823 — packages/i18n/src/locales/pt.ts:903 still carries the bare preposition (…mais recente de {{field}} durante…), and packages/plugin-detail/src/InlineEditSaveBar.tsx:144 passes the record-label key for the multi-field branch.
• One premise is ahead of main, worth the claimant knowing: 258 个 t() 调用点引用的 key 在任何语言包里都不存在(#3530 守卫首跑实测),其中 8 处直接把 raw key 渲染给用户 #3546 slice 7 has NOT landed — detail.concurrentUpdateRecordLabel is absent from packages/i18n/src/locales/pt.ts and en.ts on main, and residue-namespaces-3546.test.tsx (the current-truth pin this card says must flip) does not exist on main yet. Today the call site's defaultValue: 'this record' fallback means pt users see mixed-language "de this record" — a different render of the same hole defect; the card's exact de este registro arrives when slice 7 lands. The defect and its fix face (the pt outer sentence) are live either way.
• Coordination: slice 7 is in flight with no open PR (worktree stage) and shares pt.ts — claimant must re-read the file and the slice-7 pin at claim time and flip that assertion in the same change.
• Direction (non-binding): A (rewrite the pt outer sentence so the hole is not preceded by a bare de) as the card leans — a single-locale value fix needing no product call. B changes user-visible behavior (field names instead of "this record") and would orphan a freshly backfilled key — if evidence favors B, escalate rather than implement.
• Dedupe: createSafeTranslation 的无 provider 兜底从不读调用点的内联 defaultValue —— 只认自己那张 defaults 表,表里没有就把 raw key 渲染给用户(useDetailTranslation 实测 16 个 key) #3865 mentions the same dialog family but is the provider-less defaultValue helper defect — distinct. No other open card or PR touches this key.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code