What is covered
Interfaces that read
as if written in the language
Software localisation adapts the text of an application to another language: interface strings, error messages, help content, documentation and release notes.
Strings are translated from resource files such as XLIFF, JSON, PO or RESX exports. Placeholders, variables and tags are kept unchanged, and length limits for buttons and menus are respected where the client specifies them.
Interface terms are held in a term base and reused in the help content and manuals, so the same function has the same name everywhere. Product documentation follows the technical translation process.
Software localisation in practice
Content, method
and standard
Typical content
User-interface strings, error and system messages, online help, user guides, release notes and app-store descriptions.
Process specifics
Screenshots, string comments or access to a test version give translators the context of each string. Questions are collected and answered before delivery.
Quality standard
ISO 9001:2015 for translation and localisation, with translation and revision under ISO 17100 and software QA checks for tags and numbers.
Questions
Questions about
software localisation
Which file formats are used for software localisation?
Resource files exported from the code base or localisation platform, such as XLIFF, JSON, PO or RESX. The format is agreed when the quote is prepared.
How are placeholders and variables handled?
They are protected in the CAT tool and checked by QA software before delivery, so the translated files can be imported without changes to the code.
Can updates be localised without retranslating everything?
Yes. Translation memory recognises strings that were translated before, so later releases need translation only for new and changed text.