Software localisation, app translation and digital content with native specialists
Request a Free QuoteSoftware localisation is far more than translating strings — it is adapting a digital product so it works naturally and intuitively in every market. A button with truncated text, a date in the wrong format, an incomprehensible error message or a call-to-action that doesn't resonate culturally can compromise product adoption and drive users away. M21Global provides software localisation and technology translation with native translators who understand both the language and the technical context.
We work with software companies, SaaS providers, startups, app publishers and product teams across more than 30 language combinations. We integrate with localisation platforms such as Crowdin, Phrase, Lokalise and Transifex, and deliver in any technical format — .xliff, .json, .properties, .resx, .po, .strings. ISO 17100 certification and ISO 18587 guarantee quality, whether for full human localisation or machine translation post-editing.
Software localisation demands a balance between technical precision and linguistic naturalness. Every string has a context — a 20-character label, a tooltip, an error message, a push notification — and the translation must work within those constraints. At M21Global, our translators understand the specifics of software localisation and work with visual context whenever possible.
Content types we localise: UI strings, error and validation messages, tooltips and contextual help, menus and navigation, transactional emails, push notifications, changelogs and release notes, onboarding flows and in-app tutorials, terms of service and privacy policies adapted to each jurisdiction.
Supported formats: .xliff and .xlf (OASIS standard for localisation interchange), .json (React, Vue, Angular), .properties (Java), .resx (C#/.NET), .po/.pot (gettext, PHP, Python), .strings and .stringsdict (iOS/macOS), .xml (Android), .arb (Flutter/Dart), .yaml/.yml (Ruby on Rails), .ts (Qt). We preserve key integrity, variables, placeholders and pluralisations — translation never breaks the code.
Localisation platform integration: we work natively with Crowdin, Phrase (formerly Memsource), Lokalise, Transifex, Smartling and POEditor. If your product team uses one of these platforms, we integrate into the existing flow — import strings, translate, and return directly to the platform, without the need to manually export/import files. This reduces process friction and accelerates delivery cycles. See our website translation for web projects.
Presence in multiple markets requires more than translating an app's content — it requires cultural adaptation that extends from store descriptions to in-app micro-interactions. M21Global provides complete app localisation, covering every user touchpoint.
App Store and Google Play: we translate and adapt titles, subtitles, descriptions and changelogs for App Store (iOS) and Google Play (Android). This is not a direct translation — it is multilingual ASO (App Store Optimization): we research relevant keywords in each target market, adapt tone and selling points to the local audience, and optimise texts to maximise conversion and store visibility.
In-app strings: buttons, labels, feedback messages, confirmation dialogs, empty states, errors and notifications. Each string is translated in context — we know whether it is a 10-character button or a help paragraph, and adapt the translation to the appropriate space and tone. For iOS, we work with .strings and .stringsdict (including complex pluralisations); for Android, with .xml and ARB.
Cultural adaptation: localisation goes beyond text translation. Dates (DD/MM/YYYY vs MM/DD/YYYY), currencies (€, $, R$), units of measure (km vs miles), reading direction (LTR vs RTL for Arabic/Hebrew), and address conventions (postcode, state, district) — all must be adapted so the product feels native in every market.
Push notifications and transactional emails: content with direct impact on user retention and engagement. We translate with attention to tone (casual vs formal, as per the brand) and length (notifications have character limits). Business translation ensures brand voice is consistent across all channels.
Technical documentation is the pillar of user support and product adoption. Outdated or poorly translated manuals generate support tickets, user frustration and churn. M21Global translates technical documentation preserving the structure, formatting and functionality of the content.
User manuals: installation, configuration, operation and troubleshooting guides. We translate preserving referenced screenshots, step numbering, callouts and warning boxes. For rapidly evolving products, we manage incremental updates — translating only the changed sections, reusing existing translation for unchanged content, which reduces costs and timelines.
API documentation and developer docs: technical documentation for developers — endpoints, parameters, code examples, error codes, authentication flows. We translate preserving inline code integrity, variables and examples. Our translators understand the difference between translatable text and code/commands that must remain unchanged.
Knowledge base and help centre: support articles, FAQs, tutorials and troubleshooting guides. For large volumes of support content, we use MTPE (ISO 18587) — machine translation with human post-editing — which enables translating hundreds of articles with adequate quality at significantly lower costs than full human translation.
Formats preserved: Markdown, HTML, XML, reStructuredText, AsciiDoc. We preserve formatting — headings, lists, links, code blocks, tables, admonitions — ensuring translated content works in the client's documentation system without manual reformatting. See our technical translation for more details on our approach.
Not all digital content requires full human translation. Knowledge base articles with simple language, repetitive UI strings, level 1 support content or standardised product descriptions are ideal candidates for MTPE (Machine Translation + Post-Editing) — machine translation followed by post-editing by a qualified linguist.
ISO 18587: M21Global is certified according to ISO 18587, the standard defining requirements for post-editing of machine translation. This means the process is audited: post-editors are qualified, MT output is evaluated before post-editing to determine feasibility, and the final result is verified against defined quality criteria. This is not "using Google Translate and reviewing on top" — it is a professional process with quality assurance.
When to use MTPE: support and help centre content (high volume, standardised language), knowledge base and FAQs (repetitive structure, frequent updates), UI strings with recurring patterns (error messages, validations, confirmations), product descriptions with fixed templates, lower-visibility internal documentation. For these content types, MTPE can reduce costs by 30-50% compared to full human translation, while maintaining quality adequate to purpose.
When NOT to use MTPE: marketing copy and creative content (requires transcreation), main UI and onboarding (first user impression), legal documentation (terms of service, privacy), content with brand or safety impact. For these cases, we recommend full human translation with TEP process (Translation, Editing and Proofreading).
The decision between MTPE and human translation is made project by project, based on content type, visibility, volume and budget. M21Global advises the most appropriate approach for each case — contact us for a free analysis.
Technology companies operate with fast cycles, frequent releases and distributed teams. The translation provider must adapt to this pace, not impose its own. M21Global structures the relationship with tech companies around four pillars:
CI/CD integration for continuous localisation: instead of translating in batch, we integrate the translation process into the development pipeline. New strings are automatically exported for translation, translated by the dedicated team and returned to the platform — Crowdin, Phrase, Lokalise — ready for merge. This allows localisation to keep pace with development, instead of being a release bottleneck.
API for workflow automation: for teams that prefer full automation, we provide API integration that allows submitting content, checking status, receiving deliveries and requesting reviews programmatically. This eliminates email as a project management channel and integrates translation into the product team's existing workflow.
Team with Agile/Scrum experience: our project managers understand sprints, user stories, backlogs and releases. We know that a string can change until the last moment before the freeze, that context may come in a Figma or a Jira ticket, and that the deadline is the release date. This familiarity with the Agile process reduces communication friction and avoids misunderstandings about deadlines and priorities.
Technical glossaries and style guides per product: every product has its terminology — and that terminology must be consistent across all languages, all platforms and all versions. We create and maintain technical glossaries and style guides per product, defining how each term is translated, what tone is used (formal/informal, tu/vous), and what conventions are followed. These linguistic assets evolve with the product and belong to the client. Request your quote and see how we can integrate into your development workflow.
We support all standard localisation formats: .xliff/.xlf (OASIS), .json (React, Vue, Angular), .properties (Java), .resx (C#/.NET), .po/.pot (gettext), .strings/.stringsdict (iOS/macOS), .xml (Android), .arb (Flutter/Dart), .yaml/.yml (Ruby on Rails), .ts (Qt). We preserve keys, variables, placeholders, pluralisations and formatting — translation never breaks the code. For custom formats, we analyse the structure and adapt the process. See our website translation for web projects.
Yes. We work natively with Crowdin, Phrase (formerly Memsource), Lokalise, Transifex, Smartling and POEditor. We integrate into your team's existing flow — import strings directly from the platform, translate and return without the need to manually export/import files. For teams with more automated workflows, we provide API integration for programmatic submission, status checking and delivery reception.
Yes. We integrate the translation process into the development pipeline: new strings are automatically exported, translated by the dedicated team and returned to the localisation platform ready for merge. Our project managers understand sprints, user stories and release cycles, and know that the deadline is the release date. This approach allows localisation to keep pace with development instead of being a bottleneck. For teams that prefer batch, we also manage deliveries by milestone or release.
It depends on the content type. Yes, it is suitable for: knowledge base articles, support FAQs, repetitive UI strings (error messages, validations), standardised product descriptions and internal documentation. No, it is not suitable for: main UI and onboarding (first impression), marketing copy and creative content, legal documentation, and content with brand or safety impact. M21Global is ISO 18587 certified for MTPE and advises the most appropriate approach for each content type, and can combine MTPE and human translation in the same project.
Yes. We translate technical documentation for developers — endpoints, parameters, code examples, error codes, authentication flows, SDKs and integration guides. Our translators understand the difference between translatable text and code/commands that must remain unchanged, preserving inline code integrity, variables and examples. We support Markdown, HTML, XML, reStructuredText and AsciiDoc, ensuring formatting — headings, code blocks, tables, admonitions — works in the client's documentation system.
Solicite um orçamento gratuito e receba uma resposta personalizada em menos de 3 horas.
Request a Free QuotePlease visit this page before submitting your documentation.
