unsloth/studio/frontend/src/i18n
Daniel Han 3c6cae3863 Merge remote-tracking branch 'origin/main' into r6763_mainmerge
# Conflicts:
#	studio/backend/routes/models.py
2026-07-27 02:49:24 +00:00
..
locales Merge remote-tracking branch 'origin/main' into r6763_mainmerge 2026-07-27 02:49:24 +00:00
check-parity.ts Studio: add French, German, Spanish, Hindi, Arabic, Russian and Korean display languages (#7076) 2026-07-14 01:38:04 -07:00
index.ts Studio: add French, German, Spanish, Hindi, Arabic, Russian and Korean display languages (#7076) 2026-07-14 01:38:04 -07:00
locale-store.ts Fix Studio toast close-button positioning (#7142) 2026-07-15 07:43:40 -07:00
messages.ts Fix Studio toast close-button positioning (#7142) 2026-07-15 07:43:40 -07:00
README.md Replace standalone Studio wording with Unsloth (#7221) 2026-07-19 00:47:04 -07:00
types.ts Studio: add frontend i18n support (#5765) 2026-05-27 04:52:16 -07:00

i18n Contribution Guide

  • locales/en.ts is the complete baseline message file.
  • Non-English locale files may be partial. Missing keys must fall back to English at runtime.
  • Use BCP 47 locale tags for new languages, for example zh-CN, pt-BR, ja-JP, and ko-KR.
  • Do not change fallback logic to hide missing translations.
  • Do not add automatic DOM translation, MutationObserver text replacement, or runtime guess-based translation.
  • Preserve interpolation variables exactly, for example {count}, {model}, and {provider}.
  • Keep product and technical names unchanged unless there is an established localized name, for example Unsloth Studio, LoRA, GGUF, and Hugging Face.
  • Keep translation changes small and reviewable. Prefer separate commits for runtime changes, UI migration, and locale text.
  • When adding user-facing Unsloth UI text, add the English message key first and add non-English overrides only when the translation is clear.
  • Run npx tsx src/i18n/check-parity.ts before committing to ensure there are no shape mismatches or placeholder discrepancies in the non-English overlays.