unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@infotropique.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, tumashu <tumashu@163.com>
Subject: Re: Is font-google-noto toooooo big as a font package?
Date: Wed, 19 Jul 2017 22:50:29 +0000	[thread overview]
Message-ID: <20170719225029.szwrdekfpchazw7z@abyayala> (raw)
In-Reply-To: <87h8y8maep.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1228 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.
-- 
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-07-19 22:51 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 [this message]
2017-07-19 23:03             ` tumashu
2017-08-08 11:09             ` ng0
2017-08-08 11:35               ` ng0
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

  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=20170719225029.szwrdekfpchazw7z@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 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).