![]() ![]() I have similar start-at-square-one questions about foreign-language dubs. More generally, what workflow works for you to create captions and multilingual subtitles? These won't get burned in but uploaded to vimeo and youtube as caption/subtitle tracks. Is this helpful or is it better to do the timing by hand? The resulting text would, no doubt, need to be corrected but it gives an automated start for the timing. I also see that youtube will do automated captioning. I'm starting to learn about dot.sub and amara as subtitling platforms. We created English transcripts using Dragon Dictate followed by human proof-reading of the machine transcription. The videos are educational (think TED-like), about 20 minutes in length and currently hosted on vimeo and youtube. I'd love to get some help up the workflow learning curve. I have the human translators covered but I'm pretty clueless about best-practice workflow. But that would be a bit of an overkill for a < 2 min.I'm just getting started on internationalizing some videos. (And they could record the scripted audio descriptions, integrate them in the original video, then upload this new audio-described video somewhere, create a new Amara page for it, and reuse the text transcripts produced by the various subtitles of the first Amara page to make subtitles for the new page. This could be handy when the person who speaks in another language talks fast, which would make bilingual subtitles cover a big part of the video. You could mark these translated passages with italics and/or indicating the ISO language code (when there is one) of the original text between brackets. Then you can download these subtitles and reupload them as the main language, in your case, Indonesian, and then just translate into Indonesian the parts that are in other languages, without leaving the original. When you download the subtitles, italicized and boldened passages will be marked with the normal HTML tags in the file.Ģ) You could also start with a multilingual set of subtitles, i.e without, in your case, the Indonesian translation for the passages in other languages, using the "Meta: Geo", "Meta: Twitter" or "Meta: Wikipedia" pseudo languages. Two possibly useful hints, though:ġ) You can make italics in the video editor by putting the text between single asterisks. This is what you have done for the video you mention, from your description. There is probably no universal best practice for these videos: you have to decide in each instance, according to the main / other languages proportion and bearing in mind usability for the audience. Thank you very much for this question, Anto. announcement of a conference that took place 6 months ago :D) But that would be a bit of an overkill for a < 2 min. ![]() And as you say, before that, they could italacize the Latin parts in the Metadata: Geo subtitles. The goal of the activity was sort of a hands-on reflection on accessibility and usability of multimedia content, so the teachers stopped there, having got the point.īut in theory, they could download the Metadata: Geo subtitles, reupload them as Italian, and then translate the Latin parts in Italian there. Metadata: Audio Description for scripting an audio description of the parts that are inaccessiblle to blind people.Metadata: Geo for original subtitles in Latin and Italian.Latin for the subtitles of the parts in Latin.So a group of participants in a course for Italian teachers set Italian as the video's language, because there is more stuff in Italian, and used: Maybe an example might make the "meta" stuff clearer: in, the original video is in Italian and Latin, and it has important in-video texts and illustrations from Dante's inferno that are not accessible to blind people. ![]()
0 Comments
Leave a Reply. |