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>,
	"Gábor Boskovits" <boskovits@gmail.com>,
	"Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Video subtitles
Date: Thu, 20 Dec 2018 17:03:49 -0300	[thread overview]
Message-ID: <CAPNLzUNb_VCUD6qhXPZaG8dtzrQk4s34CeTXx59xPv+f_O864A@mail.gmail.com> (raw)
In-Reply-To: <87pntwsjmz.fsf@elephly.net>

Hi!

> I have no strong opinions about using “.usf”.  “.ass” may just be fine.
> Apparently, it can be converted to po files for translation with
> “sub2po”, which is part of the “translate” toolkit.  I have no
> experience with this, and I think it would be better to use a format
> that didn’t require even more tools to work with.
I have taken a look at sub2po. I understand that it translates .srt or
.sub files only.
I read it from here:
http://docs.translatehouse.org/projects/translate-toolkit/en/latest/formats/subtitles.html

The following formats are supported for subtitles:
MicroDVD
MPL2
MPsub
SubRip (.srt)
SubViewer 2.0 (.sub)
TMPlayer
Sub Station Alpha
Advanced Sub Station Alpha
BTW, is there a player that you suggest for adding the subtitles?
> Aegisub does not need to be part of the automated process to compile the
> videos.
Thanks, I was quite worried about having to automate the part of
creating the subtitles..  What about Pierre's suggestion of
mkvtoolnix?

Regards!
Laura

  parent reply	other threads:[~2018-12-20 20:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20  1:55 Video subtitles Laura Lazzati
2018-12-20  7:46 ` Pierre Neidhardt
2018-12-20  8:11 ` Ricardo Wurmus
2018-12-20  8:31   ` Pierre Neidhardt
2018-12-20 20:03   ` Laura Lazzati [this message]
2018-12-20 21:26     ` Ricardo Wurmus
2018-12-20 22:14       ` Laura Lazzati
2018-12-21 19:45         ` Ricardo Wurmus
2018-12-20 21:08   ` 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=CAPNLzUNb_VCUD6qhXPZaG8dtzrQk4s34CeTXx59xPv+f_O864A@mail.gmail.com \
    --to=laura.lazzati.15@gmail.com \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    --cc=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).