# Website & product localisation

[Website page](https://verlineo.cc/services/localisation) · en

This document reflects the public website. Starting rates are not a final quotation. Agreements for the individual project take precedence.

Interfaces, documentation and marketing adapted for each market, working directly in your repository or content platform.

We translate in the formats your engineers already ship: JSON, XLIFF, PO, Markdown, or straight from the design file, and return them ready to merge. Placeholders, plurals, dates and currencies are handled as code, not as prose.

## Our approach

Every string is reviewed in context, not in a spreadsheet: we run the localised build and read the interface. Text expansion is flagged before it breaks a layout, and a style guide per market keeps tone consistent as your product grows.

## Deliverables

- Translation in your source format, ready to merge without reformatting
- In-context review of the running build on each target locale
- Per-market style guide and approved terminology base
- Pseudo-localisation pass to surface truncation and encoding faults early
- Ongoing string updates on your release cadence, not ours

## Starting prices

200 RUB / 2.2 USD / 2 EUR · 250 words

Starting prices for common language pairs. The final quote depends on the pair, subject, volume, layout and urgency. Native-speaker translation, notarisation, apostilles and delivery are quoted separately. We confirm the total, taxes and deadline before work starts. Currency equivalents are indicative prices, not live exchange rates.

Turnaround: 3 days. Turnaround is indicative. The final deadline and scope are confirmed after reviewing the materials.

## Formats

JSON, XLIFF, PO, Figma, Markdown

## Questions and answers

### Can you work in our repository and file formats?

Yes. JSON, XLIFF, PO, Markdown and Figma are handled natively and come back in the structure we received, so nothing needs reformatting before it merges. Placeholders, plural forms and escapes survive intact.

### How do you keep tone consistent across markets and releases?

One style guide per market, written at the start and revised with you, and a termbase that carries between releases. The same linguist stays on the account, so the fifteenth release still sounds like the first.

### What happens when a translation breaks the layout?

We pseudo-localise before you ship, which exposes truncation, encoding faults and concatenated strings while they are still cheap to fix. Anything the code cannot express in the target language comes back as a flagged string rather than as a bad translation.

## Translation specimens

This example illustrates a translation decision. Client documents are not published here.

en: Sorry, something went wrong.

de: Es ist ein Fehler aufgetreten.

The English apologises; German product convention states the fact. «Entschuldigung, etwas ist schiefgelaufen» reads as a person apologising, and users hear a company being breezy about a failure. Register is decided once per market in the style guide, not string by string.

## Related pages

- [Indicative rates, honestly qualified.](https://verlineo.cc/knowledge/en/pricing.md)
- [Send a file. We will clarify the rest.](https://verlineo.cc/knowledge/en/quote.md)

[llms.txt](https://verlineo.cc/llms.txt)