Native technical translators, ICU/CLDR-compliant pluralisation and date/number formats, pseudo-localisation pre-translation QA, and Git/CI integration — for SaaS, mobile, desktop, games and enterprise applications.
Software localisation is more than translating UI strings. ICU MessageFormat for pluralisation and variable substitution, CLDR for locale-aware dates and numbers, pseudo-localisation QA before translation begins, and Git/CI integration for continuous releases — every piece in the i18n chain has to hold. Our native technical translators work in your tooling and your release cadence. NDA on every project.
String by string, context by context — specialists with software/i18n experience localise your software per ICU MessageFormat and CLDR conventions. Embedded in your Git/CI workflow so every release is ready in every language on release day.
Localisation mistakes tend to be small but costly: a truncated button label, a wrong date format, an incorrect plural stem in Russian, or UI that fails to mirror in RTL. Our workflow starts with pseudo-localisation as standard, exposing hard-coded strings, layout breaks and concatenation bugs before the translation phase begins — engineering fixes happen in code, not across fifteen translations later. For ongoing releases we move with your development team via Git, CI/CD and TMS integration.
From core EU languages to Arabic, Hebrew, Farsi and Urdu (RTL) — specialists with software/i18n experience per market, with full attention to UI conventions.
We analyse your software files — gettext .po/.mo, XLIFF, JSON i18n, RESX, .properties, Apple .strings/.stringsdict, Android XML — and draw up a localisation plan. Strings, variables, placeholders and context-dependent elements are identified upfront.
Standard step: pseudo-localisation temporarily replaces source strings with expanded test characters (for example "[!!! Säve čhängēs !!!]") to expose hard-coded strings, layout breaks, concatenation bugs and missing externalised strings before translators begin.
We configure an efficient workflow via Git, GitHub/GitLab Actions and TMS (Phrase, Lokalise, Crowdin, memoQ Server). Pull-request driven workflow with version control and delta strings — only new or changed strings re-enter translation.
A specialist with software-engineering training or i18n sector experience localises every UI string with an eye for context: a three-word button label needs a different approach to an extensive help text or an error message. ICU MessageFormat and CLDR plural categories are applied correctly throughout.
Where the project scope, release cadence or volume requires it, a second specialist checks the translations in context — with screenshots or a live build — to verify strings fit the available space, placeholder integrity is preserved and the interface reads logically.
We deliver localised files in your source format, import-ready via PR or your TMS. For ongoing releases we become your dedicated localisation partner — every sprint, release or hotfix.
A string like 'Delete' can be a button (imperative, short) or a confirmation header (calmer, explained). Without context a translator can miss the tone or place a placeholder incorrectly. Our approach uses screenshots, live build access and UI QA — where the project scope, release cadence or volume requires it. Combined with pseudo-localisation before the translation phase, hard-coded strings and layout breaks are fixed in code first.
From format support to sprint integration: our localisation moves with your development team, not the other way around.
Pluralisation per CLDR plural categories (zero/one/two/few/many/other), locale-aware date/number/currency formats and placeholder validation via ICU MessageFormat. No string concatenation hacks for plural forms.
We run pseudo-localisation before the real translation begins to expose hard-coded strings, layout breaks and concatenation bugs. Engineering fixes happen before the translation phase, not after — saving costly retranslate cycles.
From core European languages to Arabic, Hebrew, Farsi and Urdu (RTL): localisation for every market, with UI mirroring, BiDi text rendering, locale-aware date and currency formats and CLDR collation rules.
We always ask for the context of each string. An error message, a tooltip and a button label each demand a different tone and length. Specialists with software/i18n experience receive screenshots or direct build access.
Every localisation runs through a quality process — from format check to context QA inside your live build environment.
From SaaS dashboards and fintech mobile apps to AAA games shipping across multiple languages.
SaaS · B2B Project pattern for SaaS providers: every sprint new or changed strings flow through Git integration into multiple languages. Pull-request driven workflow, translation memory per client, specialists with UX sensibility — only delta strings sprint after sprint, no release blockers.
Fintech · Mobile Project pattern for fintech apps live in multiple markets including Arabic and Hebrew: full RTL UI localisation with mirroring, locale-aware currency and date formats per market, accessibility strings included. Context QA in the live build before release.
Games · AAA Project pattern for AAA game localisation: dialogue, UI, menus and accessibility strings localised in parallel across many languages. Context screenshots per scene, terminology base for character lore, synchronous launch across every market.
Localisation for every type of software — from B2B SaaS to mobile games, including RTL layouts and analytics dashboards.
What clients say about working with Ecrivus — from SaaS startups to AAA game publishers shipping across multiple languages.
Certified translations for our international cases are delivered quickly and carefully. Our project manager knows our account inside out.
No-obligation — response within one hour during business hours
Below you'll find adjacent services, sectors we translate for often, and the most requested language pairs.
Services frequently commissioned alongside this one.
Sectors we deliver this service for regularly.
Most requested combinations for this service.
Last updated: May 2026
