0:00 → 0:05
Accessible subtitles, the difference to a transcript.
0:05 → 0:06
In a transcript:
0:06 → 0:11
"You must never forget how profoundly people like Putin are influenced.
0:12 → 0:17
a segment contains exactly what is being said in the video.
0:17 → 0:21
I can't edit that, and I can't change the length of that segment either.
0:21 → 0:31
Because when I add another language, the segment can't be longer than the one in the previous language, of course.
0:31 → 0:33
But what about subtitles?
0:33 → 0:44
The segments in the transcript are used for dubbing in another language, in other words for my voice over.
0:44 → 0:49
Theoretically, I could just use this transcript as subtitles
0:49 → 0:57
So I could export it. Now, as you can see, when I use the transcripts as subtitles,
0:57 → 1:03
the first line is very long and the second line is very short.
1:03 → 1:05
That's not accessible.
1:05 → 1:10
But I can change that in the alugha dubbr, so what I can do is this:
1:10 → 1:24
I can use this transcript as subtitles again and then the segments are completely identical to the segments from my transcript at first.
1:25 → 1:26
Now it gets exciting.
1:26 → 1:32
When I click on this, every segment is basically red.
1:33 → 1:42
This means that each segment has at least one, but up to eight errors, which alugha checks.
1:42 → 1:44
These errors can be, for example:
1:45 → 1:51
More than 37 characters in one line, as you can see here for example here.
1:51 → 1:57
The numbers 1 to 12 are better spelled out.
1:58 → 2:05
For example, you spell out one and don't use the numeral 1.
2:06 → 2:11
2 lines per subtitle. Subtitles have a maximum of 2 lines.
2:11 → 2:17
So if I have more than 2 lines in a subtitle, I get this error.
2:18 → 2:25
The minimum gap between 2 subtitles is one frame. We also check if they are too closely placed to each other.
2:26 → 2:30
The minimum duration is one second.
2:30 → 2:35
So if a subtitle is too brief, let's use this as an example,
2:37 → 2:41
then they would be so brief that you couldn't read them in one second.
2:42 → 2:48
The minimum gap between 2 subtitles is one frame, we also would display this error.
2:49 → 2:55
Another error is, for example, if there are more than 15 characters per second.
2:56 → 3:00
Let's go back to our subtitles. How can we fix this now?
3:01 → 3:05
We could take a look at the text here.
3:05 → 3:08
We know what's wrong here.
3:08 → 3:12
There are more than 37 characters per line.
3:12 → 3:18
I go to the side by side editor, press shift and enter before "you".
3:18 → 3:23
And now this problem should be solved.
3:23 → 3:29
But accessible subtitles means more than just editing the text.
3:29 → 3:32
Important information would be, for example:
3:32 → 3:39
When there's music in the beginning, I'd put music in brackets.
3:40 → 3:47
There may also be very relevant sounds that you can't perceive visually, for example:
3:47 → 3:50
Knocking at the door.
3:51 → 4:03
If possible, I always edit the text in such a way that it still conveys all the relevant information
4:03 → 4:07
but with the fewest number of words possible.
4:08 → 4:11
Let's take a look at this segment.
4:11 → 4:16
There are two errors: there are more than 37 characters per line
4:16 → 4:21
and the gap to the previous segment is less than one frame.
4:21 → 4:27
Which means the transition between the subtitles is too fast and it's hard to follow.
4:28 → 4:35
In the side by side editor, I could easily adjust the frames here by changing the time.
4:35 → 4:42
Let's just cut 30 milliseconds off and lo and behold, there's only one error left.
4:42 → 4:50
The text is next: "Four, intimidate the people properly, you have an apparatus of fear and you should use it".
4:50 → 4:52
That's the text.
4:52 → 5:03
I can edit it in such a way that the content, the meaning, is still the same as what Mr. Gauck said,
5:03 → 5:09
but complies with the guidelines for accessible subtitles.
5:09 → 5:13
So instead, this is what the text could look like.
5:16 → 5:17
The text is now shorter.
5:17 → 5:25
Now we just have to fix this problem, too many characters per line, so we just add a line break after the comma.
5:27 → 5:32
And lo and behold, all the problems in this segment are fixed.
5:32 → 5:42
So we could go through segment by segment until there are no more visual errors in the dubbr.
5:42 → 5:49
And once we are done, we can of course publish the video subtitles on alugha.
5:49 → 5:59
Generally, subtitles are always prioritized over the transcript, which means that when I create subtitles and a transcript in alugha,
5:59 → 6:05
the subtitles will always be exported first.
6:05 → 6:14
However, if I want to use these accessible subtitles in another program or on another platform, I can simply click export.
6:15 → 6:20
Here I can choose between my dubbing segments and my subtitle segments.
6:20 → 6:24
I can choose to include the voices or not.
6:24 → 6:34
So here we have standard accessible subtitles as SRT, which we can download and use anywhere else.
6:34 → 6:36
I hope I was able to give a brief insight
6:36 → 6:42
into how to edit subtitles in an accessible way and I look forward to your feedback.