GNU bug report logs - #28404
The complete Google Noto Fonts

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 28404 in the body.
You can then email your comments to 28404 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> infotropique.org>
To: guix-patches <at> gnu.org
Subject: The complete Google Noto Fonts
Date: Sun, 10 Sep 2017 09:06:28 +0000

[Message part 1 (text/plain, inline)]

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).

The only things which really are unique are:
filenames + name + variable name + hash

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.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://krosos.org/dist/keys/
https://www.infotropique.org https://www.krosos.org

[0001-gnu-Add-font-google-noto-sans.patch (text/plain, attachment)]

[0002-gnu-Add-font-google-noto-serif.patch (text/plain, attachment)]

[0003-gnu-Add-font-google-noto-mono.patch (text/plain, attachment)]

[0004-gnu-Add-font-google-noto-coloremoji.patch (text/plain, attachment)]

[0005-gnu-Add-font-google-noto-emoji.patch (text/plain, attachment)]

[0006-gnu-Add-font-google-noto-kufi-arabic.patch (text/plain, attachment)]

[0007-gnu-Add-font-google-noto-naskh-arabic.patch (text/plain, attachment)]

[0008-gnu-Add-font-google-noto-nastaliq-urdu.patch (text/plain, attachment)]

[0009-gnu-Add-font-google-noto-sans-armenian.patch (text/plain, attachment)]

[0010-gnu-Add-font-google-noto-sans-avestan.patch (text/plain, attachment)]

[0011-gnu-Add-font-google-noto-sans-balinese.patch (text/plain, attachment)]

[0012-gnu-Add-font-google-noto-sans-bamum.patch (text/plain, attachment)]

[0013-gnu-Add-font-google-noto-sans-batak.patch (text/plain, attachment)]

[0014-gnu-Add-font-google-noto-sans-bengali.patch (text/plain, attachment)]

[0015-gnu-Add-font-google-noto-sans-brahmi.patch (text/plain, attachment)]

[0016-gnu-Add-font-google-noto-sans-buginese.patch (text/plain, attachment)]

[0017-gnu-Add-font-google-noto-sans-buhid.patch (text/plain, attachment)]

[0018-gnu-Add-font-google-noto-sans-canadian-aboriginal.patch (text/plain, attachment)]

[0019-gnu-Add-font-google-noto-sans-carian.patch (text/plain, attachment)]

[0020-gnu-Add-font-google-noto-sans-cham.patch (text/plain, attachment)]

[0021-gnu-Add-font-google-noto-sans-cherokee.patch (text/plain, attachment)]

[0022-gnu-Add-font-google-noto-sans-cjk-jp.patch (text/plain, attachment)]

[0023-gnu-Add-font-google-noto-sans-cjk-kr.patch (text/plain, attachment)]

[0024-gnu-Add-font-google-noto-sans-cjk-sc.patch (text/plain, attachment)]

[0025-gnu-Add-font-google-noto-sans-cjk-tc.patch (text/plain, attachment)]

[0026-gnu-Add-font-google-noto-sans-coptic.patch (text/plain, attachment)]

[0027-gnu-Add-font-google-noto-sans-cuneiform.patch (text/plain, attachment)]

[0028-gnu-Add-font-google-noto-sans-cypriot.patch (text/plain, attachment)]

[0029-gnu-Add-font-google-noto-sans-deseret.patch (text/plain, attachment)]

[0030-gnu-Add-font-google-noto-sans-devanagari.patch (text/plain, attachment)]

[0031-gnu-Add-font-google-noto-sans-egyptian-hieroglyphs.patch (text/plain, attachment)]

[0032-gnu-Add-font-google-noto-sans-ethiopic.patch (text/plain, attachment)]

[0033-gnu-Add-font-google-noto-sans-georgian.patch (text/plain, attachment)]

[0034-gnu-Add-font-google-noto-sans-glagolitic.patch (text/plain, attachment)]

[0035-gnu-Add-font-google-noto-sans-gothic.patch (text/plain, attachment)]

[0036-gnu-Add-font-google-noto-sans-gujarati.patch (text/plain, attachment)]

[0037-gnu-Add-font-google-noto-sans-gurmukhi.patch (text/plain, attachment)]

[0038-gnu-Add-font-google-noto-sans-hanunoo.patch (text/plain, attachment)]

