unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Laura Lazzati <laura.lazzati.15@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Outreachy project infrastructure
Date: Wed, 21 Nov 2018 22:13:44 -0300	[thread overview]
Message-ID: <CAPNLzUOD9kEJQBqzoCii98exN83aU7r+Ym=Q7rFNeLm=4xVPXw@mail.gmail.com> (raw)
In-Reply-To: <87h8ga2hhg.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

Hi!


I’ve been using Inkscape for all of my presentations (after exporting to
> PDF).
>
Yes, I was surprised, I would have never thought about it for
presentations. I used it for posters, certificates and so on.


> I would advise against using the asciinema *site*
>
Ok, I take your advice

>
> Yes, but since this workflow would be using gettext we already know that
> it basically works :)  Translation to Spanish is fine.
>
> 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.
>
Wow!  So does the rest agree in using this format?

Can’t hurt to clone that too, but it does not contain slides for past
> talks.
>
Yes, I know, just asked to know which repos are useful to have. I found
them in  https://savannah.gnu.org/git/?group=guix

Regards :)

[-- Attachment #2: Type: text/html, Size: 1964 bytes --]

  reply	other threads:[~2018-11-22  1:14 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
2018-11-22  1:13       ` Laura Lazzati [this message]
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='CAPNLzUOD9kEJQBqzoCii98exN83aU7r+Ym=Q7rFNeLm=4xVPXw@mail.gmail.com' \
    --to=laura.lazzati.15@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).