Re: [proofread] [EN] Ada video subtitles

Ana Galan <[email protected]> Mon, 17 Mar 2025 09:07:11 +0100
Newsgroups gmane.org.fsf.europe.translators
Message-ID <[email protected]>
Dear Nico and Richard,

I am, indeed, happy someone open this topic. After last years' Richard 
mail, I remember I spent some time checking Ada subtitles and they were 
not only sometimes wrong grammatically speaking but also with the 
timing. However, after some time fixing several things, I had to deal 
with other things.

So I would suggest that first Nico and I can try to check the the 
subtitles timing is the right one (that is also useful for the rest of 
the languages) and then, it would be great if Richard can check them one 
last time. I am sorry that this might be also a bit of extra work for 
Richard so we will try to have them as clear and good as possible.

What do you think?

Best,

Ana

On 3/15/25 17:53, Richard L. Schmeidler wrote:
> I suggest dividing the work.
>
> My portion would be to check the subtitles against the spoken 
> narration.  I would use the video at 
> https://media.fsfe.org/w/j1c6LQVZ8qnCLLwpXMuw3MA for the spoken 
> narration.  Should I use 
> https://git.fsfe.org/FSFE/ada-zangemann/src/branch/main/movie/en.srt 
> or some other version of the subtitles?  I would use the book text you 
> suggest for guidance as to what the narrator intended, but I would not 
> be relying on the book text in my work.  If I hear the narrator say 
> something that is not exactly what is in the book text, and the 
> subtitle agrees with what the narrator says, I would accept the 
> subtitle even if it does not agree with the book text.  (I would not 
> be hunting for such cases, but I would report such cases to the extent 
> I notice them.)
>
> Here is an example of the phenomenon from early in my email of October 15:
>
> "3.  29.  After that, he built a cleaning robot and a block sorting
> machine so that his room would - To hear "he built" (when describing
> his daydreams, not his actual accomplishments) seemed so strange that
> I checked the printed text on page 6.  It has "he'd build."  Since the
> subtitles file agrees with the spoken version, it should not be
> changed.  But this is strange.  It is too bad that the spoken version
> has been published."
>
> I have just listened to the video again, months later, and I still 
> hear "built," not "build" or "he'd build"!  If you disagree, it is 
> clear that someone else's hearing should be consulted, not mine.
>
> =====
>
> Someone else's portion of the work would be dealing with issues of 
> timing (and everything else, except comparison of spoken narration and 
> the subtitles).  If I were to deal with documentation of the timing, 
> it would be after this first undertaking of comparison of narration to 
> subtitles.
>
> Do you like this suggested division of the work?
>
> Ana, what do you think?
>
>
> On Sat, Mar 15, 2025 at 11:52 AM Nico Rikken <[email protected]> wrote:
>
>     Hi Richard,
>
>     The emails contain metadata what they reply to. I replied to that
>     email, so I didn't include further context. Maybe I should have.
>     I see this date: Tue, 15 Oct 2024 02:33:32 -0400 (15-10-24 08:33:32)
>
>     For some more context, I'm in the process of adding the subtitles to
>     git so they are on a central place for translation. I started with the
>     subtitles published with the video on media.fsfe.org
>     <http://media.fsfe.org> peertube:
>     https://media.fsfe.org/w/j1c6LQVZ8qnCLLwpXMuw3M
>     I found spelling mistakes in the text that I corrected. It seems that
>     these subtitles originate from an automated tool used by Petter at the
>     beginning of October. I was included in a direct email. The subtitles
>     were almost identical. I corrected some spelling mistakes before
>     committing it to git.
>
>     Discovering your work on the mailinglist, I made a diff with the
>     version by Ana, the version in git and your version. In the pull
>     request I adopted many of your changes, but not the change in timing.
>
>     I just prepared a separate pull request with your timing changes:
>     https://git.fsfe.org/FSFE/ada-zangemann/pulls/102
>
>     I think there are two things to check:
>
>     1. Make sure that the text corresponds to the words of the narrator.
>     2. Check and correct the timing. Long sentences might need to be
>     split.
>
>     For checking and correcting the timing I have good experience with KDE
>     Subtitle Composer https://invent.kde.org/multimedia/subtitlecomposer
>     I used the same software to record a video voiceover
>     https://blogs.fsfe.org/nico.rikken/2020/11/02/recording-a-public-money-public-code-video-translation/
>
>     I added a comment in https://git.fsfe.org/FSFE/ada-zangemann/issues/78
>     about the need for additional verification.
>
>
>     Now that the subtitle is available in a designated place, I would love
>     a final check. I haven't checked it with the video yet.
>     Based on this video: https://media.fsfe.org/w/j1c6LQVZ8qnCLLwpXMuw3MA
>     And this book text
>     https://git.fsfe.org/FSFE/ada-zangemann/src/branch/main/Ada_Zangemann-en.txt
>     These subtitles:
>     https://git.fsfe.org/FSFE/ada-zangemann/src/branch/main/movie/en.srt
>     Or your retimed ones:
>     https://git.fsfe.org/FSFE/ada-zangemann/pulls/102/files
>
>     As said there are dedicated programs like Subtitlecompose
>     available for
>     this goal.
>
>     Thanks,
>     Nico
>
>
>
> -- 
> "The problem with quotes on the internet is that it is difficult to 
> determine whether or not they are genuine." -- Abraham Lincoln

-- 
Ana Galan - Senior Project Manager Communications
Free Software Foundation Europe
Schönhauser Allee 6/7, 10119 Berlin, Germany | t:+49 157 92 34 72 12
Registered at Amtsgericht Hamburg, VR 17030  |(fsfe.org/support)

_______________________________________________
Translators mailing list -- [email protected]
To unsubscribe send an email to [email protected]

This mailing list is covered by the FSFE's Code of Conduct. All
participants are kindly asked to be excellent to each other:
https://fsfe.org/about/codeofconduct