Choose a localization vendor for Turkish, Arabic and Balkan markets on five criteria: native linguists for each market variant, proven right-to-left and multi-script handling, a documented review and QA process, fit with your translation tools and certified information security. Test every claim in a free pilot on your own content before you sign. El Turco is a London-headquartered localization vendor for enterprises, with native linguists in every market, production in Istanbul and certification to ISO 17100 and ISO/IEC 27001.
This guide is written for enterprise localization managers who are adding Türkiye, the Middle East or Southeastern Europe to a product or content roadmap. It explains why these markets need a specialist approach, compares the main vendor models and gives you a checklist to use in an RFP.
Why do Turkish, Arabic and Balkan markets need a specialist approach?
These markets sit close together on a map but behave very differently in a localization pipeline. One program can involve a right-to-left script, a language written in two scripts and a language whose grammar breaks simple string concatenation. A vendor that treats the region as one market with one style guide will deliver text that is readable but wrong for the reader.
What makes Turkish content hard to localize?
Turkish is agglutinative. Suffixes attach to words and change with vowel harmony, so a placeholder such as a player name or a product name can need a different suffix depending on the value. Strings built by concatenation often break. Turkish also has a dotted and a dotless i, so uppercase and lowercase conversion needs locale-aware code. The brand also has to settle on formal siz or informal sen as its form of address and keep it on every screen.
What makes Arabic content hard to localize?
Arabic runs right to left. Screens mirror, and any line that combines Arabic with digits, Latin-script brand names or web addresses depends on correct bidirectional handling. Formal content usually goes into Modern Standard Arabic. Marketing copy and game dialogue often work better in a Gulf, Levantine, Egyptian or Maghrebi register. Second-person address in Arabic changes with the gender of the reader and nouns have a dual form, so plural and gender logic in software needs more than a singular and plural pair.
What makes Balkan languages hard to localize?
Speakers of Serbian, Croatian and Bosnian understand each other, yet each language has its own standard vocabulary and spelling. Readers in each market notice the difference. Serbian uses both Cyrillic and Latin script, which means every channel needs a script decision before translation starts. Bulgarian and Macedonian both use Cyrillic with different alphabets and norms. Greek has its own alphabet and drops accent marks in all-caps text. Romanian needs the comma-below letters ș and ț rather than the older cedilla forms that some fonts and legacy systems substitute.
Which vendor model fits a multi-market program?
Most enterprise programs choose between three vendor models. Each one can work. The right choice depends on how many markets you cover, how much engineering support you need and how much vendor management your team can absorb.
| Model | Strengths | Watch out for | Fits when |
|---|---|---|---|
| Large multi-language vendor | One contract for many regions; mature program management | Regional languages may be subcontracted several layers down; less visibility into who translates | You need many languages well beyond this region |
| Single-language boutique or freelancers | Deep expertise in one language; direct contact with the linguist | You manage many vendors, style guides and invoices; capacity limits on large launches | You need one or two languages at modest volume |
| Regional specialist | Native teams across related markets; one process for right-to-left, Cyrillic and Latin content | Confirm coverage for every language you need and ask how languages outside the region are handled | Your roadmap centers on Türkiye, the Middle East and Southeastern Europe |
What decision criteria should carry the most weight?
Weight criteria by risk, not by price alone. A translation that fails in-market review costs more in rework and delayed launches than one that was right the first time.
Native linguists for each variant
Ask who translates and who reviews each language. Confirm that both are native speakers of the variant you ship, such as Gulf Arabic for a Saudi campaign or Latin-script Serbian for a web store. A second linguist should review every job.
Script and layout engineering
Ask how the vendor tests right-to-left layouts, bidirectional strings and Cyrillic or Latin output in context. Review in the build or on screenshots catches truncation and mirroring errors that a file-only review misses.
A documented quality process
Look for a written process: translation, editing and proofreading (TEP), automated QA checks and linguistic quality assurance against an agreed error typology. ISO 17100 certification shows that the translation process is audited. ISO 18587 covers machine translation post-editing if you plan to use MTPE.
Tool and workflow fit
The vendor should work inside your TMS or CAT tool rather than asking you to email files. Ask how translation memories and termbases are handed over. Ask how continuous updates reach the vendor without manual steps.
Security and compliance
Enterprise content often includes unreleased products, customer data or regulated material. Ask for ISO/IEC 27001 certification, an NDA for every linguist and a clear statement on whether your content can be used to train public models.
How should you run a pilot before signing?
A pilot is the cheapest way to test vendor claims. Use real content from your own product, not a generic sample. Pick a slice that contains the hard parts: strings with placeholders, a marketing headline, a right-to-left screen and any content that must ship in two scripts.
- Send the same brief you would send in production, with style guide, glossary and reference material.
- Ask for the translation plus a short QA report that lists the checks run and the issues found.
- Have an in-market reviewer score the output against an agreed error typology rather than personal preference.
- Note how the vendor handles questions. A good team asks about context before it translates.
- Compare onboarding effort as well as output quality.
Which questions belong in your RFP?
Use this checklist to compare vendors on the same terms. Ask for written answers and evidence instead of adjectives.
- Which of our target languages and variants does your own linguist network cover? Which do you subcontract?
- Who reviews each job and what qualifications do reviewers hold?
- Which ISO certifications do you hold and can you share certificate copies?
- Which TMS and CAT tools do you work in and how do you connect to ours?
- How do you test right-to-left and multi-script output in context?
- Which automated QA checks run on every delivery?
- How are pricing and turnaround set? What happens with small urgent updates?
- Can we run a free pilot on our own content before we commit?
What are the warning signs during vendor selection?
Some answers suggest that a vendor has not worked in these markets at depth. Treat the following as reasons to dig deeper before you shortlist.
- One reviewer named for Serbian, Croatian and Bosnian with no variant-specific checks.
- Arabic offered as a single language with no question about dialect or audience.
- Rates quoted before the vendor has seen a single file or asked about scope.
- No QA report with the pilot delivery.
- A turnaround promise made before scoping.
- Vague answers about who translates and where your files are stored.
How El Turco handles this
El Turco is a regional specialist. Founded in Istanbul in 2016, the company is headquartered in London and keeps its production team in Istanbul. A network of 700+ vetted native linguists covers 19 target languages in Turkish, Arabic, Persian, Balkan and Turkic markets. Arabic projects can target MSA or a Gulf, Levantine, Egyptian or Maghrebi variant.
Translation follows TEP, so a second native linguist reviews each job before it ships. Before delivery, every file is checked in What's Wrong?, El Turco's own QA tool. Xbench or Verifika reports are added when a client asks for them.
El Turco is certified to ISO 17100, ISO 18587, ISO 9001 and ISO/IEC 27001. Linguists work under NDA. Projects run in the tools clients already use, including RWS Trados Studio, memoQ, Phrase, XTM Cloud, Smartcat, Crowdin and Transifex. For continuous localization, Hub, our in-house middleware, links the client TMS to our project system so updates arrive without manual handoffs.
Enterprises can start with a free pilot or a free test translation of up to 300 words. Pricing is per-word, hourly or project-based, quoted after scoping. Turnaround is agreed at scoping, with a 24-hour option for small urgent updates.