Importing/exporting languages


To import one of our predefined languages or your own custom language file navigate to Configuration->Languages and Regional settings->Languages tab and click Import language button.

New window will open in which you can simply import one of the included languages by clicking the Import button next to the language you want to import. At the bottom of this list you will also find an option to upload your own language file in .csv format.



You can export each imported language to a CSV file directly from the Languages tab. Simply click on the Export button in the Actions column.


Exported file format

After you click on the Export button language file will be exported into a .csv file and automatically downloaded to your PC. Name of the exported file will be: pap_[language code].csv so for example if you export en-US language, name of downloaded file will be pap_en-US.csv. The file has to be opened in UTF-8 format and it is using semicolon as separator. The first line of the file contains header, next eleven lines contain language parameters(metadata). These lines should not be deleted or moved else where.

Example of header and language metadata for en-US language file:
"lang_author";"Quality Unit";"M";"";"T";"N"
As you can see there are six columns in the exported file:
  1. source -> source language text or constant. This value should not be changed!
  2. translation -> translated language text. This is what you should translate.
  3. type -> Server (S) / Client (C) / Both (B) – means where this text belongs. It should not be changed.
  4. module -> module where the text belongs (for example affiliate, merchant, etc.). If the text exists in multiple modules, it is empty. You can use it to determine for example only texts from affiliate panel. This value should not be changed for existing translations.
  5. status -> status of translation of the text: New or not translated (N), Deprecated (D), Translated (T). You can edit it and use it to keep track on what you already translated.
  6. customer -> type of text. If it's text that was added by customer (merchant), the value is Y, otherwise N. This value should not be changed.
Example of a custom translation record in which word License is translated to Lisans.
After you customize translations in your language file, you can import it back to the system. File that is being imported will overwrite the language with the same language code in the system!
NOTE: When creating new translations keep in mind that all translations are case sensitive!