Strings are translated in place
We account for the screen purpose, neighbouring elements, length limits and variables within each string.
For websites and apps
Digital product localisation for a new market
We translate interfaces and content, adapt date, number and currency formats, manage terminology and check how the text works in the layout. The result is a language version of your website, app or service ready for release.
1 marketa dedicated language and regional version
3 layerscontent, interface and locale formats
LQAlanguage checked in context
Beyond translation
Localisation considers
more than language
A button cannot be translated in isolation from its screen, and a price or date should not remain in an unfamiliar format. We look at where each string appears, what happens after an action and which conventions apply in the target market. The finished version feels native to the product rather than pasted over the interface.
Regional formats are adapted
Dates, times, numbers, currencies, units, addresses and other locale-specific data are reviewed.
The product is checked after build
We look for truncation, missing strings, incorrect substitutions and inconsistent interface elements.
What we localise
From landing page
to application interface
Corporate websites and landing pages
Navigation, forms, service pages, legal copy and post-submission messages are adapted for the market.
Web services, customer portals and SaaS
We translate interface strings, states, notifications, tooltips and system messages in their user journey.
Mobile applications
String resources, onboarding screens, permissions, push notifications and error messages are localised.
Online shops and catalogues
Product pages, filters, baskets, checkout, delivery, measurement units and email templates are covered.
Knowledge bases and customer support
Terminology is aligned across the interface, help centre, guides, chatbot and support responses.
App Store and Google Play listings
We prepare names, descriptions, key messaging, screenshot captions and supporting launch material.
Source material
Send the strings with their context
We accept JSON, YAML, XML, XLIFF, CSV and PO exports, as well as string tables. If text exists only in a design, Figma, screenshots or an editable file can be used. Complex document formatting can be included in the same order.
Include your glossary, style guide and list of protected names. For a working product, a test build or annotated screenshots make the context much clearer.
Workflow
From string audit
to language release
We define the scope
Languages, markets, files, screens, formats and release-specific material are recorded.
We build the glossary
Tone, key terms, feature names and words that must remain untranslated are agreed.
We translate and adapt
Strings and content are localised while variables, markup and field limits remain intact.
We check in context
Screens or a test build are reviewed for truncation, inconsistent terms and untranslated content.
Before the project
Questions about localisation
How is localisation different from translation?
Translation changes the language of the text. Localisation also accounts for the interface and target-market conventions, including date and currency formats, measurement units, string length, images, terminology and user journeys.
What should I send for a quote?
Send a string export or design link, several screens showing context, and the target languages and markets. Include any glossary, style guide, test build or field-length requirements available.
Which file formats do you accept?
We accept JSON, YAML, XML, XLIFF, CSV, PO and string tables. Keys, variables, tags and file structure are preserved. The return format is agreed before work begins.
Do you need access to the source code?
Usually not. We work with exported resources, designs and screenshots, while your team integrates the finished files. A test build or access to the relevant screens is sufficient for linguistic review.
How are future updates localised?
We retain the glossary and approved translations. For each release, new and changed strings are separated from existing material and then checked in the context of the updated interface.
Project assessment
Send the string export and a few screens
We will confirm the scope, team, return format and review process before work begins.