unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Laura Lazzati <laura.lazzati.15@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Outreachy project infrastructure
Date: Wed, 21 Nov 2018 23:28:11 +0100	[thread overview]
Message-ID: <87h8ga2hhg.fsf@elephly.net> (raw)
In-Reply-To: <CAPNLzUM8S5LMQN_DKYoYf5BGOVxZMmFvxfSeD7s-TQ+_g5j8eA@mail.gmail.com>


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
>> 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 — we’d 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’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
talks.

--
Ricardo

  reply	other threads:[~2018-11-21 22:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21 13:51 Outreachy project infrastructure Gábor Boskovits
2018-11-21 14:37 ` Laura Lazzati
2018-11-21 15:34   ` Julien Lepiller
2018-11-21 15:19 ` Ricardo Wurmus
2018-11-21 20:18   ` Laura Lazzati
2018-11-21 22:28     ` Ricardo Wurmus [this message]
2018-11-22  1:13       ` Laura Lazzati
2018-11-22 12:32       ` Thorsten Wilms
2018-11-22 13:12         ` Ricardo Wurmus
2018-11-22 14:23           ` Thorsten Wilms
2018-11-22 20:11     ` Björn Höfling
2018-11-23  1:54       ` Laura Lazzati
2018-11-23  9:04       ` Ricardo Wurmus
2018-11-23 10:24         ` Gábor Boskovits
2018-11-23 11:01           ` Ricardo Wurmus
2018-11-23 11:38             ` Gábor Boskovits
2018-11-23 12:27               ` Ricardo Wurmus
2018-11-25 23:08         ` Björn Höfling
2018-11-26  0:30           ` Laura Lazzati
2018-11-26 14:07             ` Björn Höfling
2018-11-26 15:40               ` Laura Lazzati
2018-11-29 15:19           ` Laura Lazzati
2018-11-29 15:36             ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h8ga2hhg.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=laura.lazzati.15@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).