VC LABServicesLocalization & LQA

Localization & LQA: the product speaks the language of the new market

We translate interfaces, copy and documentation and check the result where the user will see it — in the interface, not in a spreadsheet. Russian, English and Uzbek in-house, other languages with vetted partners under our quality control.

How localization differs from translation

Translation is text. Localization is text that fits into a button, inflects correctly next to a number, shows dates and amounts in the format the country expects and does not break local advertising rules. The difference only shows in the interface, which is why LQA — linguistic testing — is a mandatory part of the job for us, not a separate service.

Typical LQA findings that never appear in a translation sheet: a string clipped on a narrow screen, "1 items" instead of "1 item", a date in US order for a European market, a currency symbol in the wrong place, a promo text still carrying a campaign name from the previous market.

What we localize

  • Web and mobile app interfaces: strings, tooltips, errors, push notifications.
  • Documentation and knowledge bases: help centre, instructions, support answers.
  • Marketing and promo materials: landing pages, banners, emails, promotion copy — checked against platform rules.
  • Legal texts together with the client's lawyer: offers, policies, promotion terms.
  • Subtitles and voice-over for video and training materials.
Deliverables: translated resource files in your format, a glossary, translation memory and an LQA report with screenshots for every language.

How we handle terminology

The main cause of poor localization is not mistakes but inconsistency: the same button is named three different ways because different people translated it at different times. So the first step is a glossary — the product's terms with approved variants in every language — and a translation memory so that repeated phrases stay identical across releases.

  1. We build the glossary from the interface and documentation and agree it with your team.
  2. We translate against the glossary and translation memory; unclear spots are flagged as questions, not guessed.
  3. We assemble the translation into the product and run LQA on real devices.
  4. We hand over the files, the LQA report and the updated glossary — it remains your asset.

Languages and markets

Russian, English and Uzbek are handled in-house. For the Cypriot, Hong Kong and Armenian markets we bring in native speakers of Greek, Traditional Chinese and Armenian through partners who work to our glossary and our LQA checklist. We remain the single contractor and are responsible for the result in every language.

  • Date, number, currency and address formats for each country.
  • Advertising rules and mandatory disclaimers — separately for iGaming and financial products.
  • String length checks for the narrowest screens and the longest languages.
  • A single brand tone of voice across languages.

FAQ

In which format do you accept strings?
Any working format: JSON, XLIFF, PO, strings, resx, Excel, or direct access to Crowdin, Lokalise or POEditor. We return files in the same format so nothing has to be moved by hand.
What if a translation already exists but its quality is doubtful?
We start with LQA: go through the interface, record errors and inconsistencies with screenshots and estimate the volume of fixes. It is often cheaper to fix and build a glossary than to translate from scratch.
How is pricing calculated?
Translation by word count with translation memory repetitions discounted, LQA by tester hours per language and device. The estimate is fixed before work starts.
Can you work with machine translation?
Yes, as post-editing: a machine draft goes through a native editor and mandatory LQA. For interfaces and legal texts we recommend translating from scratch — there the cost of an error exceeds the saving.

Tell us about your task

We reply within one business day and send an estimate in 1–2 days. Free of charge.

Updated: 2026-10-02