Turkish machine translation post-editing (MTPE)
Light or full post-editing of Turkish machine translation by native post-editors, under ISO 18587:2017.
Native Turkish post-editors bring machine translation to an agreed level, light or full, under the ISO standard for post-editing.
Turkish machine translation post-editing (MTPE) under ISO 18587:2017, by native Turkish post-editors, for LSPs and enterprises. ISO 18587 is the international standard for post-editing machine translation output: it sets requirements for the full post-editing process and for post-editor competences. El Turco is certified to it and agrees the post-editing level, light or full, before production starts.
Turkish MTPE suits high-volume, repetitive content such as product catalogs, help articles and documentation. Marketing, legal text and UI strings with variables are better served by human translation, because that is where engines fail in Turkish. LSPs send MTPE jobs through their CAT tool or portal; enterprises can start with a free pilot on their own content.
Shared workflow: Translation & localization.
Buying for an LSP or an enterprise team? See For LSPs or For enterprises.
Scope
What does Turkish MTPE cover?
- Full post-editing
- The machine draft is brought to the standard of a human translation in terminology, grammar, register and flow. This is the level to agree for anything customers read.
- Light post-editing
- Errors that change meaning or make the text unusable are fixed, and style is left mostly as the engine produced it. Suits internal content and material read once.
- Engine output in your workflow
- For LSP jobs, post-editors work on the MT output in the LSP CAT tool or portal. For direct clients, the engine is chosen for the language pair and content. The client glossary and translation memory are applied before post-editing.
- Sample before scale
- Native linguists post-edit a sample of your own content first and record the error types they find, so the level and the plan rest on your material, not on a generic benchmark.
- LQA sampling
- An LSP or enterprise can add LQA on a sample of delivered segments, scored by category and severity.
Turkish specifics
Where does machine translation go wrong in Turkish?
- 01
Suffix chains
Turkish grammar sits in suffixes attached to a root, and vowel harmony changes their form. Engines drop or swap case, tense and possessive endings in long words, which can change who did what.
- 02
English word order
Turkish puts the verb last. Engine output often keeps the English order, so the sentence stays readable but sounds translated. A full post-edit restructures it.
- 03
Siz and sen
Engines switch between formal siz and informal sen within one document. Post-editors fix the address to the choice in the style guide.
- 04
Placeholders
The suffix after a variable depends on the value that fills it, so engine output around {name} or {count} is wrong for some values. Post-editors rewrite the string so the variable stands alone, or flag it.
- 05
Dotted and dotless i
Engines and tools mishandle İ, i, I and ı in capitals and product names. Post-editors check every all-caps term and name.
- 06
Terminology drift
An engine can translate the same product term several ways in one file. The client glossary decides, and What's Wrong? checks terms against it before delivery.
Process
How a Turkish MTPE project runs
Turnaround is agreed at scoping, with a 24-hour option for small urgent updates.
Scoping and sample
We review content types and volume and post-edit a sample of your own content to see how much correction the engine output needs.
Level and brief
The post-editing level, glossary, style guide and acceptance criteria are agreed in writing before production starts.
Post-editing
Native Turkish post-editors work under ISO 18587 in your CAT tool or ours, such as RWS Trados, memoQ or Phrase.
QA and sign-off
Like every other delivery, each MTPE job passes What's Wrong? (the translation QA tool from Still Needs a Human) and a human sign-off.
Engine feedback
Recurring engine errors are reported to whoever maintains the engine, so they can be fixed at the source.
Who buys Turkish machine translation post-editing?
Other combinations
Language page
Turkish translation and localization
Our home language: native Turkish linguists for software, game, e-commerce and marketing content, plus Turkish AI training data.
Guide
MTPE vs human translation for Turkish and Arabic: when each works
A decision guide for enterprises and LSPs choosing between machine translation post-editing and human translation into Turkish and Arabic.
Same language
Turkish game localization
In-game text, UI, store pages and LQA in Turkish, by native Turkish linguists who play the genres they translate.
Same language
Turkish e-commerce localization
Product catalogs, marketplace listings, checkout and campaigns in Turkish, by native Turkish linguists with MTPE for volume.
Same language
Turkish software localization
UI strings, help content, release notes and store listings in Turkish, with continuous localization through your TMS or localization platform.
Same language
Turkish AI training data
Turkish speech collection, text annotation, RLHF, moderation and MT training data from native speakers, with gold tasks and agreement reporting.
Same language
Turkish linguistic quality assessment
Native Turkish reviewers score translations from any vendor by error category and severity, against your error typology or an agreed one.
Same service
Arabic machine translation post-editing
Light or full post-editing of Arabic machine translation by native post-editors, under ISO 18587:2017.
FAQ
Turkish machine translation post-editing FAQ
What is Turkish MTPE?
Turkish MTPE, or machine translation post-editing, means a native Turkish linguist edits machine translation output until it meets an agreed quality level. El Turco runs Turkish MTPE under ISO 18587:2017, the standard for post-editing machine translation output. Light post-editing fixes errors of meaning only; full post-editing brings the text to the standard of a human translation.
Which Turkish content suits MTPE?
Turkish MTPE suits repetitive, informational content with stable terminology: help center articles, internal documentation and long-tail product descriptions. Turkish marketing, legal text and UI strings with variables stay in human translation, because suffix chains, tone and placeholders are where engines fail. A free pilot on your own content confirms the split before a program starts.
Can LSPs outsource Turkish MTPE to El Turco?
LSPs can outsource Turkish MTPE to El Turco as a regional vendor. Native post-editors work under ISO 18587 in the CAT tool or portal the LSP uses, to the agreed glossary, style guide and post-editing level. Every job passes What's Wrong? and a human sign-off, and the LSP can request LQA sampling on top. A free 300-word test comes first.
Which machine translation engine does El Turco use for Turkish?
The engine is set up per project. On LSP jobs, post-editors work on the MT output in the LSP's own tool. For direct clients, the engine is chosen for the language pair and content and tested on a sample of the client's material, with the client glossary and translation memory applied before post-editing.
How long does Turkish MTPE take?
Turnaround is agreed at scoping, with a 24-hour option for small urgent updates. Volume, the post-editing level and the number of review steps decide the schedule for larger jobs. The account manager confirms capacity before a job is accepted, so every Turkish MTPE deadline is agreed rather than assumed.
Ready to scope Turkish machine translation post-editing?
LSPs can send a free test of up to 300 words. Enterprises can start with a free pilot on their own Turkish content. MTPE is quoted after scoping and a sample of the engine output.
A project manager reads your brief, usually the same working day.