Localization Export/Import
Localization Text Export
 | "Localization text export / import" |
1 Open the export dialog via the main menu and select the Localization export from the list.
2 Select the objects that you want to export.
3 Choose Reference and Target languages for the export.
4 Check to not export any texts that already have status “Final” in the Target language.
5 Set a password to lock all cells apart from the columns “Target Language (New)” and “Text State”, to protect the document from unintentional changes.
6 Uncheck to not automatically open the exported Excel file.
7 Choose file name and target folder for export.
8 You can save your selected export options as a Preset and load them again for later exports. Please note that the object selection will not be saved.
The export can now be used to localize missing entries for the target language, or do an editing or proof-reading pass. When finished the file can be re-imported into articy:draft X.
Localization Text Import
To open the Import Wizard click the main menu button 9 and select “Import” 10 or use the keyboard shortcut Shift + Ctrl + I
To open the Import Wizard click the main menu button 9 and select “Import” 10 or use the keyboard shortcut + + I
The first step of the import process is to select the Localization export file (.xlsx) you want to re-import 11.
When clicking on "Next" the selected file is parsed. If it is a valid file, the Settings are displayed.
12 The Import language is detected automatically. You can use it as a check that the correct file is getting imported.
13 If the text states (In Progress, Final, Outdated) from the Excel file are supposed to be taken over into articy, check this option.
14 Otherwise you can select a state from the drop-down menu and enforce it for all imported data.
15 MULTI-USER If any partition claiming conflict occurs you have to option to Abort import and change nothing or to Only import non-conflicts, skip conflicts.
16 With this option you can decide how to handle import conflicts. Abort import and change nothing cancels the entire import process as soon as a conflict is detected. Only import non-conflicts, skip conflicts will lead to a partial import if conflicts are found. Manually resolve conflicts presents you a list of conflicts and you can decide for each conflict how it should be handled.
17 Uncheck to not create an excel file with all skipped entries during an export. It is highly recommended to use this option to keep the overview after a partial import!
18 If Manually resolve conflicts is selected and conflicts occur during import this window will appear. It can be resized to fit longer strings.
19 On the left side the conflict is shown. Each conflict is of a certain type, here it is a conflict in the Reference Text.
20 Then the conflict for this entry is displayed in detail. In this example it results from a change to the primary language after the export. What is in the exported Excel and in the project no longer matches.
21 On the right side the text that is supposed to be imported is displayed.
22 You can select a resolution for each conflict. You can skip importing this entry, if the change to the Reference text in the project no longer fits the localization that has been done, or you can import the text with a selected state. If you have a lot of conflicts to cover, you can make these selections quickly with F1 to F4 – using the hotkeys will set the resolution and move to the next conflict.
23 Here you see the total amount of conflicts found and which conflict is displayed currently. With the navigation you can go to the first, previous, next, or last conflict in the list.
24 Finish processes all your selected conflict resolutions and completes the import.
25 Cancel will automatically set the resolution for all conflicts to Skip and completes the import.
18 If Manually resolve conflicts is selected and conflicts occur during import this window will appear. It can be resized to fit longer strings.
19 On the left side the conflict is shown. Each conflict is of a certain type, here it is a conflict in the Reference Text.
20 Then the conflict for this entry is displayed in detail. In this example it results from a change to the primary language after the export. What is in the exported Excel and in the project no longer matches.
21 On the right side the text that is supposed to be imported is displayed.
22 You can select a resolution for each conflict. You can skip importing this entry, if the change to the Reference text in the project no longer fits the localization that has been done, or you can import the text with a selected state. If you have a lot of conflicts to cover, you can make these selections quickly with fn + F1 to fn + F4 – using the hotkeys will set the resolution and move to the next conflict.
23 Here you see the total amount of conflicts found and which conflict is displayed currently. With the navigation you can go to the first, previous, next, or last conflict in the list.
24 Finish processes all your selected conflict resolutions and completes the import.
25 Cancel will automatically set the resolution for all conflicts to Skip and completes the import.
If you selected Only import non-conflicts, skip conflicts or skipped entries for Manually resolve conflicts and have checked Create Excel file with skipped entries in the Import settings, then an <!your_filename>-skipped.xlsx will be created at the same location as the original export file. This file lists all entries that were skipped in the import process.
It is possible to make another import with this skipped file and then decide again how to treat the conflicts. You could do a fast first import for all strings without any conflicts, so people can continue to work on the project, then take your time looking over the conflicts with the help of the skipped file and do another import based on that file later.
If the import is complete, a result window opens that provides all necessary information regarding the import process. It shows the source file for the import 26, name and target folder for the skipped file, if applicable 27, as well as the statistics of the import process 28. This entire view is also saved as a log file 29.
Please note that the Localization Export/Import functionality comes from a plugin. If you cannot find the Localization export in the export dialog, please check the Plugin Manager if the “Localization & Voiceover Import/Export Plugins” need to be enabled. If you are working on a multi-user project, please talk to your server administrator, as they might have disabled the plugin for all users.
If you are missing any specific functionality, you can customize the Localization export with the help of the free Macro Dev Kit. You can download the source code of the plugin here.
If you are missing any specific functionality, you can customize the Localization export with the help of the free Macro Dev Kit. You can download the source code of the plugin here.