[0039-gnu-Add-font-google-noto-sans-hebrew.patch (text/plain, attachment)]

[0040-gnu-Add-font-google-noto-sans-imperial-aramaic.patch (text/plain, attachment)]

[0041-gnu-Add-font-google-noto-sans-inscriptional-pahlavi.patch (text/plain, attachment)]

[0042-gnu-Add-font-google-noto-sans-inscriptional-parthian.patch (text/plain, attachment)]

[0043-gnu-Add-font-google-noto-sans-javanese.patch (text/plain, attachment)]

[0044-gnu-Add-font-google-noto-sans-kaithi.patch (text/plain, attachment)]

[0045-gnu-Add-font-google-noto-sans-kannada.patch (text/plain, attachment)]

[0046-gnu-Add-font-google-noto-sans-kayah-li.patch (text/plain, attachment)]

[0047-gnu-Add-font-google-noto-sans-kharoshthi.patch (text/plain, attachment)]

[0048-gnu-Add-font-google-noto-sans-khmer.patch (text/plain, attachment)]

[0049-gnu-Add-font-google-noto-sans-lao.patch (text/plain, attachment)]

[0050-gnu-Add-font-google-noto-sans-lepcha.patch (text/plain, attachment)]

[0051-gnu-Add-font-google-noto-sans-limbu.patch (text/plain, attachment)]

[0052-gnu-Add-font-google-noto-sans-linear-b.patch (text/plain, attachment)]

[0053-gnu-Add-font-google-noto-sans-lisu.patch (text/plain, attachment)]

[0054-gnu-Add-font-google-noto-sans-lycian.patch (text/plain, attachment)]

[0055-gnu-Add-font-google-noto-sans-malayalam.patch (text/plain, attachment)]

[0056-gnu-Add-font-google-noto-sans-meetei-mayek.patch (text/plain, attachment)]

[0057-gnu-Add-font-google-noto-sans-myanmar.patch (text/plain, attachment)]

[0058-gnu-Add-font-google-noto-sans-n-ko.patch (text/plain, attachment)]

[0059-gnu-Add-font-google-noto-sans-ogham.patch (text/plain, attachment)]

[0060-gnu-Add-font-google-noto-sans-ol-chiki.patch (text/plain, attachment)]

[0061-gnu-Add-font-google-noto-sans-old-italic.patch (text/plain, attachment)]

[0062-gnu-Add-font-google-noto-sans-old-turkic.patch (text/plain, attachment)]

[0063-gnu-Add-font-google-noto-sans-oriya.patch (text/plain, attachment)]

[0064-gnu-Add-font-google-noto-sans-osmanya.patch (text/plain, attachment)]

[0065-gnu-Add-font-google-noto-sans-rejang.patch (text/plain, attachment)]

[0066-gnu-Add-font-google-noto-sans-runic.patch (text/plain, attachment)]

[0067-gnu-Add-font-google-noto-sans-samaritan.patch (text/plain, attachment)]

[0068-gnu-Add-font-google-noto-sans-shavian.patch (text/plain, attachment)]

[0069-gnu-Add-font-google-noto-sans-sundanese.patch (text/plain, attachment)]

[0070-gnu-Add-font-google-noto-sans-syloti-nagri.patch (text/plain, attachment)]

[0071-gnu-Add-font-google-noto-sans-symbols.patch (text/plain, attachment)]

[0072-gnu-Add-font-google-noto-sans-syriac-eastern.patch (text/plain, attachment)]

[0073-gnu-Add-font-google-noto-sans-syriac-estrangela.patch (text/plain, attachment)]

[0074-gnu-Add-font-google-noto-sans-syriac-western.patch (text/plain, attachment)]

[0075-gnu-Add-font-google-noto-sans-tai-tham.patch (text/plain, attachment)]

[0076-gnu-Add-font-google-noto-sans-thaana.patch (text/plain, attachment)]

[0077-gnu-Add-font-google-noto-sans-ugaritic.patch (text/plain, attachment)]

[0078-gnu-Add-font-google-noto-serif-bengali.patch (text/plain, attachment)]

[0079-gnu-Add-font-google-noto-serif-cjk-tc.patch (text/plain, attachment)]

[0080-gnu-Add-font-google-noto-serif-devanagari.patch (text/plain, attachment)]

[0081-gnu-Add-font-google-noto-serif-georgian.patch (text/plain, attachment)]

[0082-gnu-Add-font-google-noto-serif-gujarati.patch (text/plain, attachment)]

[0083-gnu-Add-font-google-noto-serif-lao.patch (text/plain, attachment)]

[0084-gnu-Add-font-google-noto-serif-tamil.patch (text/plain, attachment)]

[0085-gnu-Add-font-google-noto-serif-telugu.patch (text/plain, attachment)]

[0086-gnu-Add-font-google-noto-serif-thai.patch (text/plain, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #8 received at 28404 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: ng0 <ng0 <at> infotropique.org>
Cc: 28404 <at> debbugs.gnu.org
Subject: Re: [bug#28404] The complete Google Noto Fonts
Date: Mon, 11 Sep 2017 10:27:54 +0200

Hi ng0,

ng0 <ng0 <at> 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’.

Message #11 received at 28404 <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> infotropique.org>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 28404 <at> debbugs.gnu.org, ng0 <ng0 <at> infotropique.org>
Subject: Re: [bug#28404] The complete Google Noto Fonts
Date: Mon, 11 Sep 2017 10:57:04 +0000

[Message part 1 (text/plain, inline)]

Ludovic Courtès transcribed 1.2K bytes:
> Hi ng0,
> 
> ng0 <ng0 <at> 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!

Thanks.

> > 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?

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.
> 
> That’s a bummer.  Are you sure there’s no versioned URL somewhere?

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 versions
but try to get Google to do anything which is not giving up on projects
in ramdon patterns… :/ People and projects already fail with Chromium 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 ‘font-linuxlibertine’.
> 
> Thanks,
> Ludo’.
> 

-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://krosos.org/dist/keys/
https://www.infotropique.org https://www.krosos.org

[signature.asc (application/pgp-signature, inline)]

Message #14 received at 28404 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: ng0 <ng0 <at> infotropique.org>
Cc: 28404 <at> debbugs.gnu.org
Subject: Re: [bug#28404] The complete Google Noto Fonts
Date: Mon, 11 Sep 2017 13:55:35 +0200

Hello,

ng0 <ng0 <at> infotropique.org> skribis:

> 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.

--8<---------------cut here---------------start------------->8---
ludo <at> ribbon /tmp$ git clone https://github.com/googlei18n/noto-cjk
Cloning into 'noto-cjk'...
remote: Counting objects: 609, done.        
remote: Total 609 (delta 0), reused 0 (delta 0), pack-reused 609        
Receiving objects: 100% (609/609), 1.53 GiB | 6.66 MiB/s, done.
Resolving deltas: 100% (486/486), done.
Checking out files: 100% (140/140), done.
ludo <at> ribbon /tmp$ du -ms noto-cjk/.git
1568	noto-cjk/.git
--8<---------------cut here---------------end--------------->8---

Quite a lot.  However, the snapshot is half that size:

--8<---------------cut here---------------start------------->8---
$ guix download https://github.com/googlei18n/noto-cjk/archive/v1.004.tar.gz

Starting download of /tmp/guix-file.l7hpQP
From https://github.com/googlei18n/noto-cjk/archive/v1.004.tar.gz...
following redirection to `https://codeload.github.com/googlei18n/noto-cjk/tar.gz/v1.004'...
 v1.004                                                7.5MiB/s 01:44 | 785.4MiB transferred
/gnu/store/45j4prjlvc25dpbq4qgh437051cdczx8-v1.004.tar.gz
075p99prv3b5pvq60myhfjb7zyphl6fn0ckg8156m38ybisl4nl3
ludo <at> ribbon /tmp$ du -ms /gnu/store/45j4prjlvc25dpbq4qgh437051cdczx8-v1.004.tar.gz
786	/gnu/store/45j4prjlvc25dpbq4qgh437051cdczx8-v1.004.tar.gz
--8<---------------cut here---------------end--------------->8---

Maybe that’s OK, WDYT?  How does it compare to the precompiled archives?

> 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).

That “someone” does not exist.  If there were a whole bunch of people
waiting to save your time, and mine, and everyone else’s, we’d know it
by now.  :-)

Ludo’.

Message #17 received at 28404 <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> infotropique.org>
To: 28404 <at> debbugs.gnu.org
Cc: ng0 <ng0 <at> infotropique.org>
Subject: Re: [bug#28404] The complete Google Noto Fonts
Date: Mon, 11 Sep 2017 12:21:41 +0000

[Message part 1 (text/plain, inline)]

ng0 transcribed 4.2K bytes:
> Ludovic Courtès transcribed 1.2K bytes:
> > Hi ng0,
> > 
> > ng0 <ng0 <at> 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!
> 
> Thanks.
> 
> > > 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?
> 
> 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.
> > 
> > That’s a bummer.  Are you sure there’s no versioned URL somewhere?
> 
> 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 versions
> but try to get Google to do anything which is not giving up on projects
> in ramdon patterns… :/ People and projects already fail with Chromium 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.

I have to wait for another reply, so I started some notes on the lines above.

Emoji: can be build with "make" given the condition that nototools
(https://github.com/googlei18n/nototools/) is available. This in turn
depends on (python):

booleanOperations==0.7.0  defcon==0.3.1             fonttools==3.9.1
Pillow==4.0.0             pyclipper==1.0.6          ufoLib==2.0.0

emoji repo checked out with the whole history:          249 MB
emjo tagged tar:                                        33.5MB
cjk repo, latest tagged release (1st semester of 2017): 1.6 GB
cjk repo checked out with the whole history:            3.4 GB
rest of noto, repo:                                     1.0 GB
rest of noto, tagged tar:                               351 MB

The distributed fonts, pre-build:
root <at> sharknado9000:/var/www/krosos/mirror/fonts/noto-font/20170403# ls -hs
total 600M
8.0K Noto.20170403.sha256.txt                    260K NotoSansKannada-hinted.zip
4.5M NotoColorEmoji-unhinted.zip                 8.0K NotoSansKayahLi-unhinted.zip
288K NotoEmoji-unhinted.zip                       16K NotoSansKharoshthi-unhinted.zip
84K NotoKufiArabic-hinted.zip                    96K NotoSansKhmer-hinted.zip
72K NotoMono-hinted.zip                          76K NotoSansLao-hinted.zip
464K NotoNaskhArabic-hinted.zip                   40K NotoSansLepcha-unhinted.zip
164K NotoNastaliqUrdu-unhinted.zip                12K NotoSansLimbu-unhinted.zip
32K NotoSansArmenian-hinted.zip                  40K NotoSansLinearB-unhinted.zip
12K NotoSansAvestan-unhinted.zip                8.0K NotoSansLisu-unhinted.zip
20K NotoSansBalinese-unhinted.zip               8.0K NotoSansLycian-unhinted.zip
96K NotoSansBamum-unhinted.zip                  200K NotoSansMalayalam-hinted.zip
12K NotoSansBatak-unhinted.zip                   16K NotoSansMeeteiMayek-unhinted.zip
400K NotoSansBengali-hinted.zip                  340K NotoSansMyanmar-hinted.zip
16K NotoSansBrahmi-unhinted.zip                  12K NotoSansNKo-unhinted.zip
8.0K NotoSansBuginese-unhinted.zip               8.0K NotoSansOgham-unhinted.zip
8.0K NotoSansBuhid-unhinted.zip                  8.0K NotoSansOlChiki-unhinted.zip
28K NotoSansCanadianAboriginal-unhinted.zip     8.0K NotoSansOldItalic-unhinted.zip
8.0K NotoSansCarian-unhinted.zip                 8.0K NotoSansOldTurkic-unhinted.zip
32K NotoSansCham-hinted.zip                     328K NotoSansOriya-hinted.zip
48K NotoSansCherokee-hinted.zip                 8.0K NotoSansOsmanya-unhinted.zip
116M NotoSansCJKjp-hinted.zip                    8.0K NotoSansRejang-unhinted.zip
116M NotoSansCJKkr-hinted.zip                    8.0K NotoSansRunic-unhinted.zip
116M NotoSansCJKsc-hinted.zip                     12K NotoSansSamaritan-unhinted.zip
116M NotoSansCJKtc-hinted.zip                    8.0K NotoSansShavian-unhinted.zip
20K NotoSansCoptic-unhinted.zip                  12K NotoSansSundanese-unhinted.zip
276K NotoSansCuneiform-unhinted.zip               16K NotoSansSylotiNagri-unhinted.zip
8.0K NotoSansCypriot-unhinted.zip                404K NotoSansSymbols-unhinted.zip
12K NotoSansDeseret-unhinted.zip                 28K NotoSansSyriacEastern-unhinted.zip
356K NotoSansDevanagari-hinted.zip                28K NotoSansSyriacEstrangela-unhinted.zip
296K NotoSansEgyptianHieroglyphs-unhinted.zip     28K NotoSansSyriacWestern-unhinted.zip
172K NotoSansEthiopic-hinted.zip                  32K NotoSansTaiTham-unhinted.zip
44K NotoSansGeorgian-hinted.zip                  32K NotoSansThaana-hinted.zip
12K NotoSansGlagolitic-unhinted.zip             8.0K NotoSansUgaritic-unhinted.zip
8.0K NotoSansGothic-unhinted.zip                 200K NotoSerifBengali-hinted.zip
344K NotoSansGujarati-hinted.zip                 125M NotoSerifCJKtc-hinted.zip
128K NotoSansGurmukhi-hinted.zip                 128K NotoSerifDevanagari-hinted.zip
8.0K NotoSansHanunoo-unhinted.zip                 44K NotoSerifGeorgian-hinted.zip
28K NotoSansHebrew-hinted.zip                   100K NotoSerifGujarati-hinted.zip
1.3M NotoSans-hinted.zip                         840K NotoSerif-hinted.zip
8.0K NotoSansImperialAramaic-unhinted.zip         40K NotoSerifLao-hinted.zip
8.0K NotoSansInscriptionalPahlavi-unhinted.zip    64K NotoSerifTamil-hinted.zip
8.0K NotoSansInscriptionalParthian-unhinted.zip  180K NotoSerifTelugu-hinted.zip
24K NotoSansJavanese-unhinted.zip                36K NotoSerifThai-hinted.zip
32K NotoSansKaithi-unhinted.zip



> 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.

Would the tagged tarball of CJK be considered too big for our CI?
Before we can break it up in small pieces we need to deal with what
Google provides, which is awful in size.

> 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 ‘font-linuxlibertine’.
> > 
> > Thanks,
> > Ludo’.
> > 
> 
> -- 
> ng0
> GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
> GnuPG: https://krosos.org/dist/keys/
> https://www.infotropique.org https://www.krosos.org



-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://krosos.org/dist/keys/
https://www.infotropique.org https://www.krosos.org

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 28404 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: ng0 <ng0 <at> infotropique.org>
Cc: 28404 <at> debbugs.gnu.org
Subject: Re: [bug#28404] The complete Google Noto Fonts
Date: Tue, 12 Sep 2017 14:51:12 +0200

ng0 <ng0 <at> 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.

Ludo’.

Message #23 received at 28404 <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> infotropique.org>
To: 28404 <at> debbugs.gnu.org
Cc: ng0 <ng0 <at> infotropique.org>
Subject: Re: [bug#28404] The complete Google Noto Fonts
Date: Tue, 12 Sep 2017 14:51:56 +0000

[Message part 1 (text/plain, inline)]

Ludovic Courtès transcribed 0.3K bytes:
> ng0 <ng0 <at> 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

[signature.asc (application/pgp-signature, inline)]

Message #26 received at 28404 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: ng0 <ng0 <at> infotropique.org>
Cc: 28404 <at> debbugs.gnu.org
Subject: Re: [bug#28404] The complete Google Noto Fonts
Date: Tue, 12 Sep 2017 17:22:39 +0200

ng0 <ng0 <at> infotropique.org> skribis:

> 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

Sounds like a plan!

Thanks,
Ludo'.

Message #29 received at 28404 <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> infotropique.org>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 28404 <at> debbugs.gnu.org, ng0 <ng0 <at> infotropique.org>
Subject: Re: [bug#28404] The complete Google Noto Fonts
Date: Mon, 25 Sep 2017 12:25:54 +0000

[Message part 1 (text/plain, inline)]

Ludovic Courtès transcribed 0.3K bytes:
> ng0 <ng0 <at> infotropique.org> skribis:
> 
> > I propose:
> >
> > 1. package nototools.

Proposed for QA in bug#28594

> > 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
> 
> Sounds like a plan!
> 
> Thanks,
> Ludo'.
> 

-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://krosos.org/dist/keys/
https://www.infotropique.org https://krosos.org

[signature.asc (application/pgp-signature, inline)]

Message #34 received at 28404 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: ng0 <ng0 <at> infotropique.org>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 28404 <at> debbugs.gnu.org
Subject: Re: bug#28404: The complete Google Noto Fonts
Date: Thu, 13 Jan 2022 16:23:07 +0100

Hi,

This patch #28404 series [1] is about a font.  The last comment is from
late 2017.


1: <http://issues.guix.gnu.org/issue/28404>


On Mon, 25 Sep 2017 at 12:25, ng0 <ng0 <at> infotropique.org> wrote:
> Ludovic Courtès transcribed 0.3K bytes:
>> ng0 <ng0 <at> infotropique.org> skribis:
>>
>> > I propose:
>> >
>> > 1. package nototools.
>
> Proposed for QA in bug#28594

This #28594 had been closed,

        Tue, 28 Nov 2017 19:59:03 +0000
        (4 years, 6 weeks, 3 days ago)

but…

>> > 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
>>
>> Sounds like a plan!

…some parts of the plan are still missing. :-)


The primary author is not responding since years.  What do we do for the
patch series?  On one hand, piece of work had already been done and on
the other hand, other piece of work is still missing.

Is someone interested in helping to clean the work already done for
easing the merge?


Cheers,
simon

Message #37 received at 28404 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: 28404 <at> debbugs.gnu.org
Subject: Re: bug#28404: The complete Google Noto Fonts
Date: Mon, 17 Jan 2022 14:16:39 +0100

Hi,

zimoun <zimon.toutoune <at> gmail.com> skribis:

> The primary author is not responding since years.  What do we do for the
> patch series?  On one hand, piece of work had already been done and on
> the other hand, other piece of work is still missing.
>
> Is someone interested in helping to clean the work already done for
> easing the merge?

I think in this case it’s okay to close as “donewontfix” or something
along these lines.

The patch is still around and anyone interested in it can pick it up
from the archive.  Clearly, leaving issues open forever makes it harder
for us all to see where our attention is needed, so closing after a long
period of inactivity sounds like the right course of action to me.

Thanks,
Ludo’.

Message #40 received at 28404 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 28404 <at> debbugs.gnu.org
Subject: Re: bug#28404: The complete Google Noto Fonts
Date: Mon, 17 Jan 2022 15:23:42 +0100

Hi Ludo,

I reorganize the answers since it is 2 different items. :-)

On Mon, 17 Jan 2022 at 14:16, Ludovic Courtès <ludo <at> gnu.org> wrote:

>> The primary author is not responding since years.  What do we do for the
>> patch series?  On one hand, piece of work had already been done and on
>> the other hand, other piece of work is still missing.
>
> I think in this case it’s okay to close as “donewontfix” or something
> along these lines.

I will do with this “donewontfix” tag.


>> Is someone interested in helping to clean the work already done for
>> easing the merge?
>
> The patch is still around and anyone interested in it can pick it up
> from the archive.  Clearly, leaving issues open forever makes it harder
> for us all to see where our attention is needed, so closing after a long
> period of inactivity sounds like the right course of action to me.

The question is how to pick up.  On one hand, being still open does not
seem to work.  On the other hand, do we document in the manual this tag
“donewontfix” as the tag for “unfinished” patches.  For instance, some
of these “old” patches could be good starters for people wanting to help
but without knowing where to look at first.  WDYT?


Cheers,
simon

Message #43 received at 28404 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: 28404 <at> debbugs.gnu.org
Subject: Re: bug#28404: The complete Google Noto Fonts
Date: Mon, 17 Jan 2022 17:07:15 +0100

Hi,

zimoun <zimon.toutoune <at> gmail.com> skribis:

> On Mon, 17 Jan 2022 at 14:16, Ludovic Courtès <ludo <at> gnu.org> wrote:

[...]

>> The patch is still around and anyone interested in it can pick it up
>> from the archive.  Clearly, leaving issues open forever makes it harder
>> for us all to see where our attention is needed, so closing after a long
>> period of inactivity sounds like the right course of action to me.
>
> The question is how to pick up.  On one hand, being still open does not
> seem to work.  On the other hand, do we document in the manual this tag
> “donewontfix” as the tag for “unfinished” patches.  For instance, some
> of these “old” patches could be good starters for people wanting to help
> but without knowing where to look at first.  WDYT?

I wouldn’t worry much.  Someone might find it via a search engine, or an
old-timer might invite them to look for it in the bug tracker.  Worst
that can happen is that someone redoes the work from scratch, which is
suboptimal but not the end of the world either.

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.