• Software localisation

    Software localisation

    KERN Global Language Services localises user interfaces, dialogue boxes, buttons and online help, for example.

Software localisation

KERN makes use of the latest methods to localise menus, dialogue boxes, buttons in a software user interface, online help, printed documentation and other accompanying files (licence agreements, README files and much more) for use in the target country. Since the text lengths in various languages can be significantly different, KERN adapts the size of user interfaces and dialogue boxes (resizing) as part of localisation. The localised user interface serves as a reference when translating online help and documentation; ideally, this is carried out by the same team that localises the user interface.

Test procedure for quality assurance

Within the meaning of software user-friendliness, quality assurance has a fundamental role in avoiding internationalisation and localisation errors. The quality of the internationalisation strategy and the source language texts largely determine the standard of a software that is available in several languages.


Internationalisation tests

Before the actual product localisation, an internationalisation test is useful to test – as part of pseudolocalisation, if applicable – the extent to which the software can be adapted and in order to facilitate the country-specific localisation. This test checks, for example, whether regional standards, the font used, and the software and hardware are supported in the target countries.

Localisation tests

Experienced specialist mother-tongue translators with sector-specific IT knowledge are vital for translation. A high-quality localisation includes a review from a second specialist translator and also a localisation test, in which language-specific, visual and functional aspects are taken into account to ensure that the localised software is user-friendly.

Functional tests

To implement functional tests after the localisation, a test script will be required that contains all the instructions for opening menus and performing functions. Possible functional tests comprise, for example:

  • Validation testing (validation based on defined requirements)
  • Defect testing (localisation and rectification of errors, debugging)
  • Regression testing (Repetition of tests for changed versions)

User interface testing, compatibility testing, performance testing, security testing, transaction testing and many more types of testing can also be carried out in this regard, depending on customer-specific requirements.

Do you have questions about the areas of localisation and testing? The KERN language team is always readily available to give you personal advice and information.