Spanish TestStand Operator Interface

[JoeTestEngineer]

Has anyone translated the Teststand 3.1 versions of the INI files in Spanish? Thank you in advance

[Ray.R]

Maybe I do not understand what you are trying to achieve...

I don't know why you want to translate the ini file to Spanish.  You can create a User Interface with messages in any language that you like.  I am assuming that it is the User Interface that you would like in Spanish (or any language), and not the development environment.

Can you elaborate?

Thanks,
RayR

[Dennis_Knutson]

I'm sure that what he wants is a spanish translation of the ini files in the \Language\English folder. Having a Spanish folder of these files will allow you to go to the Localization option in Station Options and change languages so that all menu items, etc. are in a different language (development and UI). I'm looking for the same thing to save a bit of time.

[Ray.R]

The way I have solved this in the past is by calling the message with a token.  The token contains the language that the same message appears in.  So for instance, if I have a message that describes how the test is setup, then it opens the appropriate file and the token points to the language of choice.

I have a dll in TestStand that handles all message displays.  I pass parameters which points to the file with the messages, the token for the language and a pointer to which line to display (for multi-line / screen / popup messages).

Lets say the file is "UUT-setup.txt"

UUT-setup.txt

[English]

Prepare test fixture by....

Insert UUT into test fixture...

Configure this and that...

[French]

Veillez preparer le...

Inserez la carte dans le system d'essais...

Veuillez configurer ceci et cela...

[Spanish]

....

...

[END]

[Dennis_Knutson]

Well, a mechanism already exists in TestStand for that and that is with the ini files in the language folder. For example, the UIControlOperatorInterfaceStrings.in has TESTSTAND_OPERATOR_INTERFACE = "TestStand Operator Interface". By using the ResStr() function, just the category and tag have to be specified. You can create your own custom language files and they can be used to add or replace existing strings. I plan on creating custom ini files in English and Spanish but I would like to save some time if the existing files were already translated by someone. At one time, TestStand shipped with a set of language files in Japanese. That was probably fine for development systems but for deploying to contract manufacturer's, other languages would be much more useful.

[JoeTestEngineer]

Dennis has the right idea.... I need the translation of the ini files in the \Language\English folder. We also have a database that stores test application messages based on an error code that is a primary key. It is really the TestStand controls that I have interest in. I have also found that these controls do not support selecting the color which is a huge deficiency. Especially since the work around that NI posted in the knowledge base says not to use TestStand controls. This requires additional software development that I don't have time for right now. Without the translation this feature isn't real useful. .NET ties this type of language support directly to the regional settings defined on the computer. This makes alot of sense to me.  

Hope these controls get some focus in the beta going on now.

[Ray.R]

Thanks Dennis,

All this time we took a different route.  This is the better approach.  I learned something good today 🙂