Nicolas Pastorello ec137c6fa5 fix(i18n): label the contact name field with its own key ... The Details tab rendered `t("company")` above the name input, so the panel showed "Company" twice and the name field carried the wrong label — in English as well as Korean. There was no `Contacts.detailView.name` key at all; the call papered over it with `{ fallback: "Name" }`, which next-intl ignores (the second argument is ICU values, not options). Add the missing key to both catalogues, point the label at it, and drop the two decorative `fallback` arguments so the remaining call sites read as what they are.		2026-07-29 13:52:51 -03:00
..
en.json	fix(i18n): label the contact name field with its own key	2026-07-29 13:52:51 -03:00
ko.json	fix(i18n): label the contact name field with its own key	2026-07-29 13:52:51 -03:00