---
title: "Dashboard translations"
description: "The dashboard (apps/web) is available in 11 languages. English is the source; the other catalogs were machine-translated and need review by native speakers."
url: https://onesend.email/docs/translations/
---
# Dashboard translations

The dashboard (`apps/web`) is available in 11 languages. English is the source; the other catalogs were
machine-translated and **need review by native speakers**. Each translated catalog says so in its metadata:

```json
{ "_status": "machine-translated, needs native review", "_reviewed": [] }
```

| Code | Language | Catalog |
|---|---|---|
| `en` | English (source) | `apps/web/src/i18n/locales/en.json` |
| `es` | Spanish | `es.json` |
| `fr` | French | `fr.json` |
| `de` | German | `de.json` |
| `it` | Italian | `it.json` |
| `pt-BR` | Portuguese (Brazil) | `pt-BR.json` |
| `ru` | Russian | `ru.json` |
| `ja` | Japanese | `ja.json` |
| `ko` | Korean | `ko.json` |
| `zh-CN` | Chinese (Simplified) | `zh-CN.json` |
| `hi` | Hindi | `hi.json` |

People choose a language in the user menu (**Language**) or on the **Account** page. The choice is saved in the
browser (`localStorage` key `onesend.locale`); without a choice the dashboard follows the browser's languages
(`pt-PT` → Portuguese (Brazil), `zh-TW` → Chinese (Simplified), anything unsupported → English). Switching reloads the
page. Emails, templates and API responses are not translated: only the dashboard's own text is.

## How it works

- `src/i18n/index.tsx`: `t(key, vars)` returns a string, `<T k vars tags />` renders a message with React elements in
  it, `tDynamic()` looks up keys built at runtime, `formatList()` joins lists. Keys are typed from `en.json`, so a
  missing or misspelled key fails `tsc`.
- `src/i18n/message.ts`: a small ICU MessageFormat subset (arguments, `plural`, `selectordinal`, `select`, `#`,
  `<tag>…</tag>`, ICU apostrophe quoting). Plural categories come from `Intl.PluralRules`, so Russian gets
  one/few/many and Japanese, Korean and Chinese need only `other`.
- English is bundled; every other catalog is a separate chunk, loaded before the app modules (`main.tsx` → `boot.tsx`).
- `src/lib/format.ts`: numbers, percentages, money, dates and relative times through `Intl` with the active locale.
- Fonts: Inter has no CJK or Devanagari glyphs, so `styles.css` sets per-language system font stacks
  (Hiragino/Yu Gothic, PingFang/Microsoft YaHei, Apple SD Gothic Neo/Malgun Gothic, Kohinoor/Nirmala UI, with Noto
  fallbacks). Nothing extra is downloaded.

### Catalogs of dashboard extensions

