Localization

We cover 70+ languages. That includes the major European and Asian languages, right-to-left scripts like Arabic, Hebrew, Farsi and Urdu, and the Indian languages — Tamil, Hindi, Telugu, Kannada, Malayalam, Bengali and others. If you need a pair we have not listed, ask. We can usually source a vetted linguist within a few days.

Translation converts the words. Localization makes the whole thing work in the target market — dates, currencies, units, images, layout direction, even colour choices where they matter. A brochure usually just needs translation. A website or app needs localization, because text expands, layouts break, and forms have to accept local addresses and phone numbers.

Per source word for most documents. DTP and layout work is quoted per page. Software and website localization is quoted per project after we see the files. Rates vary by language pair — common pairs cost less than rare ones. Larger volumes get better per-word rates, and repeated text matched by translation memory is discounted or free.

A single translator handles roughly 2,000 to 2,500 words a day. Add a day or two for review and any formatting. We run 24/7, so urgent jobs can be split across linguists in different time zones — that speeds things up but needs a shared glossary to stay consistent. Tell us your deadline and we will say honestly whether we can meet it.

Translation memory is a database of every sentence we have translated for you. When the same or similar sentence comes back — in a manual update, say — the tool flags it and we reuse the earlier translation. You pay a reduced rate for partial matches and little or nothing for exact repeats. On technical documentation the savings add up quickly.

Yes. Before a large project we build a glossary of your product names, technical terms and preferred phrasing, and send it to you for approval. Every linguist on the job then works from it. It costs a little time up front and saves a lot of rework later. The glossary stays yours.

Native speakers of the target language. A translator working into their mother tongue catches tone and idiom that a second-language speaker misses. For technical content we also match subject background — a medical document goes to someone who has translated medical material before, not just anyone who speaks the language.

Yes — Arabic, Hebrew, Farsi and Urdu are regular work for us. RTL needs more than translation: layouts mirror, tables flip, and mixed-direction text (an English product name inside an Arabic sentence) needs careful handling. Our DTP team does this in InDesign and other tools, and a native speaker checks the final layout.

Yes. Tamil, Hindi, Telugu, Kannada, Malayalam, Bengali, Gujarati, Marathi and more. Indic scripts have their own problems — font support, conjunct characters, text rendering in PDFs and apps. We test the output on the actual target format, not just in the translation tool, so you do not get boxes where letters should be.

You export your strings — resource files, JSON, XML, PO, XLIFF, whatever your platform uses. We translate them in a CAT tool that protects the code and placeholders, then return files in the same format. After you build, we do a pass on the live site or app to catch truncated text, broken layouts and untranslated strings.

A second linguist reviews the translation against the source for accuracy, grammar, terminology and consistency with the glossary. We also run automated checks for missing numbers, double spaces, untranslated segments and broken tags. For software, QA extends to checking strings in context on the running product. It is a separate step from translation, done by a different person.

Most of them. Word, Excel, PowerPoint, PDF, InDesign, FrameMaker, HTML, XML, JSON, PO, XLIFF, plain text, subtitle files. Scanned PDFs work too — we recreate the document first, which adds a little to the cost. If you have something unusual, send a sample and we will confirm before quoting.

We sign an NDA before you send anything — just ask. Files are shared only with the linguists assigned to your job, and they are under confidentiality agreements with us. If you need files deleted after delivery, tell us and we will do that, though keeping the translation memory helps with future updates.

Yes. There is a minimum charge to cover setup and review, but a single certificate, letter or product label is fine. Small jobs often turn into regular work, so we treat them the same way — native translator, second-person check, delivered on time.

Only when you ask for it. We never deliver raw machine output as finished work. If your budget or volume suits it, we offer machine translation with full human post-editing — a linguist corrects every sentence. For anything customer-facing or legally sensitive, we recommend human translation from the start. We will tell you plainly which approach fits your job.

Checking the translation where it will actually appear — on the web page, in the app screen, in the laid-out PDF — rather than in a spreadsheet of strings. Text that reads fine in isolation can be wrong in place: a button label too long, a heading that loses its meaning. We include this pass on website, software and DTP jobs.

Send us the files, the target languages and your deadline. We will come back with a word count, a quote and a delivery date, usually within one working day. On most projects we will translate a short sample free first, so you can judge the quality before committing. No payment is due until you approve the quote.

Reasonable revisions are included. If something is mistranslated or off-tone, send your comments and we fix it at no charge. If you change the source text after delivery, that is new work and we quote for the changed portion only — translation memory keeps that cost small.