Integrate JSON

with Localazy within minutes.

You can translate JSON (JavaScript Object Notation) files with the assistance of machine translation engines (such as Google Translator) and copy-paste the results into your text editor. But this translation option is time-consuming and inefficient.

Considering that JSON is one of the most lightweight data interchange formats, working with it is pretty handy. And the best way to translate JSON files is to use an online translation service, such as Localazy. Localazy serves as TMS and localization suite to help you translate your JSON files effectively. With its help, you can translate multilingual JSON files, JSON5 files, or HJSON files and integrate a Translation Management System (TMS) into your workflow.

To translate JSON files using the Localazy interface, sign up for free and create a new translation project. Once you upload your JSON file, you can add the target language, start translating, and then download the translated files with ease. You can even pre-translate the whole file in JSON format by applying machine translations in bulk. This and many other features make Localazy the ideal tool to produce professional translations.

Localazy is a state-of-the-art translation management platform and localization suite to help you translate your JSON files effectively. Learn more in the Getting Started Guide.

You can use any text/code editor such as Notepad, Sublime Text, and others to open and edit JSON files. Alternatively, use an online editor to edit your JSON files.

However, for JSON files containing strings of texts or translations, you should use Localazy, suitable for managing multiple file formats.

To open and edit JSON files using the Localazy interface, sign up for free and create a new translation project. Once you upload your JSON file, click on the File management tab to view, open and access your file content.

Localazy is a state-of-the-art translation management platform and localization suite to help you translate your JSON files effectively. Learn more in the Getting Started Guide.

Resources #️⃣

CLI: JSON File Format CLI Quick Start - JSON

You can use the Format Conversions feature of Localazy to convert JSON files to over 20 other localizable file formats, including Microsoft Excel, PO and XLIFF.

Begin by signing up for free and creating a new translation project. Upload your JSON files and set up the Localazy CLI with the correct configuration. You can also convert JSON files by navigating to File management section in Localazy, from there, locate your JSON file you wish to convert, click the download icon and select the desired format.

Suppose you have a project where the source file is a JSON file with a row in the format:

"about.moreButton": "Learn more on our website",

When using the Localazy CLI to import to Android with Format Conversions (or when you just try to export the JSON file to Android XML inside the Localazy web platform), you might notice that the format is:

<string name="about_moreButton">"Learn more on our website"</string>

Now, you might think you should delete those start and end quotation marks in the body of the XML row to achieve this result:

<string name="about_moreButton">Learn more on our website</string>

However, you can keep the quotation marks in the Android XML file because it’s a supported construct used to correctly encode white characters that would otherwise be lost in all cases. Quotation marks ensure that the exact form of your strings is preserved after conversion.

In actual use, the text will render correctly on the device.

More information can be found on the Android Developers website: String Resources

You might encounter a situation, when not all keys that are a part of the same structure get downloaded from your Localazy project. Most likely, the issue here is that you have the key both as a single text and also as a structure.

This often happens when you first create a key and later decide to actually change it to an object with multiple subkeys.

So at first, you create a key, e.g.: user.welcome with text “This is a welcome text.”

But then, you decide you want to use a structure such as:

• user.welcome.text => “This is a welcome text.”
• user.welcome.title => “Welcome title”

Supposed it is a nested JSON, then you can’t have both:

{
"user.welcome": "This is a welcome text.",
}

and at the same time use:

{
"user.welcome": {
"text": "This is a welcome text",
"title": "Welcome title"
}
}

Because the same key can not be an object and a text at the same time.

In the future, you can simply prevent this, by using deprecating during upload so old keys are automatically marked as deprecated when they are no longer part of the uploaded file. In your CLI configuration, set deprecate to value project, and all keys missing in the upload batch across whole project will be deprecated.