05-22-2009 02:15 AM
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
Solved! Go to Solution.
05-25-2009 10:14 AM
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
05-26-2009 01:46 AM
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:
06-03-2009 01:21 AM
06-08-2009 08:35 AM
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
06-08-2009 08:48 AM
When you run the code, what you see is absolutely correct.
The problem is in the preview of the UI Localizer Utility: if you
06-08-2009 09:06 AM
Hi Vix,
it seems to be a bug.
I'll write a paper and submit it to R&D.
Thanks for your help! 🙂
05-01-2013 06:43 PM
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.
05-02-2013 12:07 AM - edited 05-02-2013 12:08 AM
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"? )
05-02-2013 11:37 AM
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.