Content Control: Import Translations

Thanks to our Distributor capabilities inside of Content Control, you are now able to import a spreadsheet of translations into your Experiences, in order to quickly translate all of your Text Widgets and links without any manual effort inside of our platform!

Note: As of May 2023, this is only compatible with Experiences made inside of Creator Studio. We plan to have this working with Experiences made inside of the Fastr Frontend Editor later this year.

To get started, click on the Preview & Publish button for the Experience you would like to have translated, followed by the Manage Translations button:

You should then see a Preview of your Experience on the right, with all of the Text Widgets inside of that Experience listed on the left:

From here, you can either automatically translate your Text Widgets (as detailed in another article here) or, import a CSV file that will translate all your Text Widgets and links/URLs to languages of your choosing.

Importing a CSV file

NOTE: Before you start this process, please ensure that your CSV file adheres to the best practices and requirements found at the bottom of this article!

Click on "Drag and drop File or Browse" to select your CSV file off of your computer. After that is done importing, you should see the languages that were in your CSV listed in the highlighted box below:

You can then use the left and right arrows (also highlighted above) to flip between the translated versions of your Experience and Preview each one accordingly.

If everything looks good, you can click Apply Changes to finalize the creation of these translations!

As you might guess, some translations will naturally lead to Text Widgets becoming longer or shorter than you designed them to be in English, and create Experiences that look like this:

If that happens, you can click on Edit Experience in the top right corner to re-size and rearrange the Text Widgets inside of that language's version of your Experience, in order to correct their layout and formatting.

Please contact support@zmags.com with any further questions on this!

Best Practices and Requirements for CSV File Formatting

• File must be saved in a .csv format, specifically the CSV UTF-8 (Comma delimited) (*.csv) format and contain only one sheet [multiple tabs/sheets in an Excel file will not work]
  • You can prepare and edit your file as a regular worksheet, then once it is ready and will not need any more updates, you should save it as the .csv format mentioned above
• Users can now define the default language which should be used when creating a new Experience. This is also called the base language.
  • If not defined explicitly, we use English (en-US) as the default.
  • To make this change, please reach out to support@zmags.com
• File must adhere to the following format:
  • Rows set-up:
    • 1st row: language names, one per column, starting with the base language name in column B (for example: English)
    • 2nd row: Corresponding language code just below the language name in row 1, one per column, starting with the base language code (for Example: en-US in cell B2)
      • A list of language codes can be found at the end of this article
    • 3rd row and on: each piece of text from the design that needs to be translated and its corresponding translation in each column
    • 1st column: Define if you want to translate a link or text. If it’s a text – use keyword “text”, if it’s a link – use keyword “link”.
      • This must be defined for each row. If not, the translation will not work.
      • This can be case-insensitive and will work if you type Link or LINK or link.
  • Cell A1 and A2 will always remain blank.
  • See the following screenshot for a reference of how it should look:

• Each Text Widget in your Experience (whether made from a design file or made from directly inside our Editor) needs to correspond to a row in your translations file.
  • You cannot have multiple rows in your translation file that correspond to one Text Widget in your Experience or vice versa
• Similarly, each URL in your Experience (imported from DT or created from scratch) needs to correspond to a row in the translation file
  • There should only be a single row corresponding to a URL. If more than 1 row is present the translation will not happen.
• Each Text Widget in your design should only contain one type of styling (i.e., you cannot mix and match bold and italic, or different fonts in a text widget you are translating) to allow for matching across the languages
• Each row in your translation file must have a translation entered for all language columns (i.e. one of the languages cannot be left blank)
• Text in your csv file should not have any formatting
• Text in each row of Column B must match exactly your Text Widgets for it to be matched (that includes capitalization, any punctuation, or actual words)
• Links (URLs) in each row of your first columns must match exactly with the link defined in the Experience (including www and https://) for it to be matched and translated.
• Language codes and language names in the translation file need to match exactly the language codes from ISO 639-1 and RFC 5646 formats
  • Language codes and names can be found here: https://docs.aws.amazon.com/translate/latest/dg/what-is-languages.html