Script fit
Latin (post-1993)
left-to-right · alphabet- Cyrillic (historical)
- Arabic
Language coverage
Turkmen is a tri-script language, and that is the first thing a project has to settle.
Latin (official since 1993), Cyrillic (Soviet-era publications still in circulation), and Arabic (used by Iranian and Afghan Turkmen) each reach a different audience, so the opening question is always which script your content targets. MoniSa confirms Turkmen coverage per project through a verified network, with every linguist matched to the variety and script the content needs.
Cultural adaptation at scale is the closest available match, with script, dialect, reviewer fit, and content type made explicit before scoping.
Latin (post-1993) LTR
Translation fit
Turkmen scope checkConfirmed on brief is reviewed against audience, script, dialect, content type, and proof need before work is planned.
Language readiness
Script direction, dialect scope, service coverage, and proof context are checked before timing or reviewer assumptions get locked too early.
Coverage model
Turkmen is a tri-script language, and that is the first thing a project has to settle. Latin (official since 1993), Cyrillic (Soviet-era publications still in circulation), and Arabic (used by Iranian and Afghan Turkmen) each reach a different audience, so the opening question is always which script your content targets. MoniSa confirms Turkmen coverage per project through a verified network, with every linguist matched to the variety and script the content needs.
| Service line | Planning status | Dialect scope | Start path | Turnaround note |
|---|---|---|---|---|
| Translation and review | Confirmed on brief | Standard Ashgabat, Iranian | project brief | Confirmed on brief |
| AI data annotation | Confirmed on brief | Standard | project brief | Confirmed on brief |
| Audio transcription | Confirmed on brief | Standard | project brief | Confirmed on brief |
| Subtitling | Confirmed on brief | Standard | project brief | Confirmed on brief |
| Dubbing | Confirmed on brief | Standard | project brief | Confirmed on brief |
Service fit, reviewer continuity, and turnaround are confirmed against the live brief before production begins.
Buyer need
For Turkmen, the buyer risk is script choice, orthography control, and reviewer fit, not generic translation quality. MoniSa confirms script, dialect, reviewer, and service fit against the brief before production begins.
Service answer
Turkmen is an Oghuz Turkic language spoken by approximately 11 million people across Turkmenistan, Iran, Afghanistan, and smaller diaspora communities. Script upheaval defines its modern history: Arabic script replaced by Cyrillic under Soviet rule, then replaced by Latin in 1993. This tri-script legacy means written materials exist in three alphabets. Iranian Turkmen retains Arabic script and carries Persian vocabulary distinguishing it from Ashgabat-standard Turkmen.
MoniSa confirms the reviewer path, review depth, and delivery timing for Turkmen in the project brief. Every assigned linguist is verified for the variety and domain your project needs. We publish coverage and review depth, not the routes we recruit through.
Tri-script complexity creates production challenges that surface at delivery
Turkmenistan's 1993 switch from Cyrillic to Latin left a legacy of older materials in Cyrillic, while Iranian and Afghan Turkmen communities use Arabic script. A project targeting multiple Turkmen audiences may need content in two or three scripts, each requiring a different linguist profile and rendering verification.
Energy sector operations in Turkmenistan need local-language documentation
international companies in the oil, gas, and construction sectors operating in Turkmenistan face requirements for Turkmen-language workplace documentation, regulatory filings, and community communications.
No MT engine produces usable Turkmen output
basic Google Translate support exists but quality is poor. The tri-script situation means no single automated system covers all written variants. Human translation is the only reliable path.
Iranian and Afghan Turkmen communities are distinct target audiences
content for Iranian Turkmen (Gorgan region) uses Arabic script and reflects Persian-influenced vocabulary. Afghan Turkmen content requires yet another linguistic register. These are not interchangeable with Ashgabat-standard Turkmen.
Our Turkmen translation process
All Turkmen work follows MoniSa's 3-layer review model: translator (domain-matched, verified native speaker of the specified Turkmen variety with confirmed script proficiency), editor (bilingual accuracy, Russian/Persian-interference check depending on variety, and terminology adherence), proofreader or community validator (cultural and contextual review). Review depth is set in scope rather than assumed from the language name alone.
Three things are settled at intake: the target variety (Ashgabat standard, Iranian, Afghan, or Yomut), the script, and the domain. Script is a real decision here, since Turkmenistan adopted the Latin alphabet in the 1990s after a Cyrillic period, while Iranian and Afghan Turkmen communities use an Arabic-based script. Together these set the linguist profile, and because qualified Turkmen reviewers are scarce, the timeline is confirmed at scope.
Translation, editing, and proofreading stay tied to that scope, and the work is produced by speakers of the specified variety. For Latin-script output, reviewers hold the text to the current official orthography; for Iranian Turkmen, they check for Persian interference; and Russian interference is watched for with linguists from post-Soviet environments. Terminology and meaning are confirmed alongside the script-specific checks.
You receive the translated files with the script and variety confirmed, and with the review notes needed to accept the work. Where a program runs across more than one script, each version is delivered as its own track with rendering checked, and any later correction keeps those decisions attached to the change.
Backup path
Resource continuity is planned during project scoping. Turkmen timelines vary by variety — Ashgabat-standard confirms faster than Iranian or Afghan Turkmen.
Reviewer path
The same MQM error categories, scoring thresholds, and review stages apply to rare-language work as to any high-resource delivery.
Sourcing status after scope
Sourcing path and review depth are confirmed in the project brief.
Live interpreting
Turkmen work reaches MoniSa mainly as written material, and a spoken request is the exception rather than the rule. When one does arrive it is scoped as its own piece of work rather than folded into a translation quote, because the unit, the screening and the delivery are all different.
Interpreting in Turkmen means a qualified interpreter renders a live conversation between Turkmen and another language, delivered in one of three ways: on an audio call, over a video link, or in the room. It is not translation. Translation produces a written deliverable and is quoted on volume, file type and review depth; interpreting is a live event with a date, a duration and a setting, and is booked as time. That is also how the two appear on a quote, with content on one line and time on the other, so a matter that needs both is scoped as two pieces of work rather than one. MoniSa sources and screens interpreters across 300+ languages and 4,500+ dialects from its network of 110,000+ verified language specialists, and operates under ISO 9001 and ISO 27001 certification.
Screening for a Turkmen session starts with the variety the speaker actually uses, because a near match is not a match once a conversation is under way. The interpreter is then checked in the working pair and screened against the setting the session comes from, so a clinical encounter, a legal proceeding and a school meeting count as separate qualifications rather than one. Everyone assigned signs the confidentiality agreement before receiving access, and named backup coverage is recorded alongside the primary assignment. What MoniSa publishes is the coverage and the screening, never the routes it recruits through.
Audio line
An audio line connects faster than any other modality, which makes it the right route for short, unscheduled exchanges such as an intake call, a benefits query, or an appointment booking, where nothing visual carries meaning.
Over-the-phone interpretationVideo link
A live video link is used when a document, a device, a physical examination or a signed language is part of the conversation, and when the people in the room and the interpreter need to see each other without anyone travelling.
Video remote interpretingClinical setting
A clinical encounter adds a credential requirement and a domain screen on top of the language check, because a summarised symptom or a softened instruction changes the care that follows.
Medical interpreter servicesRelated proof
Cultural adaptation at scale is the closest available match, with script, dialect, reviewer fit, and content type made explicit before scoping.
Related case study
Cultural review and glossary control across indigenous-language streams.
Buyer questions
The questions buyers send before a scope conversation, answered on the page rather than in a meeting. Take them to your team, then send us the one we did not answer.
MoniSa maintains a verified Turkmen network across the main varieties, with availability and handling requirements confirmed directly before any work is scoped. Coverage is confirmed per project, and every assigned linguist is verified for the variety, script, and domain the content needs.
Latin (post-1993 official), Cyrillic (Soviet-era legacy), and Arabic (Iranian/Afghan Turkmen) are all covered through different linguist pools. Each script requires a separate linguist assignment and rendering verification process. For tri-script projects, we deliver each version as a separate linguistic track with cross-script semantic equivalence checks.
Turnaround is confirmed in the project brief. Iranian Turkmen may take longer depending on domain. Turnaround is confirmed in the project brief. Scope, sourcing path, and delivery timing are confirmed in the project brief.
These are treated as distinct linguistic assignments. Ashgabat-standard Turkmen uses the Latin script with Turkmenistan-specific terminology and orthographic conventions. Iranian Turkmen uses Arabic script and carries significant Persian-influenced vocabulary. A linguist proficient in one variety does not automatically qualify for the other. The target audience determines which variety is assigned.
Translation is written: a document, a record, a subtitle track, delivered as content and quoted on volume and review depth. Interpreting is spoken: a live conversation on the phone, over video or in the room, booked as time with a date attached. A hearing, an appointment or a call needs an interpreter; a form, a notice or a record needs a translation, and most matters need both. MoniSa scopes them separately, because the sourcing, the screening and the unit of work differ, and confirms which one the brief actually needs before quoting.
You are told before a date is agreed, not after. Coverage is reported pair by pair as staffed today or needing a recruitment window, with the window stated — in writing, while the scope is still being agreed. Nobody new goes onto live work until a pilot batch has been reviewed and signed off. A coverage claim you cannot check before signing is not coverage.
Next step
A useful brief names the language, content, deadline, review depth, and proof the buying team needs.
Production-ready brief
01Language pair, dialect, and script02Content or data type03Volume and deadline04QA and reviewer requirement05Security and access requirement06Proof needed for buyer approval