From: zimoun <zimon.toutoune@gmail.com>
To: ng0 <ng0@infotropique.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 28404@debbugs.gnu.org
Subject: [bug#28404] The complete Google Noto Fonts
Date: Thu, 13 Jan 2022 16:23:07 +0100 [thread overview]
Message-ID: <86y23jirs4.fsf_-_@gmail.com> (raw)
In-Reply-To: <20170925122554.hdonznpj4z6ylpx6@abyayala> (ng0@infotropique.org's message of "Mon, 25 Sep 2017 12:25:54 +0000")
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@infotropique.org> wrote:
> Ludovic Courtès transcribed 0.3K bytes:
>> ng0 <ng0@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
next prev parent reply other threads:[~2022-01-13 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 9:06 [bug#28404] The complete Google Noto Fonts ng0
2017-09-11 8:27 ` Ludovic Courtès
2017-09-11 10:57 ` ng0
2017-09-11 11:55 ` Ludovic Courtès
2017-09-11 12:21 ` ng0
2017-09-12 12:51 ` Ludovic Courtès
2017-09-12 14:51 ` ng0
2017-09-12 15:22 ` Ludovic Courtès
2017-09-25 12:25 ` ng0
2022-01-13 15:23 ` zimoun [this message]
2022-01-17 13:16 ` Ludovic Courtès
2022-01-17 14:23 ` zimoun
2022-01-17 16:07 ` Ludovic Courtès
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=86y23jirs4.fsf_-_@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=28404@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=ng0@infotropique.org \
/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).