• You maintain a distinct set of scripts for each language
• You work with one set of scripts, covering all languages within the script

Here we describe the 2nd possibility.  

An advantage of the 2nd  approach is  that you can simplify your maintenance work: You can split each script into a language independent part in which you delete and rearrange fields, set defaults etc, and a language specific part in which you rename fields or add new texts.

A disadvantage is that you have to use the technical field names in the language independent part.

Furthermore, the users cannot work with the "Low speed connection (Reduced Network Traffic)", since the technical field names are not sent to the frontend in this case. This parameter is set in the SAP logon screen:

How to proceed:

In GuiXT profile you set the "No language key" option:

If you work with a guixt.ini file, the parameter is

NoLanguageKey   Yes

GuiXT now searches the scripts without a language key, e.g. instead of SAPMF05A.E0100.txt it reads the file SAPMF05A.0100.txt. In addition, in the screen elements you will now find the technical field name in the first column:

With a mouse click on a screen element you can copy the technical field name into the clipboard, and insert it into your script with Ctrl+V .

When you record an InputScript, GuiXT will also generate the technical field names:

In your scripts  you can start with a language independent part, addressing all screen elements with their technical name.  Example:

The resulting screens in the 3 languages:

Within the language specific parts you can also work with the technical field names: