Why does my LabVIEW occasionally display in Chinese?

[falkpl]

I believe this property is private.  This was a fix if was provided several years ago when I first encountered my vi outsourcing (ie font change)

[Paul-D]

Hi everyone, I'm Paul an Applications Engineer at National Instruments

After reviewing this thread today and doing some research, I have followed up with Joe-F to create a CAR for this issue.  The CAR # is 285555

[FlamingYawn]

I just ran into the same problem this morning with LabVIEW 2010 SP1.  I've seen this half a dozen times in the past couple of years.  Restarting LabVIEW has always fixed the problem for me, although it freaks me out whenever I see it.  In my experience it always happens when I'm dealing with the project.  Several of my colleagues have seen this as well, so it is not all that rare.  I sure hope NI gets it figured out soon.  This is definitely not strictly a "Windows" issue.

[_Norm_]

The way I've fixed this is to open a VI reference to the VI that has the messed up BD, set the BDWin.Open property to True, then use 'TRef Traverse for References.vi' with Class Name = 'GObject' and Traverse Target = BD, which will return an array of references to BD objects. Next, pipe the array through a For-Loop and use the 'To More Specific Class' VI with GObject as the target class and use the ClassName property to drive a case structure that you'll use in conjunction with another 'To More Specific Class' to cast the reference to the specific class for the object (i.e. ControlTerminal, CaseStructure, FeedbackNode, SubVI, etc,...). Now, set Label.InterpretAsUnicode and Label.SizeToText to False then set Label.SizeToText to True.

[D_J]

The same thing happened to me at the end of last week - I build an executable from a project that I use regularly, and some of the text in this exe was in Chinese.

I had not knowingly done anything to select unicode.

I noticed on some occassions that some text in the LabVIEW IDE itself was displayed in Chinese.

It is reassuring to know that others have seen the same problem - this executable controls our company's machinery, and it was extreemly unnerving.

David James

[Paul-D]

Hey guys, just as a follow up, my CAR from above was rolled into CAR: 185890 , and this is an issue that our R&D is aware of.

Paul

[falkpl]

Thanks for the CAR.  I first reported this almost 5 years ago, around v8.0 (when the project was added) it is nice to see some action finally.  One thing that could be done in the meantime is to provide a project fixer application for thoese who make the mistake of saving changes before realizing the problem.  As several have noted this can be done with transversing vis and un unicoding the strings.  This will also help people stuck using versions prior to the implementation of the CAR fix (I assume LV2012 if we are lucky).

[falkpl]

Thanks for the CAR.  I first reported this almost 5 years ago, around v8.0 (when the project was added) it is nice to see some action finally.  One thing that could be done in the meantime is to provide a project fixer application for thoese who make the mistake of saving changes before realizing the problem.  As several have noted this can be done with transversing vis and un unicoding the strings.  This will also help people stuck using versions prior to the implementation of the CAR fix (I assume LV2012 if we are lucky).

[Jon_S.]

Hello Everyone,

I want to clear up a bit of confusion about this issue (in fact its two separate issues).

1st Issue:

LabVIEW built applications (Distributed System Manager, Veristand, etc) show Chinese characters after upgrading to a newer version of LabVIEW.  This install could be a patch or a service pack upgrade.  It was reported as CAR 285555 on this forum but it has been closed as a duplicate.  The CAR number to track is 202900.  What is happening is that a file that needs to be replaced during an install is resevered and cannot be replaced.  Because the run time engine doesn't see the correct file it goes to the next language. In this case Chinese.  A simple repair has fixed this issue in most cases.  Also, we believe that this is only caused when the user doesn't restart after installing the upgrade.

2nd Issue:

This is the issue that falkpl reported.  Sometimes after a LabVIEW crash or building an application the internal Unicode flag gets turned on for many of the LabVIEW objects.  This case we have been unable to reproduce after vigorosly attempting to do so.  We are working on implementing a fix that would help the user out after this happens but as of right now we haven't determined what exactly causes this bug.  This CAR has been reported as 185890.  If you expereince this behavior contact NI support.  We will try to help recover your VIs as much as possible.

Both of these issues are set to a high priority and we are taking them seriously.

[magyar]

Here is a new flavor to the same problem.

I was using LabVIEW Help, reading up on the "In Place Element Structure". When I clicked the "Add to the block diagram" button, I ended up with this "CDK_loadPrev_2009_2010.vi"

I  posted this in the hope that it might help narrowing down the number of suspects.