From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@infotropique.org>
Cc: 28404@debbugs.gnu.org
Subject: [bug#28404] The complete Google Noto Fonts
Date: Mon, 11 Sep 2017 10:27:54 +0200 [thread overview]
Message-ID: <87shftbpx1.fsf@gnu.org> (raw)
In-Reply-To: <20170910090628.mltsqkaepyh3xncd@abyayala> (ng0@infotropique.org's message of "Sun, 10 Sep 2017 09:06:28 +0000")
Hi ng0,
ng0 <ng0@infotropique.org> skribis:
> These patches add all of Google Noto font.
>
> Be aware that you will need at least 600 MB for the source tarballs.
> There are only 5 real big tarballs, the rest is small.
>
> You will have 86 or 87 patches, so if you want to test it in another
> way try adding my guix developer repository at
> https://gitweb.krosos.org/ng0_guix/guix if I fixed it
> (otherwise git://git.krosos.org/srv/git/ng0/ng0_guix/guix works).
Woow, impressive piece of work!
> The only things which really are unique are:
> filenames + name + variable name + hash
To me, that clearly suggests that we need a function to produce the
package, like:
(define (google-noto-font-package name hash)
(package
(name (string-append "font-google-" (camel-case->hyphens name)))
…))
Could you look into that?
> As Google (and 99% of all fonts out there) update in place,
> I have a versioned inofficial mirror directory in case we
> should ever want to use it.
That’s a bummer. Are you sure there’s no versioned URL somewhere?
Alternatively, could we build from source with FontForge or something?
An example of that is ‘font-linuxlibertine’.
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-09-11 8:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 9:06 [bug#28404] The complete Google Noto Fonts ng0
2017-09-11 8:27 ` Ludovic Courtès [this message]
2017-09-11 10:57 ` ng0
2017-09-11 11:55 ` Ludovic Courtès
2017-09-11 12:21 ` ng0
2017-09-12 12:51 ` Ludovic Courtès
2017-09-12 14:51 ` ng0
2017-09-12 15:22 ` Ludovic Courtès
2017-09-25 12:25 ` ng0
2022-01-13 15:23 ` zimoun
2022-01-17 13:16 ` Ludovic Courtès
2022-01-17 14:23 ` zimoun
2022-01-17 16:07 ` Ludovic Courtès
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=87shftbpx1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28404@debbugs.gnu.org \
--cc=ng0@infotropique.org \
/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).