To localize front panels of LabVIEW programs, you need to translate all front panel strings. To use ?Export VI Strings? and ?Import VI Strings? has many disadvantages:
- If you modify the VI, importing a previously exported and translated text file results in errors.
- The exported text file has a structure close to XML. If you want to give it a translator, you would need a parser that would allow you to extract only the translatable strings.
- It is not possible to change the strings at runtime, because the you can not import the textfile if the VI is running.
- Each VI of your application has its own textfile. If strings appear in many VIs (like ?cancel? of a cancel button), you have to translate them in each textfile.
- Run Time Menu (RTM) items are not included in the exported textfile.
The ?translate.vi? allows you to localize your front panel with none(!) of the disadvantages listed above!
How to use:
- Insert the ?translate.vi? into the block diagram of the VI you want to localize. Be sure, that the ?translate.vi? will be executed at the beginning of your VI. For default settings nothing has to be connected to the ?translate.vi?. Now start your VI.
- In the folder of your VI the translation file ?strings.txt?, that contains all strings of your VI, was created. Open this file with a editor (e.g. Wordpad) and add one or more columns, delimited with tabulators, of translated strings.
- Connect the language index to the ?translate.vi? you want. If you want to use the strings of the first column of the translation file (original language) use language index 0, if you want to use the strings of the second column of the translation file use language index 1 and so on. Now run the VI. That's it!!
How it works:
It extracts and searches for the front panel strings and RTM items (dependent on the translation options and menubar parameters) in the translation file (a tabulator delimited spreadsheet file of strings, each line contains a string to translate and each column contains a different language) and replaces them with the strings of another column of this file (dependent on the language index parameter).
Lines in the translation file beginning with // (double slash) are ignored and can be used as comment lines to insert version information etc. into the translation file. See ?string.txt? as an example for a translation file.
The translation file can be a different one for each VI or the same for all (or some) of them, dependent on the translation file parameter.
If you add front panel objects to your VI, all new strings will be appended to the translation file automatically, after you start the VI the next time. Afterwards you need only add the translation(s) of the new string(s) to the translation file
If you are interested in a demoversion please write a short e-mail to email@example.com.