[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Outreachy project infrastructure

From: Ricardo Wurmus
Subject: Re: Outreachy project infrastructure
Date: Wed, 21 Nov 2018 23:28:11 +0100
User-agent: mu4e 1.0; emacs 26.1

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’ve been using Inkscape for all of my presentations (after exporting to
PDF).  It’s 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’d need to use multiple
ffmpeg invocations then to “glue” the slideshow and command line
recording segments together.)

>> Translations themselves don’t have to be created as part of this
>> project, but the pot files should be uploaded to the
>>, 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 — we’d only need a common directory structure to store a
bundle of a subtitle file, audio recording(s), and translated source

> 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’t know, but we can figure this out later.
Recording and merging the audio track is an almost purely cosmetic step
— 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’t
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’t hurt to clone that too, but it does not contain slides for past


reply via email to

[Prev in Thread] Current Thread [Next in Thread]