A subtitle has two enemies, and neither of them is the source language. One is the box — the width of the line. The other is the clock — how long that line stays on screen. Everybody talks about the box. Almost nobody pays for the clock.
Here's the thing that took me years to say out loud: subtitling Turkmen is not translation. It's triage. You get a spoken line, you get a slot of maybe two and a half seconds, and you decide what the person watching will never find out. That decision is the work. The typing is the easy part.
Reading speed is the real cage
Professional subtitling runs on characters per second. The common target is around 17 CPS for adults, sometimes stretched to 20, dropped to 12 or 13 for children's content. It's not a suggestion. Read faster than a person can process and they stop watching the picture — they're just chewing text, and the film becomes a document.
Now put Turkmen in that cage. We're agglutinative. Meaning stacks onto the end of the word — case, possessive, tense, the works. A tidy English phrase like "to your houses" becomes one long Turkmen word with a tail of suffixes. So a line that fits English CPS blows past the Turkmen limit not because I translated badly, but because the language physically takes up more room per idea.
So I cut. And cutting is where the judgment lives.
The amateur cuts words. "He said that he would probably come by later if the weather held" becomes a shorter sentence that still tries to carry every clause. Wrong instinct. The professional cuts information. "Probably" goes. "If the weather held" goes, because the next shot shows rain anyway and the viewer will connect it. What survives: "He'll come later." Three ideas thrown overboard so one arrives on time and readable.
That's not laziness. That's the entire skill. Deciding what the picture already tells the viewer, what the tone already tells them, and what the words therefore don't have to.
The condensation nobody itemizes
Here's my complaint, and it's a rate complaint dressed as a craft complaint. Agencies quote subtitling per minute of runtime or per subtitle. Fine. But that number assumes I'm converting speech to text at a fixed effort. I'm not. On a fast, overlapping dialogue scene I might be discarding 40% of the literal content and rebuilding what's left so it reads at 17 CPS without feeling amputated. On a slow scene with pauses, the same minute is trivial.
Two minutes of runtime, wildly different jobs. The per-minute rate flattens that. It pays me the same for triage and for transcription.
And the condensation is invisible to review. When a reviewer or an agency QA pass reads my subtitle against the audio, they hear "probably come by later if the weather held" and see "He'll come later" and flag it as a missing translation. Omission! I get a query. I have to write back and explain that I didn't miss it — I killed it on purpose, because keeping it would've forced 24 CPS and the line would've flashed by unread. The good decision looks like an error to anyone measuring completeness. The bad decision — cramming it all in — passes the completeness check and fails the viewer.
That's the trap. Our QA tools count what's there. They can't see the cost of what's there being unreadable.
Turkmen has no house style, so you build one
Make it worse: there's no settled Turkmen subtitling convention to lean on. Spanish subtitlers argue about dialogue dashes and where to break a line, but they argue inside an established tradition. Turkmen never got a dubbing or subtitling industry of its own — content came through Russian, and Russian carried its own habits. So when a streamer suddenly wants Turkmen subs, I'm not just translating. I'm deciding, on the fly, questions that other languages settled decades ago.
Where do I break a line so the Turkmen phrase splits at a natural joint and not mid-suffix? Do I use a dash for the second speaker in a two-person subtitle, or does that read as a Russian import to a Turkmen eye? Do I italicize off-screen speech when half my potential audience has never seen the convention and might read italics as emphasis? There's no guide. I write the guide inside my own head and hope the next Turkmen subtitler on the project made the same guesses, which they won't, because there's no guide.
So if you're a PM sending Turkmen subtitling out to more than one person: pick the conventions first. Write them down. Two paragraphs. Line-break logic, dash usage, italics, how to render on-screen text. Otherwise you'll get two files that are both correct and completely inconsistent, and you'll blame the translators for a decision you never made.
The viewer will never know what I threw out. That's the point — if I did it right, they don't feel the absence. They just read the line, glance back at the face, and stay in the story. Somebody has to decide what's missing. Might as well pay for it.