Software and Game Localisation 5 August 2026
Software Genres: Translating System, Utility and Application Software
Not every piece of software is translated in the same way. We explain how system, utility and application software and the embedded documentation genres bear on localisation.
Translating an operating system is not the same job as translating a mobile game or a user manual. Each has its own language, its own terminology and its own constraints. To be able to see these differences you first need to know the software genres, because the genre settles from the outset how localisation will be planned.
Contents
In this article we take software genres in three main groups: system, utility and application software. We then examine how a software product is not a single text but a whole made up of embedded genres, and why documentation genres are planned separately. The aim is to take translation decisions that fit the genre.
Why do software genres matter?
As Sommerville notes, there are a great many different genres of software, from simple embedded systems to complex information systems operating worldwide (Jiménez-Crespo, 2024). This diversity means that no single localisation recipe will suit every product. The genre settles both the language and the process.
The strings of an operating system, for instance, have to be short, technical and utterly consistent, because these terms set a reference for all other software. A game, on the other hand, calls for creative and fluent language. Even the same translator follows different strategies in these two genres.
Knowing the software genres therefore makes it possible to take the right decisions before a project has even started. How the termbase is to be built, which constraints will come to the fore and what expertise will be needed all vary with the genre.
System software
System software is the layer that governs the basic working of the device: operating systems such as Windows, macOS, Linux, Android and iOS belong to this group. It is loaded into memory when the device starts up and it controls all the hardware components. Whether it runs on a local computer or in the cloud, every product rests in the end on this layer.
Translating system software is the most sensitive of all where consistency is concerned. The terms used in an operating system become a shared glossary for every application running on it. The renderings of concepts such as “Save”, “Copy” and “Settings” spread to other software almost as a standard.
Following the platform terminology is therefore obligatory when translating system software. If an application departs from the terms the operating system has set, the result is an inconsistent experience for the user. The system layer is the reference point of the whole localisation chain.
Utility software
Utility software is regarded as an extension of system software. It helps the computer to run properly and most of the time it works quietly in the background. Antivirus programs and certain optimisation tools are typical examples of this genre.
The language of utility software is generally technical and heavy on warnings. It consists of short strings that report a risk to the user, recommend an action or describe a state. In these strings clarity matters more than style; the user has to grasp at a glance what needs to be done.
The greatest risk in translations of this kind is a technical warning being carried across in vague or alarming language. A good utility software translation is calm and clear enough for the user to take the right step without panicking.
Application software
Application software covers everything we call an “app” in everyday life. Word processors, spreadsheets, multimedia programs and communication software belong to this group. Games running on a local computer count as application software as well.
Because this is the broadest and most varied genre, it also holds the most variability in localisation. An accounting application calls for technical language, while a social application needs a warm, everyday tone. Separate applications sometimes come together to form software suites, and consistency then matters even more.
The industry also classifies software by the purpose it is put to. The table below summarises a categorisation of software based on use.
| Category | Example use |
|---|---|
| Platform and management | Operating and system applications |
| Education and reference | Learning and reference tools |
| Home and entertainment | Games, multimedia |
| Content creation and communication | Productivity, messaging |
| Operations and professional | Business process software |
The software genre system and embedded genres
A software product is in fact not a single text; it is a whole made up of embedded genres. The interface text, the documentation, the product’s website and the quick reference guide are all parts of that whole. These parts have to share the same terminology and the same style.
This unity ties translation decisions to one another. Once the rendering of a menu item has been settled, for example, that same item has to appear in the same form in the help documentation and in the screenshots. Saying “Save As” in one document and using a different rendering in another misleads the user.
Localisation therefore treats the product in its entirety as a coherent global unit. Every layer of the product is translated not on its own but as an interconnected system. The idea of a genre system is the key to securing this consistency.
Documentation genres
Software documentation divides first of all into internal and external. Internal documents are aimed at the team that develops and maintains the software; external documents at the end user. Localisation projects generally deal with external documents, that is, with the manuals and tutorials the user sees.
There are also many documentation genres defined by purpose: product help, tutorials, technical notes, reference guides and promotional texts. Each of these calls for a different style; a tutorial goes step by step and encourages, while a technical note has to be short and exact.
In recent years external documentation has moved beyond the traditional help page; video tutorials, “getting started” texts and discussion boards have joined this field. Users turn to the manual on first encounter but prefer searching online at later stages. This calls for planning which document is to be translated first.
Games are application software too
Interestingly, video games are classified as application software as well when they run on a local computer. Games are, however, the most complex and most multimodal example of application software. Their interface strings resemble those of an accounting application, while the dialogue and story layer comes close to literary translation and the audio assets to audiovisual translation.
This layering puts games in a place of their own among the software genres. Technical, creative and audiovisual translation all sit together in a single product. Game localisation therefore brings the skills of every software genre together in one project.
This view shows that the boundaries between genres are not firm. A product can carry the features of more than one genre at the same time. The localisation team works out which genre weighs most heavily in which layer of the product and adjusts its approach accordingly.
How does knowing the genre guide translation decisions?
Knowing the genre of a product turns into concrete decisions at the translation desk. In system software, consistency and fidelity to the platform terms come first, whereas in a game creativity and fluency take priority. The same translator works in a different frame of mind depending on the genre.
Knowing the genre also settles what expertise will be needed. A technical utility program calls for a translator with knowledge of the field, while a creative application needs a translator with a fine ear for style. Matching the two correctly is the first condition of quality.
Finally, the genre settles the constraints as well. Character limits, termbases and testing methods all vary with the genre. A project whose genre is correctly identified at the outset allows for these constraints in advance and meets fewer surprises.
The Türkiye context
Software localisation in Türkiye is concentrated for the most part on application software and mobile apps. At operating system level, Turkish terminology has largely settled, and this gives translators of applications a ready reference glossary. Following the system terms is the first condition of consistency in Turkish applications.
On the documentation side, Turkish content is often incomplete or out of date. Many products put their interface into Turkish but leave the help content in English. Yet at the first difficulty the user looks for a manual in their own language; this gap slows the take-up of the product.
The capacity of Turkish to coin terms of its own is an advantage in this field too. Using established Turkish equivalents for technical concepts strengthens both comprehensibility and the local feel of the product. Whatever the genre, a consistent Turkish terminology settles the quality. In products made up of more than one component in particular, a rendering chosen in the interface has to stay the same in the documentation and on the website if the user is not to be left confused; that consistency can only be secured through a shared termbase.
What does this mean for you?
Before having software translated, working out which genre it falls into and which components it consists of is the first step towards an accurate quote. Whether you are having only the interface translated, or the documentation and the website as well, bears directly on your budget and your schedule. A request whose genre and scope are not clear leads both to an incomplete quote and to surprise items appearing later; defining the scope at the outset gives both sides a predictable process.
- List the genre of your product and its embedded components.
- Secure alignment with the operating system terminology from the start.
- Make sure the interface and the documentation are tied to the same termbase.
- Decide which document is to be translated first according to what users need.
To make these decisions clear you can look through our software localisation services, and for a road map suited to the scope of your project you can request a quote. A project whose genre is correctly identified is correctly planned from the very beginning.
Frequently asked questions
What are the software genres?
Broadly, they divide into three: system software, utility software and application software. Operating systems, tools running in the background and everyday applications belong to these groups.
Why does the software genre affect the translation?
Every genre carries a different language, terminology and set of constraints. An operating system, a game and a help manual are localised with the same care but through different approaches.
What does the software genre system mean?
A software product consists not of a single text but of embedded genres: the interface, the documentation, the website, the quick reference guide and so on. All of these have to be consistent.
Why are documentation genres handled separately?
Documentation divides into internal and external; external documents are aimed at the user. Manuals, tutorials and technical notes call for different styles and are planned separately.
References
- Jiménez-Crespo, M. A. (2024). Localization in Translation. Routledge (Ch. 8).
- Sommerville, I. (2010). Software Engineering. Addison-Wesley.
- Roturier, J. (2015). Localizing Apps. Routledge.