Normally, you should not check the "Include label type constants’" option. As an example, you can use the option for special ASCII characters above 127.
Probably, you only need to translate the GUID's that the company own.
Click on "Extract languages" and wait until VIGO6 is done with the extraction. At the end of the extraction, select where to put the language file ("LanguageList.vtr"). The default path is “Documents\LanguageList.vtr”.
Now you can send the file and the translator program to the person who will translate the texts.
You can now begin to translate the texts. When you change a text, its background changes to light blue.
In case a language GUID for a text already exists, you can see a dark blue color for the “=>” symbol
You can show line numbers by:
In addition, you can zoom the width of each language column:
You can also search for a text within the translation file. As a result, you can see the line with the text you search for, as the first entry in the editor window. It has a blue or white color, as you can see below. But, if there are fewer lines ‘after’ the line, this can't be shown as the first line. You may need to scroll through the languages to find the text.
Along the way, and when you are done, the system will save changes in the same - or another file.
Now you have to return the file to the sender, for import back into VIGO6. (Only the exporter can do the import.)
To summarize, you have loaded translations into your catalogue.
Next time you build and download the program that holds the visulization, you will then include the new translations.