Top Notch Software Localization

Software localisation is adapting a product's interface for another locale - the resource files, the layout, the formats and the build. The work is produced by people and not by software, and what shapes it here is translation across documents, websites, media and software from one supplier, so the deliverable fits how you actually work instead of a generic template. Every file is checked by a second reviewer before it is sent.

The practical part is this: strings are translated in the resource file with their keys and placeholders intact, never in the compiled build. It is agreed with you before anyone starts, because the alternative is a first delivery built on a guess and a second round of work to undo it. The translator works into their own first language, which is what keeps long text readable instead of merely correct.

It depends on length and on how difficult the source is, and the time is in the quote before you commit. Rush delivery within 2 to 24 hours covers the urgent end. Software localisation is scheduled against the people who actually do this work, not against a general pool. Scope is agreed before the clock starts, so a document job, a website and a media file on the same order each get their own realistic date.

Work is done by human linguists and compared with the original before it is sent, which is how the 99+% accuracy standard is met. What gets checked on software localisation is the detail a reader would otherwise have to verify alone: names, figures, terms and anything the source left ambiguous. One person working alone would not catch a detail that is right in one file and wrong in the next.

It is handled by restricting access, not by promising discretion. Software localisation often involves material people would not want circulated, so the file is closed to everyone except the pair working on it. Everyone on the job is under NDA, transfer is encrypted, and your own confidentiality agreement is signed before work starts if you have one.

Word, PDF, Excel, Google Docs or plain text, or your own template applied so the file comes back ready to use. Headings, tables and numbering are built properly instead of pasted in. The format for software localisation is agreed at order stage, so the first delivery is the one you can file, send on or publish.

Send the files or a link, say what you need and when, and an exact quote comes back within minutes. Once you approve it the work goes to a linguist suited to the material. Say what the software localisation is for when you send it, because a filing, a publication and an internal record are formatted differently. Say what the finished text is for - a filing, a launch, a reader - because the brief changes the wording more than the language does. Revisions are free for 30 days after delivery.

A pseudo-localised build is run first, so clipped labels and hard-coded text show up before any translation is paid for. Nothing there is an upgrade, and work that falls outside the agreed software localisation brief is priced separately and only once you have agreed to it. A certified version and a plain working copy can be issued from the same job.

Yes. Software localisation is available in 100+ languages, with every file going to a native speaker of the target language and a reviewer who also reads it. Rarer languages are confirmed as available before the quote goes out, not after you have paid. Where a language is rare, availability is checked before the quote.

Transcription starts at $1 per audio minute and translation at $0.10 per word. Translation is priced per word and certification per page, so you can see which part of the figure is which. Software localisation is quoted from the material you send, so a short job and a long one are worked out the same way. Quotes are calculated from what the material is, how long it runs and how quickly you need it back, so two clients sending comparable material pay the same, and nothing begins until you approve the written total.