Software interfaces
Web, desktop and mobile apps, system messages, notifications, help.
Software localisation, in every customer’s language.
Interfaces, resource files, documentation and content, translated and tested in the product. 25+ years of experience, 50+ language pairs, localisation engineering for recurring releases.
What we localise
Devices and hardware
Device menus and messages, manuals, installation materials.
Websites and content
Pages, commercial content, marketing materials, with per-market SEO requirements.
Documentation, DTP and multimedia
Manuals, e-learning, subtitling and voice-over coordination.
Engineering, not just translation
- We separate text from the code that must be kept; we check variables, tags and the import into the app
- Encoding, diacritics, text expansion and local formats, solved with the product team
- Translation memories and glossaries per client: the same terms in UI, help and manuals
- Linguistic and functional QA in the application, not only in the file
- We work in your CAT/TMS or ours; for MLVs: in-country review, DTP, cultural QA
LOCALISATION WORKFLOW
A complete workflow with clear review points
Analysis and preparation
We inventory content, languages, formats and product constraints. We request context, screenshots or test access and identify integration risks.
Terminology and translation
We agree terminology, style and references. Translation uses the applicable memory and glossaries, with the review level agreed for the project.
Engineering and integration
We return resources in delivery formats, check variables and encoding and work with the product team on the localised version.
QA and updates
We review in context, report issues and track corrections. For later releases, existing language resources support work on changed content.
Who it is for
Software companies
Products with recurring releases in several languages, with resources and help that must keep up.
Brands present in several countries
Website, commercial materials and product content adapted to each market.
Multilingual vendors (MLVs)
Engineering and Romanian-language partner for projects coordinated across markets.
Experience inEnterprise softwareIndustrial automationFinanceHealthcareE-commerce
INDICATIVE PRICING
A starting point for your localisation budget
| Service | Indicative rate |
|---|---|
| Software interfaces and web applications | EUR 0.06–0.10 / word |
| Help, manuals and web content | EUR 0.04–0.06 / word |
| Graphic localisation, DTP and other hourly work | EUR 15–30 / hour |
| Editing and proofreading | 30% of the standard translation rate |
FAQ
Questions about localisation
Answers about the project, collaboration and getting started.
Have a question about your project?01How does software localisation differ from translation?
Translation adapts text into another language. Software localisation also addresses interface context, terminology, locale formats, technical constraints and validation inside the application.
02Can we use our existing translation memory and tools?
Yes. We review your resources, glossaries and CAT/TMS environment. The goal is terminology continuity and integration into a workflow your team can manage.
03Do you work with translation agencies?
Yes. We can support MLV-led projects with language resources, in-country review, DTP, testing and engineering. Responsibilities and handovers are defined before work begins.
04What should we send for an estimate?
Target languages, source files or formats, approximate volume and the desired deadline. Glossaries, screenshots and test access help clarify context and validation effort.
05How do you handle frequent application updates?
We establish a resource baseline, identify changes between releases and reuse relevant translations. For recurring delivery, frequency, responsibilities and review steps are agreed.
06Do you use machine translation or AI?
They can be part of the workflow where the content and processing conditions allow. Methods, services and the level of human review are agreed for the project.
07What does localisation testing include?
Linguistic checks in context, text display, terminology consistency and relevant functional scenarios. Languages, versions and devices are defined in the project plan.
What does software localisation include?
Software localisation adapts interface text, resources and documentation to the language and cultural context of the target market. It can also include linguistic engineering, internationalisation support and testing.
How is localisation different from translation?
Translation concerns the text. Localisation also considers the product context, terminology, interface constraints, formats and the way the software works for users in another market.
What should we provide for a localisation estimate?
Share the target languages, resource formats, approximate volume, product context and required delivery schedule. Access to a test environment and reference terminology can help clarify the scope.