From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39516) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1drMPm-00083H-TW for guix-patches@gnu.org; Mon, 11 Sep 2017 06:58:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1drMPi-0002NU-Dz for guix-patches@gnu.org; Mon, 11 Sep 2017 06:58:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:51892) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1drMPi-0002NQ-Av for guix-patches@gnu.org; Mon, 11 Sep 2017 06:58:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1drMPi-00068l-0t for guix-patches@gnu.org; Mon, 11 Sep 2017 06:58:02 -0400 Subject: [bug#28404] The complete Google Noto Fonts Resent-Message-ID: Date: Mon, 11 Sep 2017 10:57:04 +0000 From: ng0 Message-ID: <20170911105704.dfd7kcijb2ncjbdu@abyayala> References: <20170910090628.mltsqkaepyh3xncd@abyayala> <87shftbpx1.fsf@gnu.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="cy5ahdo7t7qycup3" Content-Disposition: inline In-Reply-To: <87shftbpx1.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 28404@debbugs.gnu.org --cy5ahdo7t7qycup3 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s transcribed 1.2K bytes: > Hi ng0, >=20 > ng0 skribis: >=20 > > 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). >=20 > Woow, impressive piece of work! Thanks. > > The only things which really are unique are: > > filenames + name + variable name + hash >=20 > To me, that clearly suggests that we need a function to produce the > package, like: >=20 > (define (google-noto-font-package name hash) > (package > (name (string-append "font-google-" (camel-case->hyphens name))) > =E2=80=A6)) >=20 > Could you look into that? I thought about this while I worked on it, but I was running out of free time. I'll see if I can resolve this. I'll get back to this thread with questions or results. > > 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. >=20 > That=E2=80=99s a bummer. Are you sure there=E2=80=99s no versioned URL s= omewhere? I'm absolutely sure that there is no official download link with versions. This problem is a basic condition in the font distribution, you have met a happy exception if you have some kind of version in the name of the distributed archive file and even more so when you have no file updating in place. If we find no other solution, my server is located in Germany, has enough diskspace (fonts aren't that big) and I have fair-use uncapped bandwidth (if I hit some kind of TBs/month limit, monthly fee will be adjusted. same network, different server: 40+ TB tor node was okay). I would not be happy with this, but I'd do it. Google should provide versio= ns but try to get Google to do anything which is not giving up on projects in ramdon patterns=E2=80=A6 :/ People and projects already fail with Chromi= um requests, no idea if I can convince them to version the fonts. It's not like they don't have the diskspace. > Alternatively, could we build from source with FontForge or something? Well they are build from source, and the source is on github. for cjk: https://github.com/googlei18n/noto-cjk not cjk: https://github.com/googlei18n/noto-fonts emoji: https://github.com/googlei18n/noto-emoji and they seem to use noto-tools for building, but I haven't looked into the build process at all. We want to avoid download large source repository checkouts or large tarballs, this was one of the problems this project was set out to solve. If someone could look into the build process and describe it here and how big the repositories are, this would save a good amount of time for me (can't look into it that much this week I think). > An example of that is =E2=80=98font-linuxlibertine=E2=80=99. >=20 > Thanks, > Ludo=E2=80=99. >=20 --=20 ng0 GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588 GnuPG: https://krosos.org/dist/keys/ https://www.infotropique.org https://www.krosos.org --cy5ahdo7t7qycup3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlm2bAAACgkQ4i+bv+40 hYidoQ/+IouRv+6J7Mmapq+/YV8ODELX4BB8o/9UFjPEEeMUReFTI23CZnD11UnA TP7ZJLIjdldXDS1elGWe6tmjKFEcmopWdVuzuiU1ajRvf8XHkOXPnue4bLiBXNjM wEn/E/RsVI1QqcoKm3eGwMqQrciF7//BhQUvbX2CoCbH/Aa4sR90pptT8OB/egwk 4JfV4Qd/qAOjCuOLKAXcNZy9BtQJocv325EDBhUSkLGR1WH3hJX/Zms7KgntvoG8 qVuQR1HKTM5vb5JZRU11jkc3ctzjJ2nnBVd7r2bachhldv/73CBIEgsfBTgmI6d0 qYgCQsZ9FFDyNSNuj995NVbffc0wRPp0+6bsJYQDn3D+uFvlKNgPDVU27OZzlEJp kEYO3yFDA1e82pZEGjEP5KGHyAYPHJrzH3fMMRZAH3Vb2XrRAwc5i5DM58iIz+vm R4oajg4PMc0oOEWjgeKWRwHPty3emAdIgQ40tPxu6aDQDSin547ukDEJZ7PIy1HA HVapY+R+DRSuAx4m6plXK2GHALcwrY/nNLLG4CQ6shuBT/juh5pF+lL2HKnv24Pk 60N4ZMnbdXOaPC6/K97WmkDiIhePXz1ZRwaoSs8uwmWInAR3Ul48N5r61t3lrI+n gMPUvzWaivSWsi8C959L+PG5c1VGSbrLngCw+cif7TbM5ZvcN2o= =vbGV -----END PGP SIGNATURE----- --cy5ahdo7t7qycup3--