2 replies to this topic

[Kargor]

Well, I just tried to upload an srt file, and keep getting this message.

The file works fine when I play it, so I played around with some details. Changed the line endings from "DOS" (CR-LF) to "Unix" (LF), which didn't make a difference. Then I noticed that the last line in the file doesn't have a line-end at all, so I added one. No change either.

As it's an english file, I don't think there should be any "weird" characters in it. Still, I don't know what the encoding SHOULD be... it's just that the two most likely candidates, UTF-8 and Windows-1252 (which in turn is a superset of ISO 8859-1) are both supersets of ASCII so it shouldn't make a difference for english texts.

What ARE the precise requirements for an srt file to be accepted?

I did check the other recent thread, but they just solved their problem with not much of an explanation :-) Besides, it may or may not be the same problem here.

[Kerensky]

As long as the file follows strictly the subrip (.srt) format, should be fine.
The web should handle most encoding (UTF-8, ISO 8859-1, etc) but not Unicode (as Alex1969 pointed out).

The subrip format is:

<Line Number>
<HH:MM:SS,mmm> --> <HH:MM:SS,mmm>
<Text>
<Text>
...
<Text>
<Blank line>

The most common errors are:
1) The time code has "." instead of "," for milliseconds
2) The arrow it's "->" instead of "-->"
3) No blank line between the srt lines.

Also, subtitle needs to have at least 2 blank lines at the end.


The easiest way to solve this errors, it's to read the subtitle with some error tolerant subtitle app
(like Subtitle Workshop, Subtitle Edit or Transcript Annotations Cleaner) and just save it.

Edited by Kerensky, 04 October 2011 - 07:52 AM.

[Alex1969]

If the encoding of the srt file is Unicode, you get an error message, so you'll just have to save it as UTF-8 or ANSI.