Contact
Newsletter
Schedule Consultation

Localizing Dynamic Contents

  • To provide localized dynamic contents, the following steps are required:
  • Export the JSON file in the desired source language.
  • Preparation of the JSON file in Across, if necessary
  • Translate the JSON file into the desired target languages in Across.
  • Import the localized JSON files.
  1. To provide the file, proceed as follows:
  2. Open the Localization page in the administrator area of crossTerm Now.
  3. From the drop-down list, select the language of the JSON file that you would like to use as source language for the localization.
    Attention

    The selected language must match the language of the dynamic content.

  4. Enable the checkboxes for the contents you want to localize.
  5. Click Export and save the JSON file to your hard disk.
    Tip

    If a new page or tab is opened in your browser instead of the save dialog, open the respective menu of your browser and select the entry Save Page As in order to open the save dialog manually. Normally, the file name and format are predefined.

  6. Translate the JSON file as usual via a project in Across and then check out the target files.
    Tip

    If the JSON file contains contents that you do not want to translate, use a workflow that additionally contains the task type Document preparation. During the document preparation, lock the segments not to be translated and subsequently perform the other tasks of the workflow. If you use the same project for the next localization cycle and perform a document update, the previous segment locking will be retained.

    Observe the following naming conventions when checking out the translated JSON file(s):

    Localization language
    File name
    English
    en.json
    German
    de.json
    French
    fr.json
  7. Open the Localization page in the administrator area of crossTerm Now.
  8. From the drop-down list, select the language of the JSON file that you would like to import and click Import.
  9. Import each checked out, localized JSON file individually (per language).

JSON localization files that you import to crossTerm Now are automatically saved to the i18n folder of the program directory of crossTerm Now, e.g. to C:\Program Files (x86)\Across\crossTermNow\App_Data\i18n. As this folder is not changed when crossTerm Now is updated, your individual localization will not be overwritten. Thus, you only need to renew or update the localization of the JSON file when you add new dynamic contents to Across, which you want to provide in localized form in crossTerm Now.