A dashboard extension (see [Extensions](https://onesend.email/docs/architecture/extensions/)) keeps its own catalogs in its package, in
`locales/<code>.json`, with the same languages and the same rules. They are merged into the dashboard's at run time:
the English one with the bundled source, the others when that language loads. A key belongs to one catalog set (an
extension's keys are not in `apps/web/src/i18n/locales`), and inside the extension `t()` and `<T>` come from its
own `src/i18n.ts`, typed with both sets of keys. `npm run i18n:check -w @onesend/web` checks every set.

### Writing UI code

Every user-facing string goes through `t()` or `<T>`; add the English text to `en.json` first:

```tsx
<Button>{t('common.save')}</Button>
<Field label={t('accounts.displayName')} />
toast.success(t('accounts.connected', { email }));
<T k="campaigns.scheduledFor" vars={{ date: dayDate(at) }} tags={{ b: <strong />, link: <Link to="/campaigns" /> }} />
```

```json
"inbox.selected": "{count, plural, one {# conversation selected} other {# conversations selected}}",
"campaigns.scheduledFor": "Sends on <b>{date}</b>. <link>Change the schedule</link>"
```

Rules: one key per sentence (never concatenate translated fragments), plurals with ICU instead of `n === 1 ? '' : 's'`,
numbers and dates through `lib/format.ts`, no `'en-US'`. Keep untranslated: product and provider names, code, commands,
environment variables, header names, DNS record types, URLs, example addresses and `{{template_variables}}` (write them
as `'{{name}}'` so the ICU parser treats the braces as text). Server error messages are shown as the API sends them.

## Checks

```bash
npm run i18n:check -w @onesend/web   # catalogs + hard-coded JSX text
npm test -w @onesend/web             # the same checks, plus parser and rendering tests
```

The check fails when:

- a key from `en.json` is missing from a locale, is empty, or a locale has a key `en.json` does not have;
- a translation's `{placeholders}` or `<tags>` differ from the English message, or the message does not parse;
- JSX contains hard-coded text: text children, or string literals in `title`, `aria-label`, `placeholder`, `label`,
  `alt`, `description`, `hint` and similar props. Code-like text (`<code>`, `<Kbd>`, example addresses, URLs,
  identifiers, DNS record types and brand names) is skipped. For a deliberate exception, put `i18n-ignore` in a
  comment on the line or the line above, or add `"path/File.tsx: exact text"` to `src/i18n/hardcoded-allowlist.json`.

## Contributing translations

Native-speaker review is the most useful contribution.

1. Pick a language and an area of the dashboard (keys are grouped by page: `campaignEditor.*`, `contacts.*`, `common.*`).
2. Run the dashboard in that language (`npm run dev:web`, then **Language** in the user menu) and look at the screens
   while you read the catalog, so each string is judged in context.
3. Edit `apps/web/src/i18n/locales/<code>.json`. Change only values, never keys. Keep every `{placeholder}`, every
   `<tag>…</tag>`, the ICU structure (`{count, plural, one {…} other {…}}`; add `few`/`many` where your language needs
   them) and the `#`. Use a typographic apostrophe (’) rather than `'`, which ICU treats as a quote before `{`, `}` and `<`.
4. Follow the glossary below so a term is the same everywhere. If a term in the glossary is wrong, change it everywhere
   in the catalog in the same pull request.
5. Add the key prefixes you reviewed to `"_reviewed"` (for example `["common", "campaignEditor"]`). When a whole catalog
   has been reviewed, change `"_status"` to `"reviewed"`.
6. Run `npm run i18n:check -w @onesend/web` and open a pull request. Mention which screens you checked and at what width:
   long translations must not break buttons, tabs, tables or dialogs at 375 px and 1440 px.

### Style

- Concise UI register, sentence case where the language uses it, no exclamation marks.
- Address the user the way well-known software in your language does: Spanish *tú*, French *vous*, German *Sie*,
  Italian *tu*, Portuguese (Brazil) *você*, Russian *вы* (lowercase), Japanese です/ます for sentences and plain nouns
  for labels, Korean 합니다/하세요체, Chinese 你, Hindi आप.
- Buttons are verbs (German infinitive: *Speichern*; French infinitive: *Enregistrer*; Russian infinitive or imperative
  as in current Russian software: *Сохранить*).

### Glossary

| English | es | fr | de | it | pt-BR | ru | ja | ko | zh-CN | hi |
|---|---|---|---|---|---|---|---|---|---|---|
| campaign | campaña | campagne | Kampagne | campagna | campanha | рассылка | キャンペーン | 캠페인 | 营销活动 | अभियान |
| automation | automatización | automatisation | Automatisierung | automazione | automação | автоматизация | オートメーション | 자동화 | 自动化 | ऑटोमेशन |
| contact | contacto | contact | Kontakt | contatto | contato | контакт | 連絡先 | 연락처 | 联系人 | संपर्क |
| list / segment | lista / segmento | liste / segment | Liste / Segment | lista / segmento | lista / segmento | список / сегмент | リスト / セグメント | 목록 / 세그먼트 | 列表 / 细分 | सूची / सेगमेंट |
| template | plantilla | modèle | Vorlage | modello | modelo | шаблон | テンプレート | 템플릿 | 模板 | टेम्पलेट |
| inbox / mailbox | bandeja de entrada / buzón | boîte de réception / boîte aux lettres | Posteingang / Postfach | posta in arrivo / casella | caixa de entrada / caixa postal | входящие / почтовый ящик | 受信トレイ / メールボックス | 받은편지함 / 메일함 | 收件箱 / 邮箱 | इनबॉक्स / मेलबॉक्स |
| workspace | espacio de trabajo | espace de travail | Arbeitsbereich | area di lavoro | espaço de trabalho | рабочее пространство | ワークスペース | 워크스페이스 | 工作区 | वर्कस्पेस |
| sending provider | proveedor de envío | fournisseur d’envoi | Versanddienst | provider di invio | provedor de envio | сервис отправки | 送信プロバイダー | 발송 제공업체 | 发送服务商 | भेजने वाला प्रदाता |
| routing (policy) | enrutamiento (política) | routage (règle) | Routing (Richtlinie) | instradamento (criterio) | roteamento (política) | маршрутизация (политика) | ルーティング（ポリシー） | 라우팅(정책) | 路由（策略） | रूटिंग (नीति) |
| sender / domain | remitente / dominio | expéditeur / domaine | Absender / Domain | mittente / dominio | remetente / domínio | отправитель / домен | 送信者 / ドメイン | 발신자 / 도메인 | 发件人 / 域名 | प्रेषक / डोमेन |
| suppression list | lista de supresión | liste de suppression | Sperrliste | lista di soppressione | lista de supressão | стоп-лист | 配信停止リスト | 수신 차단 목록 | 屏蔽列表 | दमन सूची |
| deliverability | entregabilidad | délivrabilité | Zustellbarkeit | recapitabilità | entregabilidade | доставляемость | 到達率 | 전달성 | 送达率 | डिलीवरेबिलिटी |
| bounce (hard/soft) | rebote (duro/suave) | rebond (permanent/temporaire) | Bounce (hart/weich) | rimbalzo (permanente/temporaneo) | rejeição (permanente/temporária) | отказ (жёсткий/мягкий) | バウンス（ハード/ソフト） | 반송(하드/소프트) | 退信（硬/软） | बाउंस (हार्ड/सॉफ्ट) |
| spam complaint | queja de spam | plainte pour spam | Spam-Beschwerde | segnalazione di spam | reclamação de spam | жалоба на спам | 迷惑メール報告 | 스팸 신고 | 垃圾邮件投诉 | स्पैम शिकायत |
| unsubscribe | darse de baja | se désabonner | abmelden | annullare l’iscrizione | cancelar inscrição | отписаться | 配信停止 | 수신 거부 | 退订 | सदस्यता छोड़ें |
| open / click rate | tasa de apertura / de clics | taux d’ouverture / de clics | Öffnungsrate / Klickrate | tasso di apertura / di clic | taxa de abertura / de cliques | доля открытий / кликов | 開封率 / クリック率 | 열람률 / 클릭률 | 打开率 / 点击率 | ओपन / क्लिक दर |
| conversion | conversión | conversion | Conversion | conversione | conversão | конверсия | コンバージョン | 전환 | 转化 | कन्वर्ज़न |
| draft / scheduled | borrador / programada | brouillon / planifiée | Entwurf / geplant | bozza / programmata | rascunho / agendada | черновик / запланирована | 下書き / 予約済み | 임시 저장 / 예약됨 | 草稿 / 已计划 | ड्राफ़्ट / शेड्यूल |
| API key | clave de API | clé d’API | API-Schlüssel | chiave API | chave de API | API-ключ | API キー | API 키 | API 密钥 | API कुंजी |
| webhook | webhook | webhook | Webhook | webhook | webhook | вебхук | Webhook | 웹훅 | Webhook | वेबहुक |
| two-factor authentication | verificación en dos pasos | authentification à deux facteurs | Zwei-Faktor-Authentifizierung | autenticazione a due fattori | autenticação em duas etapas | двухфакторная аутентификация | 2 段階認証 | 2단계 인증 | 双重身份验证 | दो-चरणीय प्रमाणीकरण |
| sign in / sign out | iniciar / cerrar sesión | se connecter / se déconnecter | anmelden / abmelden | accedi / esci | entrar / sair | войти / выйти | ログイン / ログアウト | 로그인 / 로그아웃 | 登录 / 退出登录 | साइन इन / साइन आउट |
| owner / admin / member / viewer | propietario / administrador / miembro / lector | propriétaire / administrateur / membre / lecteur | Inhaber / Admin / Mitglied / Betrachter | proprietario / amministratore / membro / visualizzatore | proprietário / administrador / membro / leitor | владелец / администратор / участник / наблюдатель | オーナー / 管理者 / メンバー / 閲覧者 | 소유자 / 관리자 / 멤버 / 뷰어 | 所有者 / 管理员 / 成员 / 查看者 | मालिक / एडमिन / सदस्य / दर्शक |
| sandbox | sandbox | sandbox | Sandbox | sandbox | sandbox | песочница | サンドボックス | 샌드박스 | 沙盒 | सैंडबॉक्स |
| warm-up | calentamiento | préchauffage | Aufwärmphase | riscaldamento | aquecimento | прогрев | ウォームアップ | 워밍업 | 预热 | वार्म-अप |
| trigger / step / condition | disparador / paso / condición | déclencheur / étape / condition | Auslöser / Schritt / Bedingung | trigger / passaggio / condizione | gatilho / etapa / condição | триггер / шаг / условие | トリガー / ステップ / 条件 | 트리거 / 단계 / 조건 | 触发器 / 步骤 / 条件 | ट्रिगर / चरण / शर्त |
| thread / reply / forward | conversación / responder / reenviar | conversation / répondre / transférer | Unterhaltung / antworten / weiterleiten | conversazione / rispondi / inoltra | conversa / responder / encaminhar | цепочка / ответить / переслать | スレッド / 返信 / 転送 | 스레드 / 답장 / 전달 | 会话 / 回复 / 转发 | थ्रेड / जवाब / फ़ॉरवर्ड |
| archive / snooze | archivar / posponer | archiver / mettre en attente | archivieren / zurückstellen | archivia / posticipa | arquivar / adiar | архивировать / отложить | アーカイブ / スヌーズ | 보관 / 다시 알림 | 归档 / 稍后提醒 | संग्रहित करें / स्नूज़ |

Keep in English everywhere: OneSend, provider and product names (Gmail, Postmark, Amazon SES…), SPF, DKIM, DMARC,
MX, TXT, CNAME, BIMI, MTA-STS, SMTP, IMAP, POP3, API, SDK, CLI, MCP, URL, HTML, CSV, JSON.

## Adding a language

1. Add it to `LOCALES` in `apps/web/src/i18n/locales.ts` (code, native name, English name, `ltr`/`rtl`).
2. Copy `en.json` to `<code>.json`, set `"_status": "machine-translated, needs native review"` (or `"in progress"`)
   and translate. The check reports every key that is still missing.
3. If the script needs other fonts, add a `:root:lang(<code>)` font stack to `apps/web/src/styles.css`. For a
   right-to-left language set `dir: 'rtl'`; `<html dir>` follows it, and layouts should use logical properties
   (`ms-`/`me-`, `ps-`/`pe-`, `start`/`end`).
