Translate app localization files
Drop your en.json or en.yml and get a new locale file with translated values and identical keys.
Don't upload confidential documents on the free tier. Why?
Adding a language to an app or website usually means translating a locale file: hundreds of short strings under keys your code depends on. Translation tools built for prose tend to mangle keys, quotes and placeholders. DropTranslate parses JSON and YAML properly and translates only the values, so the keys, nesting and order stay identical and the file loads like the original. It is a quick way to get a complete first version of a new locale, which you can then review in the running app.
Review in context
Interface strings are short and depend on context, so a machine translation can pick the wrong meaning for a word. Review the new language in the running app, ideally with a native speaker, before you ship it to users.
Good for
- Creating a first version of a new locale file in one step
- Translating newly added strings for an existing language
- Translating Markdown docs and README files alongside the app
Before you translate
- Search the output for placeholders such as {name}, {{count}} or %s and check they're unchanged.
- Check plural forms: some languages need more forms than English.
- Review short strings in context. A word like Save or Open can be translated in more than one way.
- Check text length in the UI, especially buttons and menus.
Questions
Will keys be translated?
No. Only values are translated; keys, nesting and order stay exactly the same.
Which formats are supported?
JSON and YAML locale files, plus Markdown and HTML for documentation. Gettext PO, XLIFF and platform strings files aren't supported yet.
What about placeholders?
The model is instructed to keep them unchanged, and it usually does. Search the output for your placeholders before you ship.