Xlifflane answers
Every answer below is aimed at a question people measurably search for, is written from named sources, and links to the page that handles the job itself. None of them is a landing page in disguise.
Guides for the engineer who owns a software product's strings: what software localization, internationalisation, translation memory, continuous localisation and localisation testing are for, what a translation management system has to keep, and how a game, a mobile app and a SaaS differ. Every guide points at the free worksheet that works the figure it discusses.
- What is software localization? Strings, locales and the builds that ship them
What software localization is: adapting a product's strings, plurals, formats and layouts for each locale, and the record a team keeps to do it again.
- Translation management systems: what a TMS has to keep for a software product
What translation management systems keep for a software team: the string catalog, translations per locale with a status, the memory and the handoff.
- Localization management software: what the tooling has to do for the team that owns the strings
What localization management software and localization tools have to do for a software team: keep the catalog, cost the release, hand off, score the build.
- Localisation (localisation strategy): what localisation is for a software product, the UK term for the discipline, and how a team decides which locales to ship
What localisation is, in the UK spelling: adapting a software product for each locale, and the localisation strategy that decides which locales ship first.
- Localization strategy: the decisions a software team makes before a locale ships
A localization strategy for a software product: which locales, in what order, at what cost per release, and the practices that keep the catalog shippable.
- Translation memory software: what the memory holds and what it saves a release
What translation memory software holds and why it cuts a release's cost: exact and fuzzy matches priced at their rates. The free sheet works the saving.
- Continuous localization: the release loop run on every merge, and the record it needs
What continuous localization is: the localization workflow run on every merge, strings frozen, handed off, read back and tested, and the record it needs.
- Software internationalization: the i18n engineering that comes before localization
What software internationalization is: the engineering that puts strings in a catalog, formats by locale and lets layouts stretch, before any locale ships.
- Game localization: strings, plurals and the locale build a studio ships
What game localization takes for a studio: the catalog with context, plurals and placeholders per locale, the memory across titles, the build played.
- Mobile app localization: one string catalog from the app to the store listing
What mobile app localization and SaaS localization take: one catalog exported per platform, plurals and formats per locale, the memory and the handoff.
- AI localization: what machine translation does to the string catalog, and what it cannot do
What AI localization does for a software team: a first pass on new strings, a suggestion on fuzzy matches, a placeholder check, and the review it needs.
- Localization testing tools: what a locale build is checked for, and how defects are counted
What localization testing tools check in a locale build: untranslated strings, truncation, hardcoded text, plurals and formats, against a ship threshold.