Prevedite SRT datoteko podnapisov, ne da bi jo poškodovali

An SRT file looks plain because it is plain. It is a text file, but it has a strict shape, and every block in it repeats the same four parts in the same order.

1
00:00:04,200 --> 00:00:07,850
Thanks for joining today's call.

2
00:00:08,100 --> 00:00:11,400
We will start with the roadmap update.

Read that as four pieces. A block number, counting up from one, so a player and an editor both know the sequence. A timecode line, giving a start time and an end time separated by an arrow. The subtitle text itself, which can run to two or three lines. Then a blank line, which marks where one block ends and the next one begins.

A timecode is simply a clock reading written as hours, minutes, seconds, and thousandths of a second. It tells the player the exact instant to show a line of text and the exact instant to remove it again. Nothing in that line is meant to be read as language. It is a number format, not a sentence.

This is exactly what a general translation tool does not know. It sees a page of text and translates everything on it, including a line like 00:00:08,100 --> 00:00:11,400, which is not language at all but gets treated as if it were. It also has no concept of "this blank line matters" or "this number is a counter, not a word to reorder." A subtitle-aware workflow treats the block number and the timecode line as fixed structure, and only sends the actual dialogue text through translation.

Paste an SRT into a general-purpose translation site and a few things typically happen at once. The block numbers can get shuffled or dropped if the tool reflows the paragraph breaks. The timecodes can be reformatted, spaced differently, or have their separators altered, since the tool has no reason to know that --> is load-bearing syntax rather than a stray character. Adjacent blocks can get merged into one paragraph if the blank line between them does not survive the round trip.

The result is a file that still looks roughly right if you skim it, but no longer parses as valid SRT. A video player reads the structure strictly. If a timecode line is malformed or a block number is out of sequence, the player can refuse the whole file rather than showing you a file that is merely a little off.

Here is the same sequence without the schema markup.

That is the whole workflow, and it is a desktop one. Translation runs on macOS, Windows, and Linux. It is not available on the iPhone, iPad, or Android apps today.

Getting the file to still parse as valid SRT is the mechanical half of this job. The other half is judgment, and no translation step, subtitle-aware or not, can finish it for you.

Text expansion. Translated text is very often longer than the original. German and Spanish are the two languages people run into this with most often, since a phrase that fits comfortably in English can run thirty percent longer once translated. Subtitles are read at a pace, not just displayed, so a line that used to fit its two seconds on screen can now be too long to read in that same window. The timecodes themselves do not change during translation, only the text does, which means a line that was already tight can now overrun. Trimming a translated line to fit its original timing is a manual edit, not something translation can decide on your behalf.

Names, brands, and technical terms. A general-purpose translator, and even a good subtitle-aware one, will sometimes "translate" a proper noun that was never meant to change. A person's name, a product name, a piece of jargon specific to your field. These are worth a dedicated pass through the translated file, checking each one against the source rather than assuming the translation left them alone.

Tone, idiom, and humour. A joke or a turn of phrase that lands in the source language does not always survive a literal translation. This is true of any machine translation, not a limitation specific to subtitles, and it is the reason a translated dialogue track intended for a real audience benefits from a human pass, particularly anywhere the humour or tone is doing real work.

A subtitle-aware translation keeps the file valid. It does not promise the translated line fits on screen for the same two seconds, and it does not promise a joke still lands. Those are checks a person still has to do.

Yaps

A subtitle file is also often the most exposed part of a video project. It is plain readable text sitting right next to unreleased footage or a client's dialogue, and a general translation site is a third-party service that file does not need to pass through. Keeping the translation step on the same machine that holds the footage removes that exposure entirely.

Do not treat a translated SRT as finished the moment the export button is pressed. Run through this before it goes anywhere near an audience.

