From: wolf <wolf@wolfsden.cz>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 63707-done@debbugs.gnu.org, "Zhu Zihao" <all_but_last@163.com>,
宋文武 <iyzsong@envs.net>
Subject: [bug#63707] [PATCH] gnu: Add font-ipa.
Date: Sun, 2 Jul 2023 20:10:48 +0200 [thread overview]
Message-ID: <ZKG9qG9IKomrnaVg@ws> (raw)
In-Reply-To: <87jzvkj5g9.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
On 2023-07-01 12:23:34 +0200, Nicolas Goaziou wrote:
> Hello,
>
> Wolf <wolf@wolfsden.cz> writes:
>
> > * gnu/packages/fonts.scm (font-ipa): New variable.
>
> Applied with the changes below. Thank you.
Thank you for merging it.
> > ---
> > + (build-system font-build-system)
> > + (arguments
> > + (list #:phases #~(modify-phases %standard-phases
> > + (add-after 'unpack 'make-read-only
>
> I fixed indentation, which consumes way too much horizontal space here.
>
> > + (add-after 'install 'install-doc
> > + (lambda* (#:key outputs #:allow-other-keys)
>
> outputs argument is not necessary when using G-expressions. You don't
> use it either in your phases.
I admit I just copied over the package for font-ipa-ex and adjusted it, not
realizing that this part is not necessary.
>
> > + (description "Japanese outline fonts by Information-technology Promotion
> > +Agency, Japan (IPA)")
>
> The description should consist of full sentences:
>
> "These package provides Japanese outline fonts..."
Will keep that in mind.
>
> Regards,
> --
> Nicolas Goaziou
Have a nice day,
W.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-07-02 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 21:22 [bug#63707] [PATCH] gnu: Add font-ipa Wolf
2023-06-21 16:36 ` [bug#63707] Ping wolf
2023-07-01 10:23 ` bug#63707: [PATCH] gnu: Add font-ipa Nicolas Goaziou
2023-07-02 18:10 ` wolf [this message]
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=ZKG9qG9IKomrnaVg@ws \
--to=wolf@wolfsden.cz \
--cc=63707-done@debbugs.gnu.org \
--cc=all_but_last@163.com \
--cc=iyzsong@envs.net \
--cc=mail@nicolasgoaziou.fr \
/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.