From: Laura Lazzati <laura.lazzati.15@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: GNU Guix Video Documentation
Date: Sun, 28 Oct 2018 20:26:31 -0300 [thread overview]
Message-ID: <CAPNLzUP4xAeOiG9=FyEseTzi4+1q1s9b4C3pXe3wZvYUc2kGKQ@mail.gmail.com> (raw)
In-Reply-To: <CAE4v=pjKyP-O6tOFGezZFcBXBu9W4wHgsYwbJb0C9mcz_6haLg@mail.gmail.com>
On Sun, Oct 28, 2018 at 5:20 PM Gábor Boskovits <boskovits@gmail.com> wrote:
>
> Hello Laura,
>
> Laura Lazzati <laura.lazzati.15@gmail.com> ezt írta (időpont: 2018.
> okt. 28., V, 20:15):
>
> > First, we need to know which have the highest priorities, the
> > promoting, the howtos, and belonging to which topic(s). And in case
> > both (the ones "promoting" as well as the "howtos" are equally needed,
> > I believe that maybe the screencasted one is more appealing, even
> > taking into account that they are difficult to translate or update if
> > they get stale, but it also implies in the worst case creating only
> > one 3 minutes lenght video again on each topic.
> > And then, for the "howtos", I don't know how many 3 minutes length
> > videos will be required for each topic, or the depth of them but the
> > non-screencasted I believe is better, as most of you mentioned.
> > But I kind need to know which are more important at least for now.
> > Recall I am new to Guix :)
>
> I believe one of the most important part of this discussion is to set
> these priorities. It might worth to start a new thread for explicitly
> this, but we can also keep the discussion here. What do you think
> would be preferable?
Yes, please, because based on that I will send you the timeline :) And
I would like to show you the first version ASAP.
Sometimes threads get too long and messy. Because when we end up
replying to a certain part then at least I miss what was before, and
need to read the whole thread to end up writing "X said...". We could
write like a summary of all this thread of mails and start from that
point, WDYT?
>
> > I still have to do more research on texinfo, I read the Reference
> > Guide, but maybe even the slides can be generated with it -LaTex has
> > Beamer, for instance, there has to be something similar to it.
>
> LaTex and Beamer are prefectly acceptable, especially if you are already
> familiar with them. (You will need texinfo to work with the manual) Also,
> currently texinfo lacks some translation capabilities,
> you can ask Julien Lepiller (a.k.a. roptat) on the status of these, but as we
> control the whole process here, these might be ignored. I am think about
> generating code, tests and documentation from the same source for a
> while, but that is a whole new story :-)
Great! Yes I need more explanation on this last part. But let's open
another thread if possible :) Maybe I could contact Julien on IRC
channel.
>
> > > It would be nice to have the ability to translate on demand in the future.
> > > The second version of the graph I have posted is created with keeping
> > > that in mind, that is one of the reasons why it has so many selection and
> > > composition steps. (Another reason is to have a versitality of outputs).
> > Great. I don't know if the translations will be automated and with
> > which tools - Ricardo mentioned that the non screencasted had, among
> > the benefits, easier translations, but I don't know up to which point
> > they will be automated. I read about the tools for the localization
> > of the command line commands, but the audios and text (both subtitles
> > and the slides) will be that easy to translate with scripts? That's
> > why I though about texinfo- i don't know if by slideshow you mean the
> > non-GNU slideshow or any other tool.
>
> The audio translation would have to be done using a recording,
> video+audio of a narrator, we can't actually do any better :-)
> The only thing I propose here, is to break down the recoding to
> short cuts, so that we can do this in smaller parts. That's why I
> presented this part as a 'set of clips' in my description.
>
> The subtitles translation can be done using a base subtitle file/
> subttile database and a separate set of translation files. That
> way the translations can simply be sent to translators, and
> work can be parallelized, like it is done for guix, and the manual.
Ok,let me see if I am understanding. For the audio, some people will
have to say "I speak X language" and narrate that part, By video you
mean for screencasted, like changing the people that appear? I thought
that maybe only replacing the audio was OK. When I did my little
research about concepts for videos, I read that you can mute the
original video, and add another voice, even if the lips don't match,
and even add the options of choosing subtitles (For example: have the
video with English speaker and choose not to add the subtitles, or add
english/spanish/french/choose whatever language you like, too, even
some of them are made with extra comments like [writing on a board] -
I don't remember the name of that - or have the video in Spanish and
do the same. For non-screencasted translating the slides and CLI
comands I thought it was easier. I could do the spanish translations,
at least for the subtitles, but if we can parallelize that, the
better.
>
> Best regards,
> g_bor
Regards!
Laura
next prev parent reply other threads:[~2018-10-28 23:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 12:39 GNU Guix Video Documentation Gábor Boskovits
2018-10-25 21:53 ` Björn Höfling
2018-10-26 4:13 ` Ricardo Wurmus
2018-10-26 6:22 ` Gábor Boskovits
2018-10-26 9:59 ` Giovanni Biscuolo
2018-10-26 10:00 ` Björn Höfling
2018-10-26 11:09 ` Gábor Boskovits
2018-10-28 0:32 ` Laura Lazzati
2018-10-28 9:13 ` Gábor Boskovits
2018-10-28 19:14 ` Laura Lazzati
2018-10-28 20:19 ` Gábor Boskovits
2018-10-28 23:26 ` Laura Lazzati [this message]
2018-10-29 8:17 ` Gábor Boskovits
2018-10-29 12:47 ` Laura Lazzati
2018-10-29 9:10 ` Björn Höfling
2018-10-29 12:49 ` Laura Lazzati
[not found] <CAG=FMuXO7X0j-D_SMWNgxO0p_0xsyJ_eahDGDjtuv465Y3Xk0A@mail.gmail.com>
2018-10-25 6:17 ` Björn Höfling
2018-10-25 9:18 ` Gábor Boskovits
2018-10-25 16:25 ` Larissa Leite
2018-10-25 16:52 ` Gábor Boskovits
2018-10-29 9:31 ` Gábor Boskovits
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='CAPNLzUP4xAeOiG9=FyEseTzi4+1q1s9b4C3pXe3wZvYUc2kGKQ@mail.gmail.com' \
--to=laura.lazzati.15@gmail.com \
--cc=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).