Hello everybody,
Context
we are developing a test automation solution and do also support executing VIs for that purpose.
To gather information about the interface of a VI, I am using "PrintVIToText".
So I can later on parameterize it properly, when executing it.
Recently, I encountered a VI containing chinese characters.
This lead to unexpected results in the file created by "PrintVIToText", that our parser for these files was not able to handle properly.
After some research I found out that reading the file using "GB18030" or "GB2312" lead to the correct results.
But this obviously broke compatibility to other character sets.
There seems to be no indication of which encoding to use for the file.
Maybe this export function is not the right way to do it at all.
Our LabView connector has been around for quite a few years, but has been working perfectly until this point.
Question
Is there any way to find out how to interpret the exported text representation?
Can I somehow tell LabView to use a certain encoding for the export?
Is there an alternative approach to find out about the interface of a VI?
Kind regards,
Lukas
