From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: Is font-google-noto toooooo big as a font package? Date: Tue, 8 Aug 2017 11:45:41 +0000 Message-ID: <20170808114541.zrls6vybowwavyj4@abyayala> References: <87pod1z1id.fsf@163.com> <87r2xf5fck.fsf@gnu.org> <31124b25.a25c.15d50edf50d.Coremail.tumashu@163.com> <87pocy12jy.fsf@gnu.org> <20170718124017.udjqs4m4fo7evyjt@abyayala> <87h8y8maep.fsf@gnu.org> <20170719225029.szwrdekfpchazw7z@abyayala> <20170808110909.d3lpwzo2efrykb6p@abyayala> <20170808113552.g3oevoqvd3hjqlqx@abyayala> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="4gvdzcjgisisaqla" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42976) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1df2xg-00059W-Eu for guix-devel@gnu.org; Tue, 08 Aug 2017 07:46:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1df2xb-0001ti-7f for guix-devel@gnu.org; Tue, 08 Aug 2017 07:46:12 -0400 Content-Disposition: inline In-Reply-To: <20170808113552.g3oevoqvd3hjqlqx@abyayala> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= , tumashu , guix-devel --4gvdzcjgisisaqla Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable ng0 transcribed 3.7K bytes: > ng0 transcribed 3.3K bytes: > > ng0 transcribed 2.3K bytes: > > > Ludovic Court=C3=A8s transcribed 0.7K bytes: > > > > ng0 skribis: > > > >=20 > > > > > Ludovic Court=C3=A8s transcribed 0.2K bytes: > > > > >> Hello, > > > > >>=20 > > > > >> tumashu skribis: > > > > >>=20 > > > > >> > the first thing is improve font-build-system to support split = package easy > > > > >>=20 > > > > >> Good point, though I think we also need to find out how we would= split > > > > >> it, which may not be that simple. > > > > >>=20 > > > > >> Ludo=E2=80=99. > > > > >>=20 > > > > >>=20 > > > > > noto-cjk is offered in different packages and blends: > > > > > https://www.google.com/get/noto/help/cjk > > > > > noto itself is offered on the website in many different > > > > > blends aswell: > > > > > https://www.google.com/get/noto/ > > > >=20 > > > > So maybe we could make the CJK part a different output or a differe= nt > > > > package? > > > >=20 > > > > Ludo=E2=80=99. > > > >=20 > > > >=20 > > > Depending on how active the sources change (I see no version in the > > > names of the files) we could take every part and move it to their own > > > package, and let "google-font-noto" became a metapackage for those who > > > need/want the entire set. > > > Even cjk can be a meta set, as all the CJK fonts are split. > >=20 > > Our current noto package isn't any different than the ones offered on > > their website: It is versioned (probably from github or a news announce= ment), > > but the file is not really versioned, and our downloaded file into the = store > > is not versioned aswell. > >=20 > > Now we have two options: Switch to their github repositories for the do= wnloads, > > where they are versioned, or use all the individual files from the noto= website: > >=20 > > - https://www.google.com/get/noto/ > > Noto fonts except for CJK and emoji: https://github.com/googlei18n/noto= -fonts > > Noto CJK fonts: https://github.com/googlei18n/noto-cjk > > Noto Emoji fonts and the toolchain to generate Noto Emoji fonts: https:= //github.com/googlei18n/noto-emoji > >=20 > > I'm in favor of just using the unversioned fonts from the > > google website because they are a) upstream b) bigger than > > github (I'm positive that they have their fallback options) > > and c) the files are reasonable grouped in archives. >=20 > I started working on these fonts. I think it's okay if I throw > them one by one onto the bugtracker, I won't be able to do all > of them. I'll submit two which can give you a start for the ones > afterwards, all based modular on the first one, inheriting from > it. Actually they should be independent, so that there's not too much breakage if one updates slower than the other when they replace the files with a newser one (damn it Google, can't you just provide versioned zip files with the sheer mass of diskspace you have...). > Also I have an idea on how to fix some of the fonts which are not > using the font-build-system. --=20 ng0 GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588 GnuPG: https://n0is.noblogs.org/my-keys https://www.infotropique.org https://krosos.org --4gvdzcjgisisaqla Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlmJpGUACgkQ4i+bv+40 hYiKEg//dVNP8u43nHY5MiUZd6THjKSb1E8lQFxBFfDPxbbkLMwsIEsKW0oABrHL Hc3yelc7LLwTcAYphYxzVYxSrnPLu5ENxfdHtQYzMhymVPZX7jPC5B/ERff63Jdn tt22vOmKxsQT3xL3HEZV5PIlRGR1bStZEOtKbJZQ2mBQybVs8VqnaQ5bjK+tbWGN GzhwjF2ns64V0iu+GIRephkCXyvd+EbJRGEII2tr+dcwVKbB474Du7KCrKULMDFL QC0wy01AkKE9IlZNTpkopD4HYBHNSkxSyvUsShjEArhcbQbCwZeHJH0Ob3V0Hexq VQWel7QOuBtJSVb31c0ZIksNg65Q5ZfwVlKGFsUuP7P5HOxQR5TYhY+ATlniX30v hDJcDqkC+KVK1VuvSS2EAbYMJTvHWr7g7gLAYyQ0EY38dJDfNUPf3X/u1HNnSz9w oGaMkJ9ddLvU5eRNwFGysZei+Ikt8E/kR6/SUa2eO0TEZuaSPQsFbv1b1+/kMkw/ /dOuch8CUINsdPYR9R2YXIa6og7EpS/p+lLgdSU0mty7WaBk2w6FZa5nzY5QLDPS lBQ+trV24kzzyKr4r5c7s4Izwt5oDt6SkVlBBnAzPEQ1Kw1lqfawDFqSyVHPUbFa r94XBsawRVypP4SkqnfC8V8lf/PVbrbAWy8wmpkZEPf0SKck7yI= =Fjyu -----END PGP SIGNATURE----- --4gvdzcjgisisaqla--