From: sirgazil <sirgazil@zoho.com>
To: Laura Lazzati <laura.lazzati.15@gmail.com>,
Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix video repository: First video script commited
Date: Thu, 28 Feb 2019 14:36:41 -0500 [thread overview]
Message-ID: <96c1d004-df3b-0114-483e-e35ce24c32b7@zoho.com> (raw)
In-Reply-To: <CAPNLzUNLV6CF182s3ujJXApnAU-ou7gpcmhBSKEtCMObhR2o7Q@mail.gmail.com>
Hi, Laura, everyone,
El 28/02/19 a las 1:45 p. m., Laura Lazzati escribió:
> On Thu, Feb 28, 2019 at 2:54 PM Laura Lazzati
> <laura.lazzati.15@gmail.com> wrote:
>>
>>> I “installed” the fonts by placing them in ~/.fonts, running “fc-cache
>>> -f” as needed. As long as fc-cache knows about the directory it will be
>>> fine.
> When Ricardo knows, he knows :P.
> My missing step was putting it under ~/.fonts. Will add mabe a fonts
> folder under root dir and then a script to move it to ~/.fonts and run
> fc-cache, WDYT?
>
> Regards :)
> Laura
>
That didn't work for me.
I built the "01-installation-from-script" videos, and found the
following problems:
+ Text is not rendered with the appropriate font (known issue).
+ Firefox 65.0.1 says "Video can't be played because the file is corrupt."
These are the steps I followed to build the videos:
1. $ git clone https://git.savannah.gnu.org/git/guix/videos.git (I got
commit 03930dc)
2. Add missing fonts to $HOME/.fonts
3. $ fc-cache -f
4. $ fc-list ($HOME/.fonts is listed)
5. $ cd path/to/videos
6. $ ./environment.sh
7. [env]# cd 01-installation-from-script
8. [env]# ./buildall.sh
After running these, the videos are available in:
videos/01-installation-from-script/en_US/videos/
The resulting videos don't use the appropriate fonts in my case.
Inkscape, however, which I installed with Guix, renders the video SVGs
with the appropriate fonts.
I imagine the font problem can be solved by packaging those fonts for
Guix and adding them to the environment?
As a workaround to the fonts issue, one can convert the text in the SVG
files to paths. Using Inkscape, you can do so by running it from the
command line using the -T option. For example:
$ inkscape -z -T -l=1-mod.svg 1.svg
As for the corrupted videos, in the Totem video player, the video plays
but black colors are displayed green instead (maybe result of the
corruption?). In VLC the video plays OK, and the colors are fine.
--
Luis Felipe López Acevedo
http://sirgazil.bitbucket.io/
next prev parent reply other threads:[~2019-02-28 19:37 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 23:10 Guix video repository: First video script commited Björn Höfling
2019-02-26 23:20 ` Gábor Boskovits
2019-02-27 8:31 ` Gábor Boskovits
2019-02-27 8:47 ` Gábor Boskovits
2019-02-27 16:04 ` Björn Höfling
2019-02-27 16:41 ` Laura Lazzati
2019-02-27 17:44 ` Laura Lazzati
2019-02-27 17:49 ` Laura Lazzati
2019-02-27 18:18 ` Gábor Boskovits
2019-02-27 18:29 ` Laura Lazzati
2019-02-27 18:37 ` Gábor Boskovits
2019-02-27 17:59 ` Gábor Boskovits
2019-02-27 18:16 ` Laura Lazzati
2019-02-27 15:08 ` Laura Lazzati
2019-02-27 15:04 ` Laura Lazzati
2019-02-27 16:10 ` Björn Höfling
2019-02-27 19:37 ` Laura Lazzati
2019-02-28 2:31 ` Laura Lazzati
2019-02-28 2:40 ` Laura Lazzati
2019-02-28 17:49 ` Ricardo Wurmus
2019-02-28 17:54 ` Laura Lazzati
2019-02-28 18:45 ` Laura Lazzati
2019-02-28 19:14 ` Gábor Boskovits
2019-02-28 21:17 ` Laura Lazzati
2019-02-28 22:13 ` Gábor Boskovits
2019-02-28 23:15 ` Laura Lazzati
2019-02-28 19:36 ` sirgazil [this message]
2019-02-28 21:52 ` Laura Lazzati
2019-03-01 12:20 ` sirgazil
2019-02-28 23:19 ` Björn Höfling
2019-03-01 14:53 ` Giovanni Biscuolo
2019-03-02 3:57 ` Laura Lazzati
2019-03-02 13:36 ` Laura Lazzati
2019-02-28 10:47 ` Giovanni Biscuolo
2019-02-28 17:46 ` Ricardo Wurmus
2019-03-01 11:12 ` Giovanni Biscuolo
2019-02-28 23:03 ` Björn Höfling
2019-03-01 11:01 ` Giovanni Biscuolo
2019-03-01 13:48 ` Björn Höfling
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=96c1d004-df3b-0114-483e-e35ce24c32b7@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@gnu.org \
--cc=laura.lazzati.15@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.