From: ng0 <ng0@infotropique.org>
To: 28404@debbugs.gnu.org
Subject: [bug#28404] The complete Google Noto Fonts
Date: Tue, 12 Sep 2017 14:51:56 +0000 [thread overview]
Message-ID: <20170912145156.hqsoffr477hyd7dx@abyayala> (raw)
In-Reply-To: <87mv60yta7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
Ludovic Courtès transcribed 0.3K bytes:
> ng0 <ng0@infotropique.org> skribis:
>
> > Emoji: can be build with "make" given the condition that nototools
> > (https://github.com/googlei18n/nototools/) is available. This in turn
> > depends on (python):
>
> Cool, sounds reasonable.
>
> > Would the tagged tarball of CJK be considered too big for our CI?
>
> No, I think it’s OK.
Ok.
> Ludo’.
>
I propose:
1. package nototools.
2. noto-emoji -> use tagged tarball
2.1 split emoji into the provided fonts of upstream
which are emoji and color emoji, separate
packages.
3. noto-cjk: likewise
4. noto: likewise
The original complain was "noto is too big", so we can not
solve this problem by providing outputs like
noto: out, noto-kufi-arabic, noto-sans-avestan, …
but they have to be provided as separate nar archives.
Annoying: people interested in cjk noto fonts (which are just
5 sub font families by archive file name counting) still have
to download 1.6GB if no binary substitute is available.
Noto (351 MB) is okay, and so is Emoji (33.5MB).
I'll get to it unless you have a better idea?
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://krosos.org/dist/keys/
https://www.infotropique.org https://www.krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-12 14:53 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
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 [this message]
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=20170912145156.hqsoffr477hyd7dx@abyayala \
--to=ng0@infotropique.org \
--cc=28404@debbugs.gnu.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).