That last item is the one people skip because it feels redundant after reading the file in a text editor. It is not redundant. A file can look completely correct as text and still be wrong once a player renders it, because a text editor does not show you reading speed, line wrapping on screen, or whether a block was quietly merged with its neighbour. Watch several minutes of the video with the translated track loaded before you consider the job done.

If you still need to generate the source SRT in the first place, the earlier section of this guide links to that walkthrough. For a quick one-off without installing the desktop app, Yaps also has a browser-based subtitle generator. The translation step covered in this guide is part of Yaps' translation feature, running on the desktop app.

Why does pasting an SRT into a general translator break it?

A general translator sees the whole file as one page of text and translates everything on it, including the timecode lines and sometimes the block numbers. It has no way to know that 00:00:08,100 --> 00:00:11,400 is not a sentence. A subtitle-aware translation step keeps the block numbers and timecodes separate and only translates the dialogue text.

What is a timecode?

A timecode is a clock reading written as hours, minutes, seconds, and thousandths of a second, marking the exact moment a line of dialogue should appear or disappear. It is a number format for a video player to read, not language, which is why it should never be run through a translation step.

Will the translated file have the same timestamps as the original?

Yes. Translating an SRT changes the dialogue text in each block, not the timing. The start and end timecodes carry over exactly as they were in the source file, which is what keeps the translated subtitles synced to the same moments in the video.

What is the difference between SRT and VTT for translation?

Both are plain text subtitle formats with the same underlying idea, numbered blocks paired with start and end timecodes. SRT is the older and more broadly supported format across editors and players. VTT is built for web video players and adds some styling options SRT does not have. Yaps works with SRT files, which cover the large majority of players and upload forms.

Why does the translated text sometimes not fit the time it is on screen?

Translated text is frequently longer than the original. German and Spanish are two languages this shows up in often, since a phrase that reads comfortably in English can come out noticeably longer once translated. Because the timecodes do not change, a line that fit its window before translation can now be too long to read comfortably in that same window, and may need manual trimming.

Does Yaps translate the timing, or just the text?

Just the text. The timing in an SRT file comes from when the dialogue was actually spoken, and translation does not move it. If a translated line now runs long for its window, that is something you adjust yourself rather than something the translation step recalculates.

Which file types can Yaps translate?

Yaps translates .srt, .md, and .txt files, along with a note or a selected paragraph directly inside the app. For subtitles specifically, feed in the SRT you already have and export the result as a new SRT.

Do I need an internet connection to translate an SRT file?

Once the app and the relevant translation model are installed, translation runs on the device with no connection needed. Some language pairs require downloading an additional translation model the first time you use them, which does need a connection for that one-time step.

Which platforms can translate an SRT file?

Translation runs on the Yaps desktop app for macOS, Windows, and Linux. It is not available on the iPhone, iPad, or Android apps today.

Can I translate subtitles on my phone?

Not currently. Translation, including subtitle translation, is a desktop feature. The mobile apps handle dictation, file transcription, and other functions, but translating a file into another language is done through the desktop app.

How good is the translation quality?

It depends on the language pair and the content, and it should be treated as a strong first pass rather than a finished product. Dialogue with idiom, humour, or heavy jargon benefits from a human read-through afterward, the same way any machine translation does. This is not specific to subtitles.

Will names and brand names get translated by mistake?

Sometimes, yes. A translation step can occasionally treat a proper noun as an ordinary word and translate it. Spot-check names, brand terms, and technical vocabulary in the translated file against the source rather than assuming they were left alone.

Do all language pairs work without extra setup?

Most common pairs translate without any extra step. Some language pairs require downloading an additional translation model before the first run, and this is flagged plainly when it applies rather than failing silently.

Why does a playback test matter if the file already looks right in a text editor?

A text editor shows you the words, not how they behave in a player. Reading speed, on-screen line wrapping, and whether a block silently merged with its neighbour are things you only catch by loading the file into an actual player and watching a stretch of the video. Do this before you consider a translated subtitle file finished.