Docs / Teams and workspaces

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:

{ "_status": "machine-translated, needs native review", "_reviewed": [] }
CodeLanguageCatalog
enEnglish (source)apps/web/src/i18n/locales/en.json
esSpanishes.json
frFrenchfr.json
deGermande.json
itItalianit.json
pt-BRPortuguese (Brazil)pt-BR.json
ruRussianru.json
jaJapaneseja.json
koKoreanko.json
zh-CNChinese (Simplified)zh-CN.json
hiHindihi.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) 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:

<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" /> }} />
"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

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

Englishesfrdeitpt-BRrujakozh-CNhi
campaigncampañacampagneKampagnecampagnacampanhaрассылкаキャンペーン캠페인营销活动अभियान
automationautomatizaciónautomatisationAutomatisierungautomazioneautomaçãoавтоматизацияオートメーション자동화自动化ऑटोमेशन
contactcontactocontactKontaktcontattocontatoконтакт連絡先연락처联系人संपर्क
list / segmentlista / segmentoliste / segmentListe / Segmentlista / segmentolista / segmentoсписок / сегментリスト / セグメント목록 / 세그먼트列表 / 细分सूची / सेगमेंट
templateplantillamodèleVorlagemodellomodeloшаблонテンプレート템플릿模板टेम्पलेट
inbox / mailboxbandeja de entrada / buzónboîte de réception / boîte aux lettresPosteingang / Postfachposta in arrivo / casellacaixa de entrada / caixa postalвходящие / почтовый ящик受信トレイ / メールボックス받은편지함 / 메일함收件箱 / 邮箱इनबॉक्स / मेलबॉक्स
workspaceespacio de trabajoespace de travailArbeitsbereicharea di lavoroespaço de trabalhoрабочее пространствоワークスペース워크스페이스工作区वर्कस्पेस
sending providerproveedor de envíofournisseur d’envoiVersanddienstprovider di invioprovedor de envioсервис отправки送信プロバイダー발송 제공업체发送服务商भेजने वाला प्रदाता
routing (policy)enrutamiento (política)routage (règle)Routing (Richtlinie)instradamento (criterio)roteamento (política)маршрутизация (политика)ルーティング(ポリシー)라우팅(정책)路由(策略)रूटिंग (नीति)
sender / domainremitente / dominioexpéditeur / domaineAbsender / Domainmittente / dominioremetente / domínioотправитель / домен送信者 / ドメイン발신자 / 도메인发件人 / 域名प्रेषक / डोमेन
suppression listlista de supresiónliste de suppressionSperrlistelista di soppressionelista de supressãoстоп-лист配信停止リスト수신 차단 목록屏蔽列表दमन सूची
deliverabilityentregabilidaddélivrabilitéZustellbarkeitrecapitabilitàentregabilidadeдоставляемость到達率전달성送达率डिलीवरेबिलिटी
bounce (hard/soft)rebote (duro/suave)rebond (permanent/temporaire)Bounce (hart/weich)rimbalzo (permanente/temporaneo)rejeição (permanente/temporária)отказ (жёсткий/мягкий)バウンス(ハード/ソフト)반송(하드/소프트)退信(硬/软)बाउंस (हार्ड/सॉफ्ट)
spam complaintqueja de spamplainte pour spamSpam-Beschwerdesegnalazione di spamreclamação de spamжалоба на спам迷惑メール報告스팸 신고垃圾邮件投诉स्पैम शिकायत
unsubscribedarse de bajase désabonnerabmeldenannullare l’iscrizionecancelar inscriçãoотписаться配信停止수신 거부退订सदस्यता छोड़ें
open / click ratetasa de apertura / de clicstaux d’ouverture / de clicsÖffnungsrate / Klickratetasso di apertura / di clictaxa de abertura / de cliquesдоля открытий / кликов開封率 / クリック率열람률 / 클릭률打开率 / 点击率ओपन / क्लिक दर
conversionconversiónconversionConversionconversioneconversãoконверсияコンバージョン전환转化कन्वर्ज़न
draft / scheduledborrador / programadabrouillon / planifiéeEntwurf / geplantbozza / programmatarascunho / agendadaчерновик / запланирована下書き / 予約済み임시 저장 / 예약됨草稿 / 已计划ड्राफ़्ट / शेड्यूल
API keyclave de APIclé d’APIAPI-Schlüsselchiave APIchave de APIAPI-ключAPI キーAPI 키API 密钥API कुंजी
webhookwebhookwebhookWebhookwebhookwebhookвебхукWebhook웹훅Webhookवेबहुक
two-factor authenticationverificación en dos pasosauthentification à deux facteursZwei-Faktor-Authentifizierungautenticazione a due fattoriautenticação em duas etapasдвухфакторная аутентификация2 段階認証2단계 인증双重身份验证दो-चरणीय प्रमाणीकरण
sign in / sign outiniciar / cerrar sesiónse connecter / se déconnecteranmelden / abmeldenaccedi / escientrar / sairвойти / выйтиログイン / ログアウト로그인 / 로그아웃登录 / 退出登录साइन इन / साइन आउट
owner / admin / member / viewerpropietario / administrador / miembro / lectorpropriétaire / administrateur / membre / lecteurInhaber / Admin / Mitglied / Betrachterproprietario / amministratore / membro / visualizzatoreproprietário / administrador / membro / leitorвладелец / администратор / участник / наблюдательオーナー / 管理者 / メンバー / 閲覧者소유자 / 관리자 / 멤버 / 뷰어所有者 / 管理员 / 成员 / 查看者मालिक / एडमिन / सदस्य / दर्शक
sandboxsandboxsandboxSandboxsandboxsandboxпесочницаサンドボックス샌드박스沙盒सैंडबॉक्स
warm-upcalentamientopréchauffageAufwärmphaseriscaldamentoaquecimentoпрогревウォームアップ워밍업预热वार्म-अप
trigger / step / conditiondisparador / paso / condicióndéclencheur / étape / conditionAuslöser / Schritt / Bedingungtrigger / passaggio / condizionegatilho / etapa / condiçãoтриггер / шаг / условиеトリガー / ステップ / 条件트리거 / 단계 / 조건触发器 / 步骤 / 条件ट्रिगर / चरण / शर्त
thread / reply / forwardconversación / responder / reenviarconversation / répondre / transférerUnterhaltung / antworten / weiterleitenconversazione / rispondi / inoltraconversa / responder / encaminharцепочка / ответить / переслатьスレッド / 返信 / 転送스레드 / 답장 / 전달会话 / 回复 / 转发थ्रेड / जवाब / फ़ॉरवर्ड
archive / snoozearchivar / posponerarchiver / mettre en attentearchivieren / zurückstellenarchivia / posticipaarquivar / 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).