LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

UI Localizer preview: possible bug?

Solved!
Go to solution

In the CVI 9.0 (and 9.0.1) UI Localizer there's a Preview feature that I suppose should give a quick preview of the User Interface localization.

But I've noticed that if in the *.uir file a string has a 'Native' charset, the UI Localizer preview is wrong if the local language has a different charset, even if I select this charset in the Local Language box.

 

For example, if you load the supplied \apps\localui\intgraph project and you add the Russian language, you can use the UI Localizer to successfuly localize the panel (selecting Local Language >> Russian) when the program is executed. The Localizer Preview is wrong, and shows "strange" charactersinstead of russian ones...

But if you set the string charset to Russian in the *.uir file, the Preview works fine...

I did the same test also for Chinese, and the behaviour is the same.

 

Is this an expected situation, or is this a bug?

 

Thanks

Vix
-------------------------------------------
In claris non fit interpretatio

-------------------------------------------
Using LV from 7
Using LW/CVI from 6.0
0 Kudos
Message 1 of 13
(4,873 Views)

Hi Vix,

 

I don't think that it is an expected situation. However when I can find the example that you talked in your post?

 

I try to replicate your problem but my preview works fine.

 

M

Matteo Brunella
Application Engineer
NI Italy
0 Kudos
Message 2 of 13
(4,847 Views)

Hi M,

I simply modified the /samples/apps/localui/intgraph CVI 9.0.1 project, adding the Chinese and Russian language.

Anyway I attach the example I modified, so you can try to reproduce this behaviour...

I don't know what the chinese and russian characters mean... I simply copy/paste some chars from the web, because I only want to did some tests ...

 

I also attach two images:

  • preview.png is what I see in the UI Localizer preview (with Local Language set to GB2312)
  • executable.png is what I see when I launche executabel and selecy Chinese
Vix
-------------------------------------------
In claris non fit interpretatio

-------------------------------------------
Using LV from 7
Using LW/CVI from 6.0
Download All
0 Kudos
Message 3 of 13
(4,840 Views)
Has someone had a look at this behaviour?
Vix
-------------------------------------------
In claris non fit interpretatio

-------------------------------------------
Using LV from 7
Using LW/CVI from 6.0
0 Kudos
Message 4 of 13
(4,777 Views)

Hi Vix,

 

I run your code and I think that what I see is correct. Which is the correct steps to reproduce your issue?

 

Thanks

 

M

Matteo Brunella
Application Engineer
NI Italy
0 Kudos
Message 5 of 13
(4,725 Views)

When you run the code, what you see is absolutely correct.

The problem is in the preview of the UI Localizer Utility: if you

  1. load the GUI
  2. select the Local charset to GB2312
  3. load the Chinese dictionary 
  4. press the Open >>> button, the Chinese fonts aren't displayed in the correct wayin the preview
I've been able to reproduce this behaviour over different PCs, both with an Italian and an English version of WinXP Pro SP2
Vix
-------------------------------------------
In claris non fit interpretatio

-------------------------------------------
Using LV from 7
Using LW/CVI from 6.0
0 Kudos
Message 6 of 13
(4,721 Views)
Solution
Accepted by topic author vix

Hi Vix,

 

it seems to be a bug.

 

I'll write a paper and submit it to R&D.

 

Thanks for your help! 🙂

Matteo Brunella
Application Engineer
NI Italy
0 Kudos
Message 7 of 13
(4,718 Views)

In review of the sample intgraph.cws program,  I see that the UI localizer is useful for the static GUI.  However it  would be of even more interest for this sample to add at least two additional controls to the UI.  These would be a numeric string control for user input, and a text message control for string output.  This would allow us to see  the the code mangement (and possibly any file management) that allows the user to be able to type a string to the input control with echo in the selected foreign language, and where the application could then re-echo the same string to the message string control in the selected foreign language.  I would appreciate it if someone can expand on this.

0 Kudos
Message 8 of 13
(3,858 Views)

CVI hasn't the ability to dinamically translate text from one languge to another. The UI localizer is usefult for the programmer to translate static labels on the panels/controls and no more than this.

 

(BTW what's a "numeric string control"? )



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 9 of 13
(3,852 Views)

Sorry for the typo.  Change 'numeric string control' to just 'string control'.  I realize the limited scope of the User Interface Localizer utility.  But another real challage in foreign language translation is how to manage runtime output messaging and keyboard import in the selected foreign language context.  For basic starters, how do you display error messages in the selected foreign language?  I am interested samples and practices for runtime.   NI  supplies us with the ANSI C multibyte characters library, but there are no examples how we should use them or provide us hint of additional SDK tools to provide a solution for something like the addition of  the two controls that I mentioned for the intgraph.cws sample.   Any direction here would help.  Thanks.

0 Kudos
Message 10 of 13
(3,840 Views)