Translating a package
After exporting and downloading a package via Translations wizard, you can proceed to translate it.
The zip file contains the files to be translated. You can share these files (or the zip) with the party doing the translations for you, or you can translate the content yourself.
A couple of things to keep in mind when translating the content:
• All files inside the package have the extension .json.
• The structure inside the file must remain unchanged or this will result in import failures.
• The extension of the files (json) must remain the same.
• Inside the json files, you should only translate the text entry:
"text" : "<text to be translated>"
• If the translatable entry is: "text" : null, do not translate null, but leave it as is.
• The zip contains a file called package_info.json.
In this file, you must translate the following content:
"metadata" : {
"code" : "<enter a three-letter acronym>",
"language" : "<enter a two-letter language code>",
"country" : "<enter a two-letter country code>",
"variant" : "",
"default" : "<Not translated>",
"backupLanguage" : "",
"description" : "<enter a language description>"
"code" : "<enter a three-letter acronym>",
"language" : "<enter a two-letter language code>",
"country" : "<enter a two-letter country code>",
"variant" : "",
"default" : "<Not translated>",
"backupLanguage" : "",
"description" : "<enter a language description>"
 | This information must match with the target language that you are going to import, or the file will not be imported. |
• Regarding "packageName", it is recommended to provide a clear an unique description so that you will be able to easily identify the job in the elements list.
• Save the translated files as a zip file (best practice: prefix it as Imp_ (short for Import) to indicate the direction). You can proceed to import the package.