Manage Translations Using the Multi-Language Panel

With the node-level Translations tab in the Designer you can enter translations for words or phrases on individual nodes in a logicnet. However, LogicNets recommends using the Multi-Language panel functionality instead, as it allows content developers to apply translations across projects up to the workspace level.

The panel shows all unique keys for the current logicnet, the current project, or the entire workspace. It provides tools to search for, modify, delete, import, and export translations. The layout of the panel is as follows:

The panel displays translation keys and their corresponding text and location where the key is being used. When a key is used in multiple locations, the system displays each location. When the key changes, the system changes the color of the row, making it faster for you to recognize similar keys.

1. When you double-click on a row the Designer navigates to the key's location.
2. Use the input field in the key column to filter on a specific key or partial key.
3. You can use the text column to filter for specific text. The system displays HTML text in raw syntax, meaning the system displays and allows searching on styling and formatting tags. The ‘used by’ column shows in short format the location in which the key is used. The format is as follows: <project>/<folder>/<folder>.../<logicnet name> | <node and field>.
   
   When a key still exists in the translation tables but is not used by any node, the system displays <NONE>. This provides information on unused keys you might want to remove from the system.
4. To quickly clear all filtering, click the Reset filters button.
5. To edit the translation text, check the checkbox next to one or more rows and click the Edit button.

   

   Use the checkboxes to show/hide the descriptions and to display empty translations. Use the up/down triangles or click on the header to collapse/expand a key.
6. To remove translation keys, check one or more rows and click the Delete button. The system will display a popup asking you to confirm the deletion

   

   In this popup, the system displays English text associated with the translation key. If you delete a translation key, the system removes the text from all locations where that key is used. Note: When the same key is used in multiple places within the same project, you do not need to check all rows for that key. The system will remove all translations linked to that key in that project. However, to delete the same key in another project you must delete the key in each project.
7. To limit the number of keys displayed in the tab, you can use one of the following three methods:
   • Selecting Current view displays the keys associated with the nodes you have selected in the Designer. If you select a logicnet, the system displays the translation keys in that logicnet.
   • Selecting Current project displays all translation keys in the selected project. 
   • Selecting Workspace displays all keys from all projects in the workspace, allowing you to find duplicate text across multiple projects to increase reusability of the translation keys.
8. When you change a selection in the Designer tree, the system only refreshes the panel when you click the Reload view button to update the table. This ensures the system does not change your view unexpectedly.
   
   When you click the Refresh button, the system performs a quick scan of all projects and updates the translation key indexes. This is useful when you have imported a new project, for example. 
   
   When you click the Sync button the system starts the ‘sync’ functionality, updating all text that differs from the original and ensuring translation key consistency. Note: Sync only operates on the project level. You must sync for each project.
9. Using the Import button, you can import a comma-separated values (CSV) file with translation keys to update the translations in a project.

   

   Click Choose File to select a file to import and then click Upload. If the system detects a conflict/the text in the project was updated after the text in the CSV file, it displays an error message like the following:

   

   You can decide for each conflict which text the system should use: the one in the project/Designer or the one from the imported file.  Once the import process completes, the system displays an import summary:

   

   If there are no conflicts, the system displays the following message

   

   You cannot undo an import after it is complete and importing triggers the system to perform a sync of the translation keys. Note: Importing only applies to the current selected project.
   • Click the Select button to individually choose which text to use. When you are finished, click the Individual button.
   • To use all data from the import file, click the Overwrite button. To keep the original text of the conflicted key, click the Keep button.
   • Clicking the Cancel button stops the import and retains the original translations. 
10. To export all translations in a project, click the Export button.

    

    • Choose all the languages you want to export.
    • Click the Exclude unused keys checkbox to prevent the system from exporting keys that are not used in the project.
    • Click the Download button to start the export and save the generated CSV file in your default download location or your desired location.
11. You can also use the Download button to store the current filtered data into a comma separated file. This file cannot be imported and is different from the export functionality.