Software and games

What we localise

Interface strings, onboarding and error messages, in-game text and subtitles, store listings, patch notes, support articles, end-user licence agreements and privacy policies. Work usually arrives as a resource file rather than a document — .json, .xliff, .resx, .po, a spreadsheet export — and goes back in the same structure, with placeholders and tags intact. Longer-form material and marketing copy is handled as website localisation; the interface side is software and game localisation.

Four things Turkish does that English does not

• Dotless ı and dotted İ. Case conversion is locale-sensitive: an uppercase routine that does not know it is handling Turkish turns "i" into "I" instead of "İ", and "ı" into "I" as well. It is a classic source of broken comparisons and ugly labels.
• Suffixes instead of prepositions. Turkish adds case endings to words, and the ending depends on the vowels and final consonant of the word before it. A string built as "Go to " + placeholder cannot be translated correctly, because the suffix belongs on the variable. These strings have to be restructured, and we flag them rather than producing something that reads as broken Turkish.
• Plurals. After a numeral Turkish does not use a plural: "iki mesaj", not "iki mesajlar". English plural logic copied straight across produces text that no Turkish player would write.
• Length. Turkish strings often run longer than English, so buttons and fixed-width fields need checking in context, not only in the spreadsheet.

How we work with product teams

A glossary and a style decision on formality — siz or sen, which matters a great deal in games — are agreed before the first batch. Terminology is then held across releases. We deliver in the file format supplied, run a check on placeholders before returning, and can do a linguistic QA pass on a build or a staging environment when screenshots are available. Volume, rates and release scheduling are set terms we agree with you in writing before the first job.

Prices

English into Turkish is from £6.50 per 1,000-character page, with no UK VAT charged: a 30,000-character string file is about £195, a set of patch notes is usually one or two pages, and a full EULA runs to £60–100 depending on length. Machine translation post-editing is available where the content justifies it and is agreed in writing first, with its limits stated rather than glossed over.