Skip to main content

CSV Support

Exporting CSV Files​

There are two ways to export localizations to a CSV file for editing outside of Unity.

The first way to export localizations is to select the Translation Library Asset you want to export, then click on the 'Export...' button to save all localizations to a file. The exported file will also have blank lines for each line of text in the original language which hasn't yet been translated.

The second way is to use the Localization Panel in the EasyTalk node editor. Go to 'Language -> Localization...' to bring up the panel. There you can choose which languages to export translations for prior to exporting by toggling them on or off, then click on the 'Create Localization File...' button.

note

When exporting in the EasyTalk Node Editor, the translations can only be exported from the current Dialogue Asset.

Importing CSV Files​

There are two ways to import localizations from a CSV file into a Translation Library.

One way to import CSV files is to use the inspector 'Import...' button when a Translation Library asset is selected.

You can also import localizations in the EasyTalk Node Editor via the 'Import Localizations...' button in the Language Panel, which can be opened by going to 'Language -> Localization...' in the menu.

CSV Format​

Each localization CSV file has the following columns:

  • id - The ID of the line of text.
  • language - The ISO-639 language code for the text.
  • text - The translated text.

The ID is used to match text from one language to another. For example, text with the 'en' (English) language code and an ID of '37' might have a Japanese translation with the language code 'ja' and the ID of the translated line would also be '37'.

All columns are comma-delimited.