all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@infotropique.org>
To: "Ludovic Courtès" <ludo@gnu.org>, tumashu <tumashu@163.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Is font-google-noto toooooo big as a font package?
Date: Tue, 8 Aug 2017 11:35:52 +0000	[thread overview]
Message-ID: <20170808113552.g3oevoqvd3hjqlqx@abyayala> (raw)
In-Reply-To: <20170808110909.d3lpwzo2efrykb6p@abyayala>

[-- Attachment #1: Type: text/plain, Size: 2758 bytes --]

ng0 transcribed 3.3K bytes:
> ng0 transcribed 2.3K bytes:
> > Ludovic Courtès transcribed 0.7K bytes:
> > > ng0 <ng0@infotropique.org> skribis:
> > > 
> > > > Ludovic Courtès transcribed 0.2K bytes:
> > > >> Hello,
> > > >> 
> > > >> tumashu <tumashu@163.com> skribis:
> > > >> 
> > > >> > the first thing is improve font-build-system to support split package easy
> > > >> 
> > > >> Good point, though I think we also need to find out how we would split
> > > >> it, which may not be that simple.
> > > >> 
> > > >> Ludo’.
> > > >> 
> > > >> 
> > > > 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/
> > > 
> > > So maybe we could make the CJK part a different output or a different
> > > package?
> > > 
> > > Ludo’.
> > > 
> > > 
> > 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.
> 
> Our current noto package isn't any different than the ones offered on
> their website: It is versioned (probably from github or a news announcement),
> but the file is not really versioned, and our downloaded file into the store
> is not versioned aswell.
> 
> Now we have two options: Switch to their github repositories for the downloads,
> where they are versioned, or use all the individual files from the noto website:
> 
> - 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
> 
> 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.

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.

Also I have an idea on how to fix some of the fonts which are not
using the font-build-system.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-08-08 11:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-16  0:08 Is font-google-noto toooooo big as a font package? Feng Shu
2017-07-16  0:29 ` ng0
2017-07-16  3:15   ` tumashu
2017-07-17 14:04 ` Ludovic Courtès
2017-07-17 14:22   ` tumashu
2017-07-18 10:07     ` Ludovic Courtès
2017-07-18 12:40       ` ng0
2017-07-18 12:43         ` ng0
2017-07-19  0:38         ` tumashu
2017-07-19 20:35           ` Ludovic Courtès
2017-07-19 20:36         ` Ludovic Courtès
2017-07-19 22:50           ` ng0
2017-07-19 23:03             ` tumashu
2017-08-08 11:09             ` ng0
2017-08-08 11:35               ` ng0 [this message]
2017-08-08 11:45                 ` ng0

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170808113552.g3oevoqvd3hjqlqx@abyayala \
    --to=ng0@infotropique.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=tumashu@163.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.