From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Outreachy project infrastructure Date: Wed, 21 Nov 2018 23:28:11 +0100 Message-ID: <87h8ga2hhg.fsf@elephly.net> References: <87muq231ca.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34231) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gPayz-00077g-Ja for guix-devel@gnu.org; Wed, 21 Nov 2018 17:28:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gPayv-0006mH-N1 for guix-devel@gnu.org; Wed, 21 Nov 2018 17:28:29 -0500 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21037) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gPayt-0006iw-Vq for guix-devel@gnu.org; Wed, 21 Nov 2018 17:28:25 -0500 In-reply-to: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Laura Lazzati Cc: Guix-devel Hi Laura, >> I would like to recommend this workflow: >> > Thank you very much for the workflow as well as for the suggested tools. I > did not know that slides were created with inkscape :) I=E2=80=99ve been using Inkscape for all of my presentations (after exporti= ng to PDF). It=E2=80=99s more flexible than software made specifically for presentations, but the flexibility comes at the cost of convenience (e.g. in Inkscape you have one file per slide, and to create a slide deck you need to combine all these files to a single PDF with another tool like Ghostscript). In this project I think the flexibility outweighs these minor drawbacks. > I have one question. What about asciinema site for CLI localization? I was > reading more in detail and it says that it is a .json file. I would advise against using the asciinema *site*, but the tool can be used to record command line output. I could not find a tool to convert the recorded JSON file to a proper video. If someone can find one then we could use asciinema for some segments. (You=E2=80=99d need to use multi= ple ffmpeg invocations then to =E2=80=9Cglue=E2=80=9D the slideshow and command= line recording segments together.) >> Translations themselves don=E2=80=99t have to be created as part of this >> project, but the pot files should be uploaded to the >> translationproject.org, which is what we already do for other Guix >> translations. > > I thought that we had to at least try if translations worked, maybe for > only one video. Yes, but since this workflow would be using gettext we already know that it basically works :) Translation to Spanish is fine. > Could we try it for the audio and subtitles too? If we use the usf format for subtitles we can use gettext / itstool for the translations of the subtitles as well. The subtitles also serve as a narration script, really, so no extra step for translating audio files is needed =E2=80=94 we=E2=80=99d only need a common directory structure to = store a bundle of a subtitle file, audio recording(s), and translated source files. > BTW, who is going to use their voice for the audios in English? I have > no problem, but recall it is not my mother tongue. Good question! I don=E2=80=99t know, but we can figure this out later. Recording and merging the audio track is an almost purely cosmetic step =E2=80=94 the narrator would read the subtitles as they are displayed at the correct times. This could be done later in the project, so I wouldn=E2=80= =99t worry about this now. >> from ./talks/icg-2018 from the guix-maintenance.git repository. >> > I did not, I have just cloned it. Should I also clone guix-artwork? Can=E2=80=99t hurt to clone that too, but it does not contain slides for pa= st talks. -- Ricardo