DEV Community

Rasmus Larsson
Rasmus Larsson

Posted on

Translation System Requirements

Thank you so much to @perty for this handy list.

  1. Translations are editable by non-developers (and thus have a different deploy cycle than development work).
  2. Obvious when translations are missing.
  3. Obvious when a text is no longer in use anywhere.
  4. Some locales have their own messages.
  5. Some locales may not have all messages so no translation is needed for those messages.
  6. There is a single source of truth, i.e. only one place for the translations.
  7. Optionally, history of changes. Who and when changed a translation.
  8. Fallback to a default language when translation is missing.
  9. Contextual UI that shows the translator where the translation is used.
  10. Translation suggestions based on prior work (within the project, but also using translation services)

Sentry image

Hands-on debugging session: instrument, monitor, and fix

Join Lazar for a hands-on session where you’ll build it, break it, debug it, and fix it. You’ll set up Sentry, track errors, use Session Replay and Tracing, and leverage some good ol’ AI to find and fix issues fast.

RSVP here →

Top comments (1)

Collapse
 
perty profile image
Per Lundholm

You're welcome 😀.

Sentry image

See why 4M developers consider Sentry, “not bad.”

Fixing code doesn’t have to be the worst part of your day. Learn how Sentry can help.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay