This details how to work with custom language translations in Omniscope Evo, editing the translations using Omniscope Classic and the editedLanguages.iok file. If you have an Omniscope Classic license, this is the best way to edit language data.
Also see the main guide to custom translations including using a CSV to edit translations, as well as an overview of the system.
Omniscope Classic and Omniscope Evo are two separately licensed products available within one installation bundle. Once installed, the Classic approach for editing language data (via the Omniscope Classic settings menu and the "editedLanguages.iok" file in the user home directory) can be used to edit language data for both Omniscope Classic and Omniscope Evo.
- Install the latest version of Omniscope from https://visokio.com/evo/.
- Remove any previous editedLanguages.iok file from your user profile / home directory (e.g. C:\Users\YourName\editedLanguages.iok), after checking you've already sent any previous translation efforts back to us.
- Start Omniscope Classic; we'll use this to edit languages
- Start Omniscope Evo; we'll use this to preview the results. Navigate to the part of the app you're focusing on, e.g. create a new file, link some data, and open the report.
- In Classic, choose "Settings > Language > Edit translations"; this will create a fresh new 'editedLanguages.iok' in your user profile, including phrases from the latest Evo user interface.
- Make some edits to the language or country variant column, e.g. "Fr" or "fr_FR". Save the IOK, leave Omniscope Classic open.
- Refresh the page in Evo. You may need to change your language setting in Omniscope Evo via the flag icon or 3-dots menu in the Evo browser interface.
- Repeat steps 6 and 7 until you've finished a batch of work.
- Send us the editedLanguages.iok file, clearly indicating which columns have been edited.
Now continue reading the main guide to custom translations for wider information about the languages file and phrases structure. Also see the older knowledge base guide to translating Omniscope Classic.
Warning: if you have previously created a 'languages.csv' file in the omniscope-server folder, you must remove this for the above approach to take effect.