This procedure is intended to the Customs Authorities (or Road Transport National Associations) to explain how to proceed to request one/all of the 3 eTIR eTIR software applications - eTIR (web) Portal, eTIR Customs (mobile), eTIR Holder (mobile) - to be translated to a new language.
1. Folder structure :
To beginning with, you will need to contact the TIR Secretariat (firstname.lastname@example.org, cc email@example.com) to request the latest version of the Translations.zip file containing a folder (structure) where the 4 “UI label” files are recorded:
For the eTIR web portal, there are 2 files:
- message_en.properties → texts used for email notifications
- en.js → texts used for the web UI (User Interface)
For the mobile apps there are 2 en.json files, one for each of the 2 mobile apps containing the texts used for the mobile UI.
2. File by file translations
Although there are slight variations in the file formats (.properties vs .js vs .json) the general concept is the same (list of key:values).
For each of the 4 files, it requires you to:
- Copy the file replacing the “en” part by the target language (e.g.: “fr” for French, “tr” for Turkish, …) within the same (sub)folder (“message_en.properties” becomes “message_fr.properties”, “en.js” becomes “fr.js”, etc.)
- Update the copied file, for example below ,“en.js” text/JSON file to replace the “values” (part on the right sides) by the translated text.
In the below file, you will find the variable names (in blue below) to be left as they are (used by software as “Label key”) and the variables values (in dark orange below) to be translated by your care.
Note: although most of the variable are there… we may have a few extra added later that we will ask you eventually later to translate.
3. Note on the file format (UTF-8):
It’s important to note that the file are all text files and that they are encoded in UTF-8.
Although this is transparent during the translation exercise, it is important to save the file preserving the UTF-8 encoding to avoid losing special characters.
For this reason, we highly recommend to translate the file in a (rich or simple) text editor (notepad++, VS Code, …) and to avoid MS Words.
For example below, using (the simple text editor) notepad, to make sure to save it with UTF-8 encoding (“Unicode”), upon saving the file we have to do as shown below:
4. Package and return the files:
Once all the variable values updated/translated for the 4 files, kindly return to us the files, ideally in a zip file preserving the folder structure) and we will integrate them to the web and mobile applications and enable the translated languages.
After deployment in SIT or UAT environment, we will create for you an account to verify that the chosen wording “works as expected” in the web/mobile applications (and eventually give you a chance to adjust it if necessary).