09-04-2013 08:50 AM
Hi all,
We are trying to translate a bunch of VI's for a Russian customer. We used the 'Export Strings' function (Tools->Advanced-> Export Strings) to create a list of strings to be translated by the customer. Now that we have the translated strings, we are trying to import the strings using the 'Import Strings' function, but we are failing to display russian characters.
Experimenting with Windows localization, Arial CYR and the encoding of the translated strings file have led to different results, but none looking remotely like russian text.
When viewing the the strings file in any text editor, the russian text is displayed correctly, but when importing in Labview this is the result:
The English VI and russian strings file are attached and any help is kindly appreciated,
Kristof
09-05-2013 07:21 AM - edited 09-05-2013 07:21 AM
Hello Kristof,
Just to make sure;
- Did you follow these steps?
http://digital.ni.com/public.nsf/allkb/541DF6459994868E86257208006D5518?OpenDocument
- Which OS are you using?
Can you copy Russian strings from any text editor to NI LabVIEW (through the Windows Clipboard)?
09-05-2013 08:27 AM
Hi Thierry,
Thank you for your reply. Following the instructions described in your link I was able to display russian text after importing the strings file, but only after changing the font of each control to 'Arial CYR'. Is it possible to do this without changing the font? (A lot of VI's, a lot of controls 🙂 ).
Copying and pasting russian text from any text editor is possible without changing to a cyrillic font.
Thank You,
Kristof V.
09-06-2013 03:23 AM - edited 09-06-2013 03:24 AM
Hello Kristof,
I'm not the expert in fonts, but as far as I know you need a Cyrillic Font to show to be able to show those types of symbols.
As far as I know (just tested a little bit over here while teaching my course) the Arial CYR font can also represent Western European symbols.
So why don't you just use that one as default font.
If you want to change all Captions their Fonts at once you can quite easily do this with the aid of property nodes. (see example in attachment).