Agentry 6.1.4 clienttext.ini change language

[Former Member]

Hello community,

in the Agentry Server Version 6.0 we create a translated ClientText.ini copy from the ClientTextBase.ini file and place it in the installation folder from the AgentryServer. So the client texts was translated to the language we used in the clientText.ini.

Now we use the AgentryServer 6.1.4 and do the same with the ClientText.ini but the client have already the english texts. Not the translated from the ClinetText.ini. The Agentry.ini is configured with this parameter: "clientStringsFile=ClientText.ini"

Whats wrong or what can we do to translate the ClientTextBase.

Thanx,

André

[mark_pe · Accepted solution]

Andre,

The golden rule of thumb with respect to localization in Agentry (all the globals, clientText - ini files) is to use the ini files that came with the installation.

You can't simply copy a ClientText.ini from Agentry 6.0 and expect it to work in 6.1.4. The system can detect a discrepancy and it will not pick up the new version (I think this is your issue). The reasoning for this is each time a new server comes out there may be changes: 1) Either something change (libraries) or 2) the syntax changes or 3) some items are deprecated. You can't expect the agentry's ini files to always have the same syntax and use. The best practice in Agentry is not to copy ini from the old into the new but get the changes from the old and apply it to the new (or it may not work).

The plan is always to translate the newest clientTextBase.ini -> clientText.X.ini into the language of choice. We would like to keep clientText.ini as English as this is normally default.

In our SAP Work Manager product designed in Agentry, we have an install available in the Service Marketplace that consist of at least 16 languages (i.e. clientText.es.ini, clientText.de.ini, others) pre-configured and the agentry.ini that has it setup.  All the user has to do is choose the language they need.

If you are designing from scratch your own application, you will have to provide these localization files for your customer.

Also best practice for using localization file is to specify what non-English you want to use as an alias to the localization file instead of just using clientText.ini.

For example if you are using Spanish - the normal name of that is es. So your clientText will be clientText.es.ini.  If you are using French the name of that is fr. So your clientText will be clientText.fr.ini.  You will then specify which language your want to use in your setup in the agentry.ini.

If you do this, you can support multi-language app for your company.  Like if you have a headquarter in Europe and you are a very very big furniture store that sells world wide, you want your mobile app for inventory management for your mobile device to be used on all your big warehouse stores. So all the handhelds they will use in the warehouse will be based on the locality of what they specified their handheld to be.  This localization technique will check the language code for each country (i.e. es, de, fr) and use that same naming convention to find the clientText.X.ini where X is the language code to do the proper conversion.

All of this documented in the agentry language manual for localization on how to set the agentry.ini.

Hope this helps,

Mark Pe

SAP Senior Support Engineer.

[Former Member · Accepted solution]

Thank you Mark.

This was the right thing: "The best practice in Agentry is not to copy ini from the old into the new but get the changes from the old and apply it to the new (or it may not work)."

Very good explanation 🙂

André

[mark_pe · Accepted solution]

Andre,

No problem. Have a good day.

Regards,

Mark