A way to translate UI

[Chris_Dong]

I found a method from a book which told that we can open the VI which you want to localize, and click the "tools-->advance-->export strings", after you export the strings, you will get an XML file, then you can translate accordingly, and even you can set font property in this file;

After translate is done, you can using "tools-->advance-->import strings", then generate executive file again, all user interface is changed now.

[billko]

Using native LV XML, it's going to be slow.  It will be faster to show captions on your control and indicators and change them with values taken from (for example) a config file.  However, there are third party XML parsers that are literally hundreds of times faster than native LV XML.

[zou]

---

@billko wrote:

Using native LV XML, it's going to be slow.  It will be faster to show captions on your control and indicators and change them with values taken from (for example) a config file.  However, there are third party XML parsers that are literally hundreds of times faster than native LV XML.

---

Import XML is a one time thing in edit mode.  So how fast is not an issue.

[billko]

---

@zou wrote:

---

@billko wrote:

Using native LV XML, it's going to be slow.  It will be faster to show captions on your control and indicators and change them with values taken from (for example) a config file.  However, there are third party XML parsers that are literally hundreds of times faster than native LV XML.

---

Import XML is a one time thing in edit mode.  So how fast is not an issue.

---

Oh, I assumed it was going to be done on-the-fly at runtime.  Silly me never thought about doing it at development time.  I should've been clued in by the mention of "tools-->advance-->export strings".

[zou]

Import XML might work okay for Chinese, Japanese, or Korean.  As phrases in these languages are usually shorter then in English.

But for European languages, e.g. Russian, could have phrases long /much long then English.  Then you will have problem like phase got cutoff, or overlay on other ctrls.

Multi-language GUI is not just label/caption.  Boolean text is also very important.  Most use case:  OK, Cancel.

Other thing like menu bar, error messages, status, pull down menu, results table, etc. also need to be translated.

Toggle between English and other languages at the runtime is very important for LabVIEW programmers.  So during debug, we can understand  the error message / status etc.