![[DE: Softwareanwendung]](/fileadmin/_processed_/6/e/csm_0fdb853798_b5f4b2f545.jpg "© https://ecolotrain.loctimize.com:8080/index.php?id=2489&L=0")
Projects for localising software user interfaces usually involve the translation and adaptation of all user interface elements containing text, as well as the use of software localisation tools (see Software Localisation course 4), which allow the extraction and editing of translatable text in the user interface. Usually project managers or software engineers are responsible for preparing the source files containing the translatable elements of software. The preparation of these files varies depending on the method used for translating and editing the texts, the tools used, the client's requirements, etc. Translators take over the translation of texts into the target language, for which they have to handle – besides the software application itself – graphics, images and icons, user manuals, etc. Sometimes, translators may also work with software engineers to test the software. Both translators and software engineers may also be responsible for resizing menus, dialogues, etc., in order to fit the target texts in the space available.
But, what exactly has to be localised in the user interface?
It should first be noted that a software application consists of program code and program elements. The program code contains the instructions to control the program's performance and functions, and the program elements – also called interaction elements – provide a basis for the user and the program to "communicate". Both software component parts contain elements which have to be localised. For example:
- In program code: date, time, number, currency and paper formats; hotkey or shortcut combinations; and character sets
- In interaction elements: button labels, tooltips, menus, sub-menus, dialogue boxes and their internal elements (options, lists, etc.), system messages (error or status messages), etc.
Normally, the number of localisable elements in the program code is always smaller than that of the localisable elements in the interaction elements.
Very often, software localisation projects consist of translating only the software user interface. It is, however, very important to keep in mind that restricting localisation to the user interface of an application implies that users have to cope with two languages when using the product. And this is not considered to be user-friendly. Thorough testing of the application user interface should be carried out before the documentation is translated to avoid correction tasks for a not-yet-completed translation (Müller, 2005). Each modification of the user interface translation would imply the repetition of testing and also translation, since the terminology in the user interface should correspond to that in the documentation. However, we know that very often in real life things do not go according to plan. Sometimes, for example, localisation of documentation and of user interface sometimes occur simultaneously and within tight timelines (Johnson, 